From owner-freebsd-questions@FreeBSD.ORG Thu Mar 4 12:37:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B30DC16A4CE for ; Thu, 4 Mar 2004 12:37:17 -0800 (PST) Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B45F43D49 for ; Thu, 4 Mar 2004 12:37:17 -0800 (PST) (envelope-from ben@spooty.net) Received: from m170-mp1.cvx3-b.pop.dial.ntli.net ([80.1.84.170]) by mta02-svc.ntlworld.comESMTP <20040304203639.HRHH14417.mta02-svc.ntlworld.com@m170-mp1.cvx3-b.pop.dial.ntli.net>; Thu, 4 Mar 2004 20:36:39 +0000 From: Ben Paley To: Matthew Seaman Date: Thu, 4 Mar 2004 20:30:20 +0000 User-Agent: KMail/1.5.4 References: <200403041807.04392.ben@spooty.net> <20040304193757.GB1159@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040304193757.GB1159@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403042030.20386.ben@spooty.net> cc: freebsd-questions@freebsd.org Subject: Re: kernel panic messages? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 20:37:17 -0000 On Thursday 04 March 2004 7:37 pm, you wrote: > You need to setup your machine to capture the appropriate data after > the panic. There's general information about how to do that in a > series of articles here: > > http://www.oreillynet.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html > http://www.oreillynet.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html This is great stuff: I'm compiling a debugging kernel as I type > However, you're seeing panics in the boot sequence: if that's actually > early on during booting, the system won't have initialised the disks > systems, so it can't record a crashdump. It's before I can log in, but really at the end of the whole process: the disks have already been checked and so on, so I reckon I stand a good chance of getting a dump. > but unless you're pretty much up-to-speed with kernel development, > you're probably not going to be able to extract much useful > information that way. Not me! But I know someone who knows what all this stuff means (ie the -current@ list) Thanks very much, Ben