Date: Fri, 01 Feb 2008 22:08:26 -0800 From: "Chris H." <chris#@1command.com> To: freebsd-stable@freebsd.org Subject: Re: dueling (s)printf()'s - what's the cure? Message-ID: <20080201220826.9niawaznesgw4gc8@webmail.1command.com> 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
Quoting Jeremy Chadwick <koitsu@freebsd.org>: > 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. > > 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. Good to know. relatedness stops here. :) > > 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. Understood. > > 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: > > http://jdc.parodius.com/freebsd/common_issues.txt Yes, I read this already (thanks for sharing it when I originally asked about this). But was hoping something had been done that fixes this. > > 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. > > 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). Good to know - even if it's not a cure. :) Thank you Jeremy, for taking the time to provide such an informative reply. Best wishes. --Chris H > > -- > | 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 | > > _______________________________________________ > 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" > -- panic: kernel trap (ignored)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080201220826.9niawaznesgw4gc8>