Date: Fri, 12 Oct 2007 17:02:58 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, JoaoBR <joao@matik.com.br> Subject: Re: what is this: SdMaP0? Message-ID: <470F7082.3050200@FreeBSD.org> In-Reply-To: <20071012122948.GM2180@deviant.kiev.zoral.com.ua> References: <200710120913.47380.joao@matik.com.br> <20071012122049.GA96557@eos.sc1.parodius.com> <20071012122948.GM2180@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote: > On Fri, Oct 12, 2007 at 05:20:49AM -0700, Jeremy Chadwick wrote: >> On Fri, Oct 12, 2007 at 09:13:47AM -0300, JoaoBR wrote: >>> somebody has a translation for this in my dmesg of amd64? >>> SdMaP0:: AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e >> Here's the translation, and look closely: >> >> SMP: AP CPU #1 Launched! >> da0: 160.000MB/s transfe >> >> And yes, I have seen this before on amd64. My guess is that it's two >> things in the kernel trying to output to the console buffer at the exact >> same time, and there's no mutex lock being done. > > I think that setting the option PRINTF_BUFR_SIZE 128 could help in this > situation. BTW, note my kern/116310. It fixes relate issue for log() function. But I did not touch kernel's printf(). Our logs have no junk now. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470F7082.3050200>