From owner-freebsd-hackers Mon May 6 06:54:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA13501 for hackers-outgoing; Mon, 6 May 1996 06:54:06 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA13496 for ; Mon, 6 May 1996 06:54:05 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id IAA16330; Mon, 6 May 1996 08:52:57 -0500 From: Joe Greco Message-Id: <199605061352.IAA16330@brasil.moneng.mei.com> Subject: Re: News server kernel panics, dmesg buffer too small... To: taob@io.org (Brian Tao) Date: Mon, 6 May 1996 08:52:57 -0500 (CDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Brian Tao" at May 3, 96 11:24:30 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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