From owner-freebsd-hackers Sun Aug 27 12:14: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 39AD737B43F for ; Sun, 27 Aug 2000 12:13:59 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Aug 2000 20:13:58 +0100 (BST) Date: Sun, 27 Aug 2000 20:13:57 +0100 From: David Malone To: Simon Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Please help me identify this: Message-ID: <20000827201357.A1488@walton.maths.tcd.ie> References: <200008271702.LAA17882@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008271702.LAA17882@mail.fpsn.net>; from simon@optinet.com on Sun, Aug 27, 2000 at 01:04:14PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 01:04:14PM -0400, Simon wrote: > Can someone please help me identify the following message? I get > it when my freebsd panics and I have to do a cold- reboot. The best thing to try is getting a trace back from the panic. Add "options DDB" to your kernel, recompile and install. Now when it dies you should find it ends up in the kernel debugger. You should be able to type "t" to get a trace of where in the kernel the problem occured. If you can post that, with the output of "dmesg" just after boot, and a copy of your kernel config file that will give people more to work on. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message