Re: PNP depends on ISA ? (2.6.2-rc2

From: Micha Feigin
Date: Wed Jan 28 2004 - 18:21:31 EST


On Mon, Jan 26, 2004 at 04:17:46PM +0000, Adam Belay wrote:
> On Mon, Jan 26, 2004 at 09:31:44PM +0200, Micha Feigin wrote:
> > I was wondering why pnp depends on isa being selected in 2.6.2-rc2, is
> > pnp really only relevant to isa? What happens with pci etc. ?
> > This may explain why using pnpbios locks up my machine (at least as of 2.6.0-test9).
>
> Yes, it only is related to isa devices, but they include onboard devices
> such as serial ports. It will, however, prevent resource conflicts
> between pci and system devices, especially with unusual configurations.
> Does using pnpbios cause your machine to lockup at boot? If so, around
> where does it occur? DMI information would also be useful for blacklisting
> purposes.
>

I just checked again with 2.6.2-rc2. It occurs right after pnpbios
starts up. I wrote the oops down by hand since the computer went into a
hard lockup (no sysrq key), but couldn't get any results out of
ksymoops for some reason (maybe I am misusing it, any way to disable
pnpbios on a kernel compiled with so I can run it from the running
kernel?).
I attached the oops log and the dmi data (didn't know what is needed of
it).

> Thanks,
> Adam
>
pnpbios: scanning system for pnpbios support ...
pnpbios: found pnp bios instellation structure at 0xc00f7760
pnpbios: pnp bios version 1.0, entry 0xf0000:0xaad2, dseg 0x400
general protection fault: 0000 [#1]
cpu: 0
eip: 0098:[<00003fb8>] not tainted
eflags: 00010082
eip is at 3fb8
[...]
process swapper (pid: 1, threadinfo=cffa8000 task=cffa38c0)
stack: 00001002 0002000f 556a0000 8d350000 541c0000 8d2fc65c c64d0c40 0000005a
9e829e96 00008d2e 020b000f 0000bade 9231cc70 cc70c520 003fcbad 00010000
67df0000 0007c020 02120000 1f0e0000 50000000 0000c129 ff380000 0246c037
call trace:

code: bad eip value
<0> kernel panic: attempted to kill init!

Attachment: dmi_data.bz2
Description: Binary data