Date: Thu, 21 Jun 2001 21:27:49 +0200 From: Alexander Langer <alex@big.endian.de> To: Bill Moran <wmoran@iowna.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PANIC - 4.3-STABLE, suspecting ata controller Message-ID: <20010621212749.A3281@zerogravity.kawo2.rwth-aachen.d> In-Reply-To: <3B322B93.20994E19@iowna.com>; from wmoran@iowna.com on Thu, Jun 21, 2001 at 01:14:59PM -0400 References: <3B322B93.20994E19@iowna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Bill Moran (wmoran@iowna.com): > http://www.prioritydesigns.com/crashdata/ contains the files. I've put a > dmesg.out (obvious) as well as the kernel.0, vmcore.0 and kernel.debug > there, if anyone would like to run it through gdb themselves > (***WARNING*** vmcore.0 is 128M) (NOTE, the web server does not allow > directory listings, you'll have to access the files directly) > So ... I'm looking for any possible help in straightening this out. > Advice on how to run gdb more effectively is welcome, as well as anyone Hi! In the handbook there is a chapter about how to debug kernels. If you correctly load the symbols-file (kernel.debug), you should be able to "backtrace" and the code resulting the panic occurs (usually *g*). That's a good start to paste here. Thanks Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010621212749.A3281>