Re: Panic on boot during scan with pmspcv
> On Sep 1, 2015, at 13:30, Conrad Meyer wrote: > >> On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin wrote: >> Probably pCardInfo is NULL. >> >> Looking at the pms driver source is making my stomach churn, but I don't >> see anything obvious. The field is set during attach, so it shouldn't be >> NULL when the intrhook runs. Do you have any other storage devices on >> this box? If so, I would try to kldload the pms driver after you have >> booted far enough to setup dumps (either that or setup remote kgdb). > > In fact, I don't have any storage devices attached to the PMC > controller on this box. So it's a pretty low priority for me other > than not panicing. I've configured the BIOS to legacy boot and the > issue no longer crops up. > > I just wanted to register the stack and unpleasantness on -CURRENT@ in > case someone else runs into it too and/or PMC is reading and can > diagnose/fix it. If you see something, bug it :)! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Panic on boot during scan with pmspcv
On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin wrote: > Probably pCardInfo is NULL. > > Looking at the pms driver source is making my stomach churn, but I don't > see anything obvious. The field is set during attach, so it shouldn't be > NULL when the intrhook runs. Do you have any other storage devices on > this box? If so, I would try to kldload the pms driver after you have > booted far enough to setup dumps (either that or setup remote kgdb). > In fact, I don't have any storage devices attached to the PMC controller on this box. So it's a pretty low priority for me other than not panicing. I've configured the BIOS to legacy boot and the issue no longer crops up. I just wanted to register the stack and unpleasantness on -CURRENT@ in case someone else runs into it too and/or PMC is reading and can diagnose/fix it. Best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Panic on boot during scan with pmspcv
On Tuesday, August 25, 2015 02:27:42 PM Conrad Meyer wrote: > For some reason, it only crops up on UEFI boot. "Legacy" boot "just works." > > It looks like we're locking a mutex in a struct at NULL. > > (trap) > __mtx_assert+0xdb > agtiapi_cam_action+0x45 > xpt_action_default+0xbe3(?) > scsi_scan_bus+0x1cd > xpt_scanner_thread+0x15c > ... > > > Fault is at 0x18. > > http://i.imgur.com/615PC6b.jpg > > (kgdb) l *(agtiapi_cam_action+0x45) > 0x806d4ef5 is in agtiapi_cam_action > (/usr/src/sys/dev/pms/freebsd/driver/ini/src/agtiapi.c:1818). > > Possibly here? > > 1814 mtx_assert( &(pmcsc->pCardInfo->pmIOLock), MA_OWNED ); Probably pCardInfo is NULL. Looking at the pms driver source is making my stomach churn, but I don't see anything obvious. The field is set during attach, so it shouldn't be NULL when the intrhook runs. Do you have any other storage devices on this box? If so, I would try to kldload the pms driver after you have booted far enough to setup dumps (either that or setup remote kgdb). -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"