From: "Terry Katz" <katz@advanced.org>
To: "'Linux Kernel'" <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.[35] + Dell Poweredge 8450 + Oops on boot
Date: Fri, 1 Jun 2001 11:03:10 -0400 [thread overview]
Message-ID: <005b01c0eaab$f913b760$21efd3d1@advanced.org> (raw)
In-Reply-To: <E155prL-0000aH-00@the-village.bc.nu>
Just before I got your suggestion, I tried just that (disabling the PNP
Bios) .. I looked up the trace addresses in the system.map (which I
forgot to include) and saw that it was from the pnp bios) .. It did the
trick :) I will also see if there's an updated bios available ..
Thanks!
Terry
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Alan Cox
> Sent: Friday, June 01, 2001 10:25 AM
> To: Terry Katz
> Cc: Linux Kernel
> Subject: Re: 2.4.[35] + Dell Poweredge 8450 + Oops on boot
>
>
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > PnP: PNP BIOS installation structure at 0xc00f68f0
> > PnP: PNP BIOS version 1.0, entry at f0000:a611, dseg at 400
> Unable to
> > handle kernel paging request at virtual address 0000ff48 printing
> > eip: 00003c9c *pde = 00000000
> > Oops: 0002
> > CPU: 0
> > EIP: 0068:[<00003c9c>]
>
> Your Pnp BIOS crahsed somewhere in the BIOS when we called it
> - Disable PnP bios support or get a bios update
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-06-01 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 14:09 2.4.[35] + Dell Poweredge 8450 + Oops on boot Terry Katz
2001-06-01 14:25 ` Alan Cox
2001-06-01 15:03 ` Terry Katz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-01 14:22 Matt_Domsch
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='005b01c0eaab$f913b760$21efd3d1@advanced.org' \
--to=katz@advanced.org \
--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.