Date: Sat, 2 Feb 2008 07:24:07 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-stable@freebsd.org, "Chris H." <chris#@1command.com> Subject: Re: dueling (s)printf()'s - what's the cure? Message-ID: <20080202052407.GE57756@deviant.kiev.zoral.com.ua> In-Reply-To: <20080202043456.GA96681@eos.sc1.parodius.com> References: <20080201183111.b52knrrsw00gkokc@webmail.1command.com> <20080202043456.GA96681@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--AXfLY1v65H9m1lDu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 01, 2008 at 08:34:56PM -0800, Jeremy Chadwick wrote: > On Fri, Feb 01, 2008 at 06:31:11PM -0800, Chris H. wrote: > > I mentioned a problem with this once before, and was referred to > > other threads that also talked about this. But I believe a recent > > problem I was experiencing, may have been related to this: > > [: -le: argument expected. So I'd like to bring it up again, in > > hopes that someone might have a cure. Specifically, two printf()'s > > are sent to the same line, which results in a /very/ hard line to > > decipher. >=20 > The two problems you're discussing are entirely 100% unrelated to one > another. Please do not try and relate them, it will just confuse > readers of both threads. >=20 > The problem with [/test on your system is something that's specific to > your system. I'm hoping the reinstall you're doing (see private mail) > will alleviate this, and if it doesn't, something you're doing after the > fresh install is causing it. That should be discussed in the other > thread and not here. >=20 > The problem with kernel printf()s being interwoven is documented in my > "common issues" file, with numerous threads referenced -- see "Scrambled > dmesg/kernel output" here: >=20 > http://jdc.parodius.com/freebsd/common_issues.txt >=20 > There is no fix or workaround for this problem. Someone mentioned > increasing PRINTF_BUFR_SIZE to 128, which does not fix the problem, > nor diminish it in any way. What X in the RELENG_X where PRINTF_BUFR_SIZE has no effect ? This feature is not in the RELENG_6. Some time ago I made a backport, see http://people.freebsd.org/~kib/misc/releng_6_printf_bufr.2.patch I was said that the patch introduces some strange packet corruption, that I cannot test. >=20 > It's very important that people understand the interwoven kernel output > is specific to stuff printed to the console at the kernel level (e.g. a > driver/module, a piece of the kernel, etc.), and will not happen when > doing something that's output via printf(3) from libc (e.g. output from > "make buildworld", "yes", "ls -FRal /", and so on). >=20 > --=20 > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --AXfLY1v65H9m1lDu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkej/nYACgkQC3+MBN1Mb4hHAgCgwv7qQN8QMbv3G9i7zBZPXPnh q+QAoJNicV+Tf9G7h5dsl06MsrwyX3lf =/RqP -----END PGP SIGNATURE----- --AXfLY1v65H9m1lDu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080202052407.GE57756>