From owner-freebsd-stable@FreeBSD.ORG Sat Feb 2 04:34:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D010116A419 for ; Sat, 2 Feb 2008 04:34:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id C005C13C45D for ; Sat, 2 Feb 2008 04:34:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id A54471CC05F; Fri, 1 Feb 2008 20:34:56 -0800 (PST) Date: Fri, 1 Feb 2008 20:34:56 -0800 From: Jeremy Chadwick To: "Chris H." Message-ID: <20080202043456.GA96681@eos.sc1.parodius.com> References: <20080201183111.b52knrrsw00gkokc@webmail.1command.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080201183111.b52knrrsw00gkokc@webmail.1command.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: dueling (s)printf()'s - what's the cure? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 04:34:56 -0000 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. 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. 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 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). -- | 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 |