From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nathaniel <wfilardo@fuse.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] Re: PATCH: 2.5.29 Fix pnpbios
Date: 28 Jul 2002 21:08:52 +0100 [thread overview]
Message-ID: <1027886932.842.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3D4378B2.1000200@fuse.net>
On Sun, 2002-07-28 at 05:53, Nathaniel wrote:
> Alan Cox wrote:
> > This should do the trick for pnpbios - we load the initial gdt into each
> > gdt, and we load the parameters into the gdt of the cpu making the call
> > relying on the spinlock to avoid bouncing cpu due to pre-empt
>
> I get the following (hand-transcribed) oops at bootup on a patched (see below) 2.5.29 on a UP Athlon 900Mhz system with an ASUS K7V (unsure about the V) motherboard.
It blew up making the initial PnPBIOS call. That certainly smells of
incorrectly set up GDT segments. I'll take a look
prev parent reply other threads:[~2002-07-28 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 0:47 Alan Cox
2002-07-28 4:53 ` [OOPS] " Nathaniel
2002-07-28 20:08 ` Alan Cox [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=1027886932.842.9.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=wfilardo@fuse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®