Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 04:48:18AM +0000, mailinglists_at_debank.tv wrote:
> July 31 2015 4:21 PM, "Glen Barber" <gjb_at_freebsd.org> wrote:
> > On Fri, Jul 31, 2015 at 04:18:15AM +0000, Glen Barber wrote:
> > 
> >> On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote:
> >>> On 2015-07-30 17:17, Glen Barber wrote:
> >>>> On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote:
> >>>>> Kernel compiling -- give mr a bit and I'll boot it and make sure it
> >>>>> comes
> >>>>> up.
> >>>>> 
> >>>> 
> >>>> Larry, have you had any luck with this patch applied? If it resolves
> >>>> your issue, I want to make sure it is included in the 10.2-RC2 build.
> >>>> 
> >>>> Thanks.
> >>>> 
> >>> [...]
> >>> 
> >>> There are 3 pictures from the CURRENT panic.
> >>> 
> >>> it STILL fails. :(
> >>> 
> >> 
> >> Larry, I am sorry this is causing headaches for you, and I certainly
> >> appreciate the prompt (and detailed) report, and assistance debugging
> >> this.
> >> 
> >> Would you be able to try one more test case?
> >> 
> >> I'm interested in the behavior without the 'nodevice pmsdrv' addition to
> >> your kernel configuration (effectively, removing the device from the
> >> GENERIC kernel), and *without* the patch provided from Benno?
> > 
> > To be more specific on what I'm interested in, 'nodevice pmsdrv' and
> > 'device pmsdrv' should *both* be removed from the kernel configuration,
> > and the pms(4) should only be available as a .ko module.
> > 
> >> In particular, I'm interested in if ahd(4) attaches or if loader(8)
> >> auto-loads pms(4) after the PCI IDs are detected.
> >> 
> >> As this issue also affects the upcoming 10.2-RELEASE, your willingness
> >> to help debug this is greatly appreciated, as you've tripped over
> >> something that would have caused a great deal of pain after 10.2 was
> >> release.
> >> 
> >> I owe you several beers.
> > 
> 
> Hi All,
> 
> I've experienced the same bug although with a mvs(4) device on 10.2-PRERELEASE, once the pms driver is removed from the kernel config the problem disappears, I haven't had time to try the suggested patch as I only found this thread after removing the pms driver from the kernel.
> 
> 

Thank you for the information (stripped from my reply).

So, to be clear, you have 'device pmsdrv' removed from the kernel
config, but the /boot/kernel/pmspcv.ko is still available to the system?

Glen