From owner-freebsd-questions Tue Jul 8 10:34:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27968 for questions-outgoing; Tue, 8 Jul 1997 10:34:28 -0700 (PDT) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27962 for ; Tue, 8 Jul 1997 10:34:24 -0700 (PDT) Received: from ds9.sirius.com (ds9.sirius.com [205.134.226.34]) by mail1.sirius.com (8.8.6/Sirius-8.8.6-97.06.26) with ESMTP id KAA00669; Tue, 8 Jul 1997 10:33:40 -0700 (PDT) Received: from localhost (dlowe@localhost) by ds9.sirius.com (8.6.12/961127) with SMTP id KAA14531; Tue, 8 Jul 1997 10:32:41 -0700 X-Authentication-Warning: ds9.sirius.com: dlowe owned process doing -bs Date: Tue, 8 Jul 1997 10:32:39 -0700 (PDT) From: David Lowe X-Sender: dlowe@ds9 To: David Greenman cc: freebsd-questions@FreeBSD.ORG Subject: Re: Logging kernel panics In-Reply-To: <199707080217.TAA03145@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David - We already have everything going to a serial console, as I said - the problem is that the device we're using to attach to the serial console doesn't log anything. It would show us the panic message only if someone was attached to the console at the time. What I'm looking for is some way of storing the last panic error in a more permanent fashion - to disk, assuming the disk isn't toast... Any ideas? David Lowe On Mon, 7 Jul 1997, David Greenman wrote: > >Is there some fairly reliable way of storing panic messages, short of > >logging all console output via a serial port? We already have a serial > >console, but the darned thing doesn't have any logging at all. > > Try building your bootblocks with the "BOOT_FORCE_COMCONSOLE" option, and > then re-installing them with disklabel -B . This will cause all console > output to go to the serial port. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project >