Date: Mon, 6 May 1996 08:52:57 -0500 (CDT) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: taob@io.org (Brian Tao) Cc: freebsd-hackers@freebsd.org Subject: Re: News server kernel panics, dmesg buffer too small... Message-ID: <199605061352.IAA16330@brasil.moneng.mei.com> In-Reply-To: <Pine.NEB.3.92.960503224431.22516K-100000@zot.io.org> from "Brian Tao" at May 3, 96 11:24:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> In the first instance, the one /kernel line was the only thing > left in syslog. No panic message or boot messages were recorded (how > did the bootup stuff not get saved?). > > In the second case, it looks like the panic may have been > truncated. Is it possible to locate the cause of the panic given > above? This is the first time I've seeen a vm_page_free panic logged > with the offset, etc. information. > > Anyhow, it would be nice if the default message buffer was bumped > up to 8K. Boot time messages on my news server add up to 3678 bytes > (9 drives to report). There was some discussion back in February > about doing this, but the March 23 snapshot still allocated 4K (I > haven't had a chance to check out the May 1 snapshot). What do I need > to recompile with a larger MSG_BSIZE? There's the kernel, dmesg and > syslogd... anything else? Hi Brian, I was whining about this a while back too because I have a few more drives than 9 :-) I never actually _did_ it but the consensus, I believe, was to bump MSG_BSIZE, preferably to a power of 2. :-) ... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605061352.IAA16330>