Date: Tue, 1 Sep 2015 13:30:48 -0700 From: Conrad Meyer <cem@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Panic on boot during scan with pmspcv Message-ID: <CAG6CVpUamGe3RurMMeQMqgimeMjwPNzcyf_Oc23ODTnvk6OHMA@mail.gmail.com> In-Reply-To: <1907622.HsVbIIOtmz@ralph.baldwin.cx> References: <CAG6CVpU4dP3jFag8A1fLaYpPwqSeErL54iERL5iFMAKbmW=Bdw@mail.gmail.com> <1907622.HsVbIIOtmz@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin <jhb@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUamGe3RurMMeQMqgimeMjwPNzcyf_Oc23ODTnvk6OHMA>