From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 1A1tLD-0006ZJ-00 for ; Tue, 23 Sep 2003 16:00:55 -0400 Received: from pcp02174144pcs.verona01.nj.comcast.net ([68.37.217.154]) by comcast.net (rwcrmhc12) with SMTP id <2003092320002101400ms3ine>; Tue, 23 Sep 2003 20:00:22 +0000 Date: Tue, 23 Sep 2003 15:59:25 -0400 (EDT) From: Igor Gueths X-X-Sender: igueths@squeaks To: speakup@braille.uwo.ca Subject: messages printed after login? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Hi all. Whenever I login to a new TTY I keep getting stuff like the following: c0288010 get_option_Rsmp_b0e10781 c028805c get_options_Rsmp_0fbff9b9 c0288170 rb_insert_color_Rsmp_aa2b5a22 c02883b8 rb_erase_Rsmp_da226a80 c0288490 rwsem_down_read_failed c02885d4 rwsem_down_write_failed c0288714 rwsem_wake c028a290 zlib_inflate_workspacesize_Rsmp_ce5ac24f c028a438 zlib_inflate_Rsmp_64cf8602 c028a41c zlib_inflateInit__Rsmp_456e911d c028a32c zlib_inflateInit2__Rsmp_5d3b34e2 c028a2f0 zlib_inflateEnd_Rsmp_9ef45f92 c028a828 zlib_inflateSync_Rsmp_34582e0d c028a298 zlib_inflateReset_Rsmp_ef76d642 c028a900 zlib_inflateSyncPoint_Rsmp_41d10449 c028aa5c zlib_inflateIncomp_Rsmp_b5058135 c028cabc zlib_deflate_workspacesize_Rsmp_f0caf44b c028bacc zlib_deflate_Rsmp_28c35bd1 c028b550 zlib_deflateInit__Rsmp_c5e78d3e c028b578 zlib_deflateInit2__Rsmp_262f9b2a c028bd3c zlib_deflateEnd_Rsmp_cd8db61d c028b8f8 zlib_deflateReset_Rsmp_8abb5b63 c028bd80 zlib_deflateCopy_Rsmp_fd39628f c028b97c zlib_deflateParams_Rsmp_9088bbb2 These look like calls to zlib_deflate, and the beginning part looks like an I/O address where a device would be, however I'm not sure what would influence such behavior. I have never seen this before in all the times I've rebuilt/tinkered with various kernels. I'm currently running Kernel-2.4.22 with Debian-3.0R1. Does anyone have any idea what's causing those messages to be printed? Thanks!