From owner-freebsd-current@FreeBSD.ORG Sun Feb 17 16:50:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA4E816A468 for ; Sun, 17 Feb 2008 16:50:41 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4E30413C4CC; Sun, 17 Feb 2008 16:50:41 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47B865E0.20407@FreeBSD.org> Date: Sun, 17 Feb 2008 17:50:40 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Michiel Boland References: <43555.82.234.78.29.1203154742.squirrel@secure.synsport.net> <20080216175811.GA33393@saturn.kn-bremen.de> <47B7352B.1040302@marino.st> <20080216210731.GA40417@saturn.kn-bremen.de> <55528.82.234.78.29.1203252678.squirrel@secure.synsport.net> <20080217160642.2ac9363e@peedub.jennejohn.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: PRINTF_BUFR_SIZE (Re: 7.0 RC2 kernel panic with Kqemu/AMD64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Feb 2008 16:50:42 -0000 Michiel Boland wrote: > On Sun, 17 Feb 2008, Gary Jennejohn wrote: > > [...] >> I can't help with your problem, but I suggest that you add >> options PRINTF_BUFR_SIZE=128 >> to your kernel config file to avoid the above corrupted output. > > Any reason why this PRINTF_BUFR_SIZE option isn't in GENERIC on all > platforms? At the moment it is set for sun4v only. > > Cheers > Michiel > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > I think the fear is that it could cause a stack overflow because it allocates a character array (128-bytes in the above case) on the stack. I would like to know how real this fear is though. Clearly we do need a way to avoid interleaving console output by default. Kris