ahd(4) reliable panic

[Justin T. Gibbs]

On May 31, 2013, at 9:12 AM, Sean Bruno <sean_bruno at yahoo.com> wrote:

> ports building seems to be able to panic ahd(4) pretty reliably.
> 
> 
>> db> whe
>> Tracing pid 12 tid 100040 td 0xfffffe0015b53000
>> ahd_freeze_devq() at ahd_freeze_devq+0x16/frame 0xffffff800039da60
>> ahd_handle_seqint() at ahd_handle_seqint+0xf11/frame 0xffffff800039db00
>> ahd_platform_intr() at ahd_platform_intr+0x242/frame 0xffffff800039db20
>> intr_event_execute_handlers() at intr_event_execute_handlers+0xfd/frame 0xffffff800039db50
>> ithread_loop() at ithread_loop+0x9b/frame 0xffffff800039dba0
>> fork_exit() at fork_exit+0x11f/frame 0xffffff800039dbf0
>> fork_trampoline() at fork_trampoline+0xe/frame 0xffffff800039dbf0
>> --- trap 0, rip = 0, rsp = 0xffffff800039dcb0, rbp = 0 ---
> 
> This looks like a symptom that was reported in a lot of PR reports.  
> 
> I'm assuming that I need more information?
> 
> Sean

The panic string would be useful.  So might the msgbuf output.

--
Justin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20130531/e2bb53aa/attachment.sig>