Date: Fri, 18 Jun 2010 08:18:52 -0700 From: mdf@FreeBSD.org To: Alexander Best <alexbestms@uni-muenster.de> Cc: freebsd-current@freebsd.org, Jille Timmermans <jille@quis.cx> Subject: Re: strange scsi/CAM related dmesg output Message-ID: <AANLkTikChP3fP5WwDGD0LgZEylHo_ZiUicYMo2GPCXMv@mail.gmail.com> In-Reply-To: <AANLkTimpYGRKKF-c8YfjaQD38px3F38ktC8gwfun98od@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Thanks, matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikChP3fP5WwDGD0LgZEylHo_ZiUicYMo2GPCXMv>