From: Len Brown <len.brown@intel.com>
To: Hod McWuff <hod@wuff.dhs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HT CPU handling - 2.6.2
Date: 10 Feb 2004 02:23:23 -0500 [thread overview]
Message-ID: <1076397803.4105.900.camel@dhcppc4> (raw)
In-Reply-To: <1076395641.2246.5.camel@siberian.wuff.dhs.org>
no. the disabled flag is a reflection of wires inside the processor.
You could pop the cap and ion-beam edit the die, or buy an HT-enabled
processor. The later would be somewhat more cost effective;-)
cheers,
-Len
On Tue, 2004-02-10 at 01:47, Hod McWuff wrote:
> OK, the BIOS setting is disabled and cannot be changed, so the message
> won't get cleaned up that way. I could of course disable SMP in my
> kernel, but that really doesn't address anything.
>
> What I'm wondering is, if the second "CPU" appears to exist but is
> merely marked disabled, who cares about the BIOS flag? Why couldn't the
> disable flag be cleared or ignored?
>
> Couldn't the ACPI/APIC/SMP code just cope with the odd LAPIC ID somehow?
>
> On Tue, 2004-02-10 at 00:37, Len Brown 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.
> >
> > I'm thinking that ACPI should not register a processor that the BIOS
> > marked as disabled...
> >
> > 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.
> >
> > cheers,
> > -Len
> >
> > On Mon, 2004-02-09 at 15:44, Hod McWuff wrote:
> > > I've got a 2.0A GHz P4, advertised as non-hyperthread, that seems to
> > > be
> > > reporting the presence of a second CPU. It also seems to be disabled
> > > by
> > > setting bit 7 of its ID. I've tried compiling with support for 130
> > > CPU's
> > > and nothing changed. What would have to be done to get this disabled
> > > CPU half back online?
> > >
> > > Feb 9 04:45:03 pug ACPI: Local APIC address 0xfee00000
> > > Feb 9 04:45:03 pug ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> > > Feb 9 04:45:03 pug Processor #0 15:2 APIC version 20
> > > Feb 9 04:45:03 pug ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81]
> > > disabled)
> > > Feb 9 04:45:03 pug Processor #129 invalid (max 16)
> > > Feb 9 04:45:03 pug ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> > > Feb 9 04:45:03 pug ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe
> > > linux-kernel" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at http://www.tux.org/lkml/
> > >
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-02-10 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2004-02-10 8:48 ` Hod McWuff
2004-02-19 18:34 ` Pavel Machek
[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] <1nyMT-4MT-11@gated-at.bofh.it>
[not found] ` <1nyMT-4MT-9@gated-at.bofh.it>
2004-02-10 7:28 ` Athol Mullen
-- 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=1076397803.4105.900.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=hod@wuff.dhs.org \
--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®