On 12/17/08, pluknet <pluk...@gmail.com> wrote: > 2008/12/17 pluknet <pluk...@gmail.com>: >> 2008/12/16 Kostik Belousov <kostik...@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 ? -- Paul _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
