From owner-freebsd-questions Thu Jun 17 13:22:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from camel.ethereal.net (fraenatus.ethereal.net [204.107.140.58]) by hub.freebsd.org (Postfix) with ESMTP id 1EF8C15589 for ; Thu, 17 Jun 1999 13:22:40 -0700 (PDT) (envelope-from mistwolf@camel.ethereal.net) Received: (from mistwolf@localhost) by camel.ethereal.net (8.9.1a/8.9.1) id NAA29485; Thu, 17 Jun 1999 13:22:24 -0700 (PDT) Date: Thu, 17 Jun 1999 13:22:24 -0700 From: Jamie Norwood To: "Ronald F. Guilmette" Cc: questions@FreeBSD.ORG Subject: Re: A suggested kernel enhancement relating to kernel panics. Message-ID: <19990617132224.A28613@ethereal.net> References: <24429.929650487@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <24429.929650487@monkeys.com>; from Ronald F. Guilmette on Thu, Jun 17, 1999 at 01:14:47PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jun 17, 1999 at 01:14:47PM -0700, Ronald F. Guilmette wrote: > > I have already told my sad story about the kernel panics on my remote > machine, so I will not belabor that anymore now. > > However I would like to just note that the *one* key piece of data that > I cannot seem to lay my hands at the moment (and that would be most > helpful to me in sorting this out) is the "panic string", i.e. the > specific panic message that is being produced by the kernel when these > panics occur. Just having thoe would probably help a lot. Right now, > I don't even have the first clue as to what is causing the panics. > > These panic strings are presumably being written to the system console > at panic time. > > That's swell, except for the fact that the machine in question normally > has no monitor attached. :-( :-( And even if a monitor WAS attached, > I believe that the system is set to perform an automatic reboot after a > panic, so these message get cleared from the screen right after the > panic/reboot anyway. :-( > Why not compile the box to set it's console to serial 0? Then you could hook a laptop or other PC's serial port to it with a null-modem cable, set up a program to log all output on that port, and so when you get the message, you have it saved? Jamie -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+:+ a--(?) C++++ UB++++ P+ L--(++) E-- W++(--) N++ O? K w(---) O?>+ M?>+ V PS+ PE+ Y+ PGP->++ t+(*) 5+++ X++ R++ tv+ b+ DI++++ D++ G e>+ h--- r+++ y+++** ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message