From owner-freebsd-hackers Fri May 3 20:25:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA01895 for hackers-outgoing; Fri, 3 May 1996 20:25:47 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA01877 for ; Fri, 3 May 1996 20:25:23 -0700 (PDT) Received: from zot.io.org (taob@zot.io.org [198.133.36.82]) by post.io.org (8.7.5/8.7.3) with SMTP id XAA12359 for ; Fri, 3 May 1996 23:27:00 -0400 (EDT) Date: Fri, 3 May 1996 23:24:30 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS-L Subject: News server kernel panics, dmesg buffer too small... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For whatever reason, my news server crashed twice today. This was all I could get out of the syslog: May 3 00:02:34 news1 batcher[17263]: batcher bialik times user 0.063 system 0.220 elapsed 11.684 May 3 00:02:34 news1 batcher[17263]: batcher bialik stats batches 1 articles 271 bytes 521024 May 3 00:02:40 news1 nnrpd[16599]: akira.net5a.io.org group alt.binaries.nude.celebrities 20 May 3 00:13:26 news1 /kernel: <07> May 3 00:13:27 news1 lpd[103]: restarted May 3 00:13:30 news1 innd: ME descriptors 2048 May 3 00:13:30 news1 innd: ME outgoing 2035 [...] May 3 19:26:45 news1 nnrpd[20383]: gleaner.net4.io.org group comp.binaries.psion 1 May 3 19:37:07 news1 /kernel: vm_page_free: offset(565248), bmapped(1), busy(0), PG_BUSY(0) May 3 19:37:07 news1 /kernel: panic: vm_page_free: freeing busy page May 3 19:37:07 news1 /kernel: May 3 19:37:08 news1 /kernel: syncing disks... 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 giving up May 3 19:37:08 news1 /kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 3 19:37:08 news1 /kernel: Rebooting... May 3 19:37:08 news1 /kernel: FreeBSD 2.1.0-RELEASE #0: Fri Feb 16 21:05:06 EST 1996 May 3 19:37:08 news1 /kernel: taob@cabal.io.org:/src/2.1.0-RELEASE/sys/compile/NEWS 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? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"