Date: Fri, 12 Oct 2007 15:29:48 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: JoaoBR <joao@matik.com.br>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: what is this: SdMaP0? Message-ID: <20071012122948.GM2180@deviant.kiev.zoral.com.ua> In-Reply-To: <20071012122049.GA96557@eos.sc1.parodius.com> References: <200710120913.47380.joao@matik.com.br> <20071012122049.GA96557@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--bO/C3H35Ok2OdENj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 >=20 > Here's the translation, and look closely: >=20 > SMP: AP CPU #1 Launched! > da0: 160.000MB/s transfe >=20 > 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. --bO/C3H35Ok2OdENj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHD2i8C3+MBN1Mb4gRAsKVAJ9oKbWzEdnsnkEA47hrat6OSuOHTwCeKtRX L/BWj81cBlC4KXoOuhbkx1E= =KtLJ -----END PGP SIGNATURE----- --bO/C3H35Ok2OdENj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071012122948.GM2180>