Date: Wed, 17 Dec 2008 17:22:13 +0300 From: pluknet <pluknet@gmail.com> To: "Paul B. Mahol" <onemda@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: PRINTF_BUFR_SIZE in freebsd6 Message-ID: <a31046fc0812170622j1cfccfcem4bdc4c23f57de444@mail.gmail.com> In-Reply-To: <3a142e750812170610r25a48762y845010c6898f52d4@mail.gmail.com> References: <a31046fc0812160423g7508bdbdrb160e9d1ec12b6e3@mail.gmail.com> <20081216134035.GU2038@deviant.kiev.zoral.com.ua> <a31046fc0812170248g4fa19250j159c645bdcd4ac89@mail.gmail.com> <a31046fc0812170552k31a7434cy9a13ea5c8322e94e@mail.gmail.com> <3a142e750812170610r25a48762y845010c6898f52d4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/12/17 Paul B. Mahol <onemda@gmail.com>: > On 12/17/08, pluknet <pluknet@gmail.com> wrote: >> 2008/12/17 pluknet <pluknet@gmail.com>: >>> 2008/12/16 Kostik Belousov <kostikbel@gmail.com>: >>>> On Tue, Dec 16, 2008 at 03:23:28PM +0300, pluknet wrote: >>>>> Hi. >>>>> >>>>> Could the PRINTF_BUFR_SIZE option be safely merged into RELENG_6 without >>>>> merging a possible underlining infrastructure and breaking something >>>>> else? >>>>> I want to use it in my custom freebsd6 because I see "interspersed >>>>> strings >>>>> written from different CPUs at the same time": >>>>> >>>>> uuusseseerrvmrem: vlmivmeimtme :e mx:ceed eldi bly 2i89m68m (iihttt t >>>>> pde) eaxtx cfcorke1 22e3e >>>>> deded ebyd by28 296898 68(h t(tpdh) att ftorkp1 22d3 >>>>> ) at fork1 223 >>>>> >>>>> I'm talking about only merging kern/subr_prf.c 1.126, 1.128, 1.129. >>>>> >>>>> Thanks. >>>> >>>> I did a backport of the option some time ago, see >>>> http://people.freebsd.org/~kib/misc/releng_6_printf_bufr.3.patch >>>> >>> >>> Thank you! >>> >>> 6.3 system panics (many page faults, one after another) early at boot >>> without the option, and boots with it in the QEMU environment. >>> Next step to test it on a real (and SMPable) hardware. >>> >> >> Now tested on a real 2xXeon 3.0 w/ HTT enabled w/ PRINTF_BUFR_SIZE enabled. >> >> Received the following panic: > > And how big is PRINTF_BUFR_SIZE ? Hi. I set options PRINTF_BUFR_SIZE=128 And maybe it's not enough (?) because I stress-tested server triggering to appear many kernel messages simultaneously. I don't know coherence between buffer size and this panic though. > > -- > Paul >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0812170622j1cfccfcem4bdc4c23f57de444>