Date: Wed, 26 Feb 2003 17:29:30 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Philip Paeps <philip@paeps.cx> Cc: alpha@FreeBSD.ORG, sos@FreeBSD.ORG Subject: ATA Panic on boot Message-ID: <15965.16330.305808.221484@grasshopper.cs.duke.edu> In-Reply-To: <20030226221516.GB1930@juno.home.paeps.cx> 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> <20030226221516.GB1930@juno.home.paeps.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
Soren, This gentleman has an alpha which is panic'ing on boot after the recent round of ata changes. Its apparently following a null function pointer from atapi_attach(). Based on the hardware, he has either a CMD646 or Cypress chipset. Is this enough to go on, or would you like more information? Thanks, Drew Philip Paeps writes: > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15965.16330.305808.221484>