Re: pnpbios oops on boot w/ 2.5.47

[Adam Belay <ambx1@neo.rr.com>]

On Sun, Nov 17, 2002 at 01:00:53AM -0500, Justin A wrote:
> On Saturday 16 November 2002 06:25 pm, Adam Belay wrote:
> 
> > Oops.  I put the pnpbios_kmalloc in the wrong place.  It's amazing it still
> > worked on my test box.  Here's a patch that should fix it.  Justin: could
> > you please try it.
> >
> > Thanks,
> > Adam
> I had a fealing that call_pnp_bios was doing something with data so I tried it 

> anyway with:
> 
> CONFIG_PNP=y
> CONFIG_PNP_NAMES=y
> CONFIG_PNP_DEBUG=y
> CONFIG_ISAPNP=y
> CONFIG_PNPBIOS=y
> 
> and it booted ok.  You were right, it was a serial port(even though that port 
> always worked without pnp:))
> 
> I didn't have NAMES and DEBUG on before, so hopefully neither of those is what 

> fixed it in this case.
> 
> Here is the new dmseg, you can ignore the crap at the end, thats just pcmcia
> being broken, it goes away if I move /l/m/2/k/d/pcmcia out of the way.
>
> --
> -Justin


> pnp: the driver 'serial' has been registered
> pnp: pnp: match found with the PnP device '00:13' and the driver 'serial'
> pnp: the device '00:13' has been activated
> PnPBIOS: set_dev_node: Unexpected status 0x85

Hmm, this isn't right.  0x85 means unable to set resources.  If you have it 
could you please send me a copy of the output of lspnp for node 13.  I'm not
sure what this device is, do you have a second serial port?

Thanks,
Adam