From: Len Brown <len.brown@intel.com>
To: Shantanu Goel <Shantanu.Goel@lehman.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ACPI x86_64] 2.6.1-rc{1,2} hang while booting on Sun v20z aka Newisys 2100
Date: 22 Apr 2004 17:01:32 -0400 [thread overview]
Message-ID: <1082667692.16337.400.camel@dhcppc4> (raw)
In-Reply-To: <40882E49.2040705@lehman.com>
On Thu, 2004-04-22 at 16:42, Shantanu Goel wrote:
> >>Intel MultiProcessor Specification v1.4
> >> Virtual Wire compatibility mode.
> >>SMP mptable: bad signature [<3>BIOS bug, MP table errors detected!...
> >>... disabling SMP support. (tell your hw vendor)
> >>
> >>
> >
> >Broken BIOS/MPS tables own this failure.
> >See if you can disable MPS in the BIOS/SETUP.
> >that is, after you verify you've got the latest BIOS...
> >
> >
>
> But that still does not explain why RedHat AS3 works on the same machine
> with the same BIOS settings without specifying any acpi related
> parameters. As far as I can tell, AS3 is using an older version of the
> ACPI code. It reports "ACPI: Subsystem revision 20030619" when
> booting. So barring some hack RedHat has in there, clearly something
> has changed along the way to break things on this machine...
Right, the broken BIOS does not explain that failure.
Perhaps you can enumerate what kernels do boot on this box.
If there is RH special sauce at work, then I'd expect that
none of the kernel.org 2.4 kernels boot either.
-Len
next prev parent reply other threads:[~2004-04-22 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F976F@hdsmsx403.hd.intel.com>
2004-04-22 17:05 ` [ACPI x86_64] 2.6.1-rc{1,2} hang while booting on Sun v20z aka Newisys 2100 Len Brown
2004-04-22 19:45 ` Shantanu Goel
2004-04-22 20:35 ` Len Brown
2004-04-22 20:42 ` Shantanu Goel
2004-04-22 21:01 ` Len Brown [this message]
2004-04-28 8:42 ` Arjan van de Ven
2004-04-22 20:54 ` Shantanu Goel
2004-04-22 14:17 Shantanu Goel
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=1082667692.16337.400.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=Shantanu.Goel@lehman.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox