From: Bill Davidsen <davidsen@tmr.com>
To: Hod McWuff <hod@wuff.dhs.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: HT CPU handling - 2.6.2
Date: Tue, 10 Feb 2004 15:33:23 -0500 [thread overview]
Message-ID: <40294013.7000202@tmr.com> (raw)
In-Reply-To: <1nqw6-5W0-25@gated-at.bofh.it>
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])
Look in /proc/cpuinfo for number of siblings. If it's one you have no HT
capability, the stuff for HT is mostly there but there's no sib to
share. Sort of like a Siamese twin who's an only child or some such. You
have a funky APIC and not much else.
Don't know if the LAPIC is actually useful.
--
Bill Davidsen, TMR
next parent reply other threads:[~2004-02-10 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1nqw6-5W0-25@gated-at.bofh.it>
2004-02-10 20:33 ` Bill Davidsen [this message]
2004-02-10 17:04 HT CPU handling - 2.6.2 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
[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=40294013.7000202@tmr.com \
--to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.