From: Bas Mevissen <ml@basmevissen.nl>
To: tevaugha@ball.com, tevaughan@comcast.net
Cc: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
debian-devel@lists.debian.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernel boot crashing
Date: Fri, 13 Feb 2004 16:30:20 +0100 [thread overview]
Message-ID: <402CED8C.4040203@basmevissen.nl> (raw)
In-Reply-To: <20040211213243.GA5133@ball.com>
Thomas E. Vaughan wrote:
> On Wed, Feb 11, 2004 at 04:58:16PM +0000, Matthew Garrett
> wrote:
>
>>Thomas E. Vaughan wrote:
>>
>>
>>>PnPBIOS: PnP BIOS version 1.0, entry 0xf000:0x6d5a, dseg 0xf000
>>>general protection fault: 0000 [#1]
>>
>>There have been problems with PnP BIOS support on various
>>motherboards. Try rebuilding the kernel package without
>>PNPBIOS support (you probably don't need it - it's there
>>in order to manage resource allocation for legacy hardware
>>like serial ports, and in most cases the BIOS will happily
>>set those up on its own) and see if that works.
>
>
> That did the trick. The only config option that matters is
>
> "Plug and Play BIOS support (EXPERIMENTAL)",
>
> which must *not* be selected. I noticed that the top-level
>
> "Plug and Play support"
>
> and also
>
> "ISA Plug and Play support (EXPERIMENTAL)"
>
> can be selected, and the kernel still boots OK. But that
> PnPBIOS support crashes the kernel hard.
>
I can confirm that on an Asus P4P800 Deluxe motherboard too for at least
kernel 2.6.0 and 2.6.1.
Setting the command line option pnpbios=off is a good fix for people who
would like to run a pre-compiled kernel on those mainboards.
Regards,
Bas.
prev parent reply other threads:[~2004-02-13 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040211154044.GA656@ball.com>
[not found] ` <E1Aqxgm-0005G4-00@chiark.greenend.org.uk>
2004-02-11 21:32 ` 2.6 kernel boot crashing Thomas E. Vaughan
2004-02-13 15:30 ` Bas Mevissen [this message]
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=402CED8C.4040203@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=debian-devel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=tevaugha@ball.com \
--cc=tevaughan@comcast.net \
/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.