From owner-freebsd-current@FreeBSD.ORG Sat Mar 28 01:38:30 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 688761065672 for ; Sat, 28 Mar 2009 01:38:30 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-out2.uni-muenster.de (ZIVM-OUT2.UNI-MUENSTER.DE [128.176.192.9]) by mx1.freebsd.org (Postfix) with ESMTP id F10B08FC1A for ; Sat, 28 Mar 2009 01:38:29 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) X-IronPort-AV: E=Sophos;i="4.38,435,1233529200"; d="scan'208";a="212444604" Received: from zivmaildisp2.uni-muenster.de (HELO ZIVMAILUSER05.UNI-MUENSTER.DE) ([128.176.188.143]) by zivm-relay2.uni-muenster.de with ESMTP; 28 Mar 2009 02:38:28 +0100 Received: by ZIVMAILUSER05.UNI-MUENSTER.DE (Postfix, from userid 149459) id BC6831B07E2; Sat, 28 Mar 2009 02:38:28 +0100 (CET) Date: Sat, 28 Mar 2009 02:38:28 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: In-Reply-To: <20090321200441.573995af@ernst.jennejohn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: weird console output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2009 01:38:30 -0000 so. shouldn't this be in CURRENT? Gary Jennejohn schrieb am 2009-03-21: > On Sat, 21 Mar 2009 14:52:59 -0400 > Chuck Robey wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > Gary Jennejohn wrote: > > > On Fri, 20 Mar 2009 20:49:08 -0400 > > > Justin Hibbits wrote: > > >> On Sat, Mar 21, 2009 at 01:02:25AM +0100, Alexander Best wrote: > > >>> very often when i boot or shutdown my pc i see weird text being > > >>> output to the > > >>> console. to me it seems like 2 messages are being mixed into 1 > > >>> message. here's > > >>> an example: > > >>> "WcAdR0N IaNtG : aWtIaT1N EbSuSs o0p ttiaorng eetn a1b lleudn, > > >>> 0e > > >>> xcpde0c:t r > >>> H1W0ANR NJILN1G: DIAG2N>O SRTeImCo voapbtlieo nC De-nRaObMl > > >>> eSdC,S Ie-x0p > > >>> edcetv irceed uc > > >>> ecdd 0p:e r3f3o.r0m0a0nMcB/es. > > >>> transfers" > > >>> i'm running FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT > > >>> #20 r190162M: > > >>> Fri Mar 20 19:10:47 UTC 2009 > > >>> root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL > > >>> i386, but i've also had this issue under CURRENT. maybe this > > >>> issue is smp > > >>> related? > > >>> cheers. > > >>> alex > > >> You are correct, it is smp related. Those are two messages > > >> interlaced. I see > > >> them often when shutting down my SMP system. > > > This quesion is asked and answered again and again. > > > Set "options PRINTF_BUFR_SIZE=128" in your kernel config. > > Gary, do you know why setting it to 128 fixes things? Is the > > default size 0? I > > could see that causing things, but it's hard to believe. I've been > > watching a > > long time to see a fix for this. > Looking at /sys/kern/subr_prf.c, there's apparently no buffering at > all > when PRINTF_BUFR_SIZE isn't defined. The value 128 has proved itself > to be adequate based on experience since most kernel output is > smaller > than that. Its' what I and others use. > --- > Gary Jennejohn