From: Athol Mullen <athol_SPIT_SPAM@idl.net.au>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: HT CPU handling - 2.6.2
Date: Tue, 10 Feb 2004 18:28:41 +1100 [thread overview]
Message-ID: <200402101828.42001.athol_SPIT_SPAM@idl.net.au> (raw)
In-Reply-To: <1nyMT-4MT-9@gated-at.bofh.it>
Len Brown <len.brown@intel.com> wrote:
> Your BIOS is reporting the 2nd CPU as disabled, and telling us that it
> has LAPIC id 0x81 = 129. The ACPI table code prints this out and
> registers the processor anyway, but that chokes because the LAPIC ID is
> way out of bounds.
IIRC, This is what happens with any P4 that sets the HT flag but only
has one logical CPU. Completely within Intel specs. I spent several
days struggling with this months ago when I thought that the 2.4GHz P4
I've got was HT capable. Then I RTFM...
BTW, IIRC, the BIOS of my machine shows "Local APIC Support" instead of
"Hyperthreading Support" if the CPU installed isn't really HT capable.
> I'm thinking that ACPI should not register a processor that the BIOS
> marked as disabled...
The processor counter should find "logical processors present" is one
and ignore the hardware disabled 2nd logical CPU.
> What should you do? Apparently you've got an HT-enabled platform, BIOS,
> and OS, but do not have an HT-enabled processor. Your choices are to
> disable HT in the BIOS SETUP to clean up this message, or plug in an
> HT-enabled processor.
Better still, enable Local APIC but not SMP or HT when you build a
kernel. That way, you get Local APIC support without SMP kernel.
--
Athol
<http://cust.idl.com.au/athol>
Linux Registered User # 254000
I'm a Libran Engineer. I don't argue, I discuss.
next parent reply other threads:[~2004-02-10 7:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1nyMT-4MT-11@gated-at.bofh.it>
[not found] ` <1nyMT-4MT-9@gated-at.bofh.it>
2004-02-10 7:28 ` Athol Mullen [this message]
[not found] <1nqw6-5W0-25@gated-at.bofh.it>
2004-02-10 20:33 ` Bill Davidsen
2004-02-10 17:04 Brown, Len
[not found] <BF1FE1855350A0479097B3A0D2A80EE0023E8B98@hdsmsx402.hd.intel.com>
2004-02-10 5:37 ` Len Brown
2004-02-10 6:47 ` Hod McWuff
2004-02-10 7:23 ` Len Brown
2004-02-10 8:48 ` Hod McWuff
2004-02-19 18:34 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 20:44 Hod McWuff
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=200402101828.42001.athol_SPIT_SPAM@idl.net.au \
--to=athol_spit_spam@idl.net.au \
--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
all inboxes | Powered by JetHome®