From: Micha Feigin <michf@post.tau.ac.il>
To: linux-kernel@vger.kernel.org
Cc: Adam Belay <ambx1@neo.rr.com>, Micha Feigin <michf@post.tau.ac.il>
Subject: Re: PNP depends on ISA ? (2.6.2-rc2
Date: Thu, 29 Jan 2004 01:16:33 +0200 [thread overview]
Message-ID: <20040128231633.GF3975@luna.mooo.com> (raw)
In-Reply-To: <20040126161746.GA3180@neo.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
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
>
[-- Attachment #2: dump.txt --]
[-- Type: text/plain, Size: 662 bytes --]
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 #3: dmi_data.bz2 --]
[-- Type: application/octet-stream, Size: 2949 bytes --]
next prev parent reply other threads:[~2004-01-28 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 19:31 PNP depends on ISA ? (2.6.2-rc2 Micha Feigin
2004-01-26 16:17 ` Adam Belay
2004-01-26 23:15 ` David Sanders
2004-01-26 18:37 ` Adam Belay
2004-01-28 23:16 ` Micha Feigin [this message]
2004-01-30 0:29 ` Adam Belay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040128231633.GF3975@luna.mooo.com \
--to=michf@post.tau.ac.il \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.