From owner-freebsd-hackers Thu Jun 21 12:27:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 58A4837B401 for ; Thu, 21 Jun 2001 12:27:51 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id VAA06092; Thu, 21 Jun 2001 21:27:50 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 3290314D10; Thu, 21 Jun 2001 21:27:49 +0200 (CEST) Date: Thu, 21 Jun 2001 21:27:49 +0200 From: Alexander Langer To: Bill Moran Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PANIC - 4.3-STABLE, suspecting ata controller Message-ID: <20010621212749.A3281@zerogravity.kawo2.rwth-aachen.d> References: <3B322B93.20994E19@iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B322B93.20994E19@iowna.com>; from wmoran@iowna.com on Thu, Jun 21, 2001 at 01:14:59PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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