[lkml]   [2002]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.4 PNPBIOS fault
On 19 Feb 2002, Thomas Hood wrote:

| On Tue, 2002-02-19 at 18:05, Randy.Dunlap wrote:
| > Linux 2.5.4 with CONFIG_PNPBIOS=y and "pnpbios=off" oopses
| > in ahc_linux_isr() (or near there, according to the
| > file).
| Well, that tells us a lot, because with "pnpbios=off"
| the init routine returns immediately without calling
| the BIOS. It would appear that this isn't a PnP BIOS
| coding bug, but something subtle.

I didn't suggest that this was a PnP BIOS coding bug, but
a bug in the _called_ PnP BIOS (i.e., maybe it needs
to be blacklisted / "pnp_bios_is_utter_crap = 1" from
DMI tables).

I agree that this particluar SCSI driver has some
problems, but they didn't show up in the bug report that I
posted. However, this was in the bug report:

| PnPBIOS: Found PnP BIOS installation structure at 0xc00f6010.
| PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xb4a6, dseg 0x400.
| Unable to handle kernel paging request at virtual address 0000de3a
| printing eip:
| 00004298

Does that dseg value of 0x400 and eip value of 0x4298 give us
any clues/hints?

More info:

Booting with "pnpbios=no-res" or with "pnpbios=no-curr"
causes the same system hang (Oops) as in the original
email report. [Note *differences* in "no-res" and "no-curr"
vs. "nores" and "nocurr". Reading the source helps. :]


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.036 / U:6.308 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site