From owner-freebsd-current Sun Oct 13 23:16:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA00455 for current-outgoing; Sun, 13 Oct 1996 23:16:49 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA00450 for ; Sun, 13 Oct 1996 23:16:47 -0700 (PDT) Received: from irz201.inf.tu-dresden.de by mail.crl.com with SMTP id AA21314 (5.65c/IDA-1.5 for ); Sun, 13 Oct 1996 23:15:53 -0700 Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz201.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA01370 for ; Mon, 14 Oct 1996 08:04:37 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA00897 for freebsd-current@FreeBSD.org; Mon, 14 Oct 1996 08:04:36 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.6/8.6.9) id MAA00309 for freebsd-current@FreeBSD.org; Sun, 13 Oct 1996 12:16:03 +0200 (MET DST) From: J Wunsch Message-Id: <199610131016.MAA00309@uriah.heep.sax.de> Subject: Re: Message buffer oddity To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 13 Oct 1996 12:16:02 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from j at "Oct 13, 96 11:45:12 am" X-Phone: +49-351-2012 669 X-Pgp-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Followup after rebooting: > I gonna reboot now again, and see whether this will happen again. Of > course, i have to send the mail before... It's still there. I can fully reproduce it by booting with -v (so to produce large probe output), and even without -v, it happens a few bytes later. I recompiled a kernel from scratch, with reverted to the original version. It's less obvious now, but every now and then, i also get something like: Device sd1a: name slot allocat%4O\^A%Dc\^A\^ETO\^A\^EdO\^A\^E\M^Ts\^A\^ED\M^W\^A\^ET{\^A\^EdO\^A\^EtK\^A\^E\^DO\^AG\M^T\^N\^A\^E\M^T_\^A\^Et+\^A\^E$\M^@\^A\^ED,\^A\^ET,\^A\^Ety\^A\^E\^DJ\^A\^E$B\^A\^Edf\^A\^Etn\^A\^Ed\M^B\^A\^Etr\^A\^E\^Ds\^A\^E\^TS\^A\^E4\M^_\^A\^E\M^Dk\^A\^E\M^Tk\^A\^E$\M^[\^A\^E4k\^A\^ED3\^A\^ET\M^_\^A\^Ed\^?\^A\^Et\^?\^A\^E\^D\M^@\^A\^E\^T8\^A\^E$D\^A\^E4D\^A\^Ed\M^H\^A\^Et\240\^A\^E\M^D\M^D\^A\^E\M^T\M^D\^A\^E$\M^D\^A\^E4\M^D\^A\^EDl\^A\^ETl\^A\^Edl\^A\^Etl\^A\^E\^Dm\^A\^E\^Ta\^A\^E$m\^A\^E4m\^A\^EDm\^AGT1Gt\M^]G4]GdqGtYG\M^DYG$-ion failed (E=17) Device rsd1a: name slot allocation failed (E=17) You notice that there's just junk inmidst a word, while the word itself is intact. The amount of junk varies between inocations of `dmesg', sometimes everything looks ok. I've also noticed that syslogd takes a huge amount of time to start with allot of rattling on the disk after my upgrade to -current. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)