From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Banai Zoltan <bazooka@emitel.hu>,
Alexander Viro <viro@math.psu.edu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.30
Date: 02 Aug 2002 13:23:18 +0100 [thread overview]
Message-ID: <1028290998.18309.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208012015291.16391-100000@home.transmeta.com>
On Fri, 2002-08-02 at 04:17, Linus Torvalds wrote:
> If the PNP BIOS panic is new (ie it didn't happen in 2.5.24), can you
> write down the whole panic (and look up the symbols) and send that one to
> Ingo Molnar <mingo@elte.hu>?
>
> That would most likely be due to some of the GDT reorganizations that
> happened for 2.5.30 due to the thread-local-storage patches.
The PnPBIOS gdt setup changes I did are wrong somewhere. If I can get
2.5.30 to actually boot I'll try and track it down. The traces I have
basically go
kernel -> kernel -> kernel -> pnpbios *BANG*
and appear to be jumping to the wrong physical address (ie gdt is
incorrect)
next prev parent reply other threads:[~2002-08-02 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 21:30 Linus Torvalds
2002-08-01 23:32 ` Banai Zoltan
2002-08-02 0:12 ` Alexander Viro
2002-08-02 0:38 ` Banai Zoltan
2002-08-02 3:17 ` Linus Torvalds
2002-08-02 12:23 ` Alan Cox [this message]
2002-08-02 16:57 ` Thomas Molina
2002-08-02 21:29 ` Linus Torvalds
2002-08-03 5:16 ` Nathaniel
2002-08-02 1:25 ` Linux 2.5.30: [SERIAL] build fails at 8250.c Axel Siebenwirth
2002-08-02 17:13 ` Russell King
2002-08-02 19:19 ` Axel Siebenwirth
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 1:36 Linux 2.5.30 Douglas Gilbert
2002-08-02 6:37 ` James Simmons
2002-08-01 3:30 Ivan Gyurdiev
2002-08-02 6:03 ` James Simmons
2002-08-02 11:29 ` Helge Hafting
2002-08-02 14:32 ` James Simmons
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=1028290998.18309.9.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bazooka@emitel.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®