From owner-freebsd-alpha Wed Feb 26 14:15:22 2003 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26CC637B401 for ; Wed, 26 Feb 2003 14:15:20 -0800 (PST) Received: from eos.telenet-ops.be (eos.telenet-ops.be [195.130.132.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA31B43F75 for ; Wed, 26 Feb 2003 14:15:18 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id A03EE20009 for ; Wed, 26 Feb 2003 23:15:17 +0100 (CET) Received: from fortuna.home.paeps.cx (D5768746.kabel.telenet.be [213.118.135.70]) by eos.telenet-ops.be (Postfix) with ESMTP id 85E001FFE2 for ; Wed, 26 Feb 2003 23:15:17 +0100 (CET) Received: from juno.home.paeps.cx (juno.home.paeps.cx [2001:ab8:2007:0:240:f4ff:fe31:3090]) by fortuna.home.paeps.cx (Postfix) with ESMTP id 8D52A20ED for ; Wed, 26 Feb 2003 23:15:27 +0100 (CET) Received: by juno.home.paeps.cx (Postfix, from userid 1001) id 65B05124E; Wed, 26 Feb 2003 23:15:16 +0100 (CET) Date: Wed, 26 Feb 2003 23:15:16 +0100 From: Philip Paeps To: alpha@FreeBSD.ORG Subject: Re: Panic on boot? Message-ID: <20030226221516.GB1930@juno.home.paeps.cx> Mail-Followup-To: alpha@FreeBSD.ORG References: <20030226211435.GB627@juno.home.paeps.cx> <15965.12175.390447.175953@grasshopper.cs.duke.edu> <20030226220020.GA1930@juno.home.paeps.cx> <15965.14869.445380.268641@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <15965.14869.445380.268641@grasshopper.cs.duke.edu> X-Date-in-Rome: ante diem IV Kalendas Martias MMDCCLVI ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Mutt: User-Agent: Mutt/1.5.3i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2003-02-26 17:05:09 (-0500), Andrew Gallatin wrote: > Philip Paeps writes: > > I was doing that as I wrote my message. Unfortunately, the compiler takes > > quite a bit longer to compile an Alpha kernel than I need to type a short > > message :-) > > And it was totally useless advice, because the PC is zero. sorry! Not to worry :-) > Something followed a null function pointer. Eek! So that's what that message means. Is there a 'quick primer on debugging kernels' somewhere to be found? I would find that _very_ interesting literature! > > pc = 0x0 > > ra = 0xfffffc000038a7cc > > Can you please find the ra? fffffc000038a390 T ata_dmastop fffffc000038a5f0 t ata_dmastatus fffffc000038a690 T atapi_attach fffffc000038a860 T atapi_detach fffffc000038a9b0 T atapi_queue_cmd fffffc000038ac10 T atapi_start fffffc000038ac60 T atapi_transfer > If you have a kernel.debug, do > > % gdb kernel.debug > <...> > (gdb) l *0xfffffc000038a7cc Building one of those would take slightly longer than just adding DDB and DDB_TRACE, I think :) > If you don't have a kernel.debug, do an "nm -n /boot/kernel/kernel | less" > and look for the address range that 0xfffffc000038a7cc is in. The exact address wasn't there, but I pasted everything that was 'mathematically' around it above. Hope that helps! - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. The only game that can't be fixed is peek-a-boo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message