From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: john slee <indigoid@higherplane.net>,
"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: booting SMP P6 kernel on P4 hangs.
Date: Fri, 3 Aug 2001 21:10:46 +1200 [thread overview]
Message-ID: <20010803211046.A16299@weta.f00f.org> (raw)
In-Reply-To: <20010803000043.F1183@higherplane.net> <E15SJnZ-0000lB-00@the-village.bc.nu>
In-Reply-To: <E15SJnZ-0000lB-00@the-village.bc.nu>
On Thu, Aug 02, 2001 at 03:50:05PM +0100, Alan Cox wrote:
Which gives intel plenty of time to fix their bios problems. Right
now the situation is we are seeing Pentium IV boxes reporting
invalid MP 1.4 specs and dying. Reporting an invalid MP spec and
booting single user at least ensures people can boot their boxes
while intel fixes their problems
I assume these things, even with busted MP tables will work under
Win2k as it will use ACPI tables instead (I'm assuming they are
available abd valid?).
What about NT4? If that can also use ACPI tables (I can't see how, it
predates ACPI I think) then it may well be Linux is the only thing
that stil uses MP tables and hence won't boot in such machines :(
--cw
next prev parent reply other threads:[~2001-08-03 9:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 6:10 booting SMP P6 kernel on P4 hangs Tigran Aivazian
2001-07-31 17:57 ` Linus Torvalds
2001-08-01 9:39 ` Arjan van de Ven
2001-08-01 9:47 ` Tigran Aivazian
2001-08-01 11:49 ` Maciej W. Rozycki
2001-08-02 12:30 ` Alan Cox
2001-08-02 14:00 ` john slee
2001-08-02 14:50 ` Alan Cox
2001-08-03 9:10 ` Chris Wedgwood [this message]
2001-08-03 8:50 ` Steffen Persvold
2001-08-01 16:18 ` Linus Torvalds
2001-08-02 0:51 ` Alan Cox
2001-08-03 10:48 ` Mark Hemment
2001-08-06 14:48 ` Maciej W. Rozycki
2001-08-06 15:08 ` Mark Hemment
-- strict thread matches above, loose matches on Subject: below --
2001-07-31 10:45 Mikael Pettersson
2001-08-01 16:00 Petr Vandrovec
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=20010803211046.A16299@weta.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
/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