Date: Fri, 18 Jun 2010 20:28:48 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: mdf@FreeBSD.org Cc: freebsd-current@FreeBSD.org, Jille Timmermans <jille@quis.cx>, Alexander Best <alexbestms@uni-muenster.de> Subject: Re: strange scsi/CAM related dmesg output Message-ID: <4C1BACD0.8050707@icyb.net.ua> In-Reply-To: <AANLkTikChP3fP5WwDGD0LgZEylHo_ZiUicYMo2GPCXMv@mail.gmail.com> References: <AANLkTinPhcc8Z_BdvoEQUv-ZXlHAYOTQJwlUQDVO8iJ9@mail.gmail.com> <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> <4C0A9D57.8000900@quis.cx> <201006070957.07376.jhb@freebsd.org> <AANLkTimpYGRKKF-c8YfjaQD38px3F38ktC8gwfun98od@mail.gmail.com> <AANLkTikChP3fP5WwDGD0LgZEylHo_ZiUicYMo2GPCXMv@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 18/06/2010 18:18 mdf@FreeBSD.org said the following: > On Fri, Jun 18, 2010 at 8:11 AM, Alexander Best > <alexbestms@uni-muenster.de> wrote: >> On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin <jhb@freebsd.org> wrote: >>> It can happen because the print buffer size thing is not line-buffered, it is >>> printf-invocation buffered. >> hmmm...can this somehow be fixed? i'm not sure this is specific to >> scsi/cam. the other day i bootd my system and almost all of the dmesg >> output was displayed incorrectly. would increasing PRINTF_BUFR_SIZE >> from 128 to lets say 512 or 1024 solve the issue? > > I think what jhb meant was that we could look for the '\n' and flush > to console there, instead of waiting for the end of the buffer. This > would perhaps have more interleaved full lines, but likely fewer > interleaved partial lines. Not sure if it's relevant here, but want to point out that writing to kernel msgbuf is char-by-char, so any kind of interleaving is possible there and PRINTF_BUFR_SIZE is irrelevant to that. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C1BACD0.8050707>