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?
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_
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 majo...@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message