From: Robert Hancock <hancockr@shaw.ca>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dual Xeon hyperthread system only showing up as 2 cpus
Date: Wed, 15 Aug 2007 17:35:14 -0600 [thread overview]
Message-ID: <46C38DB2.9040400@shaw.ca> (raw)
In-Reply-To: <fa.5IVbZBqVHBgyu8BpsYPjQ9pqQ5M@ifi.uio.no>
Chris Friesen wrote:
>
> Hi all,
>
> I've got a system that has two hyperthread-capable Xeons. If I boot it
> with 2.6.10 it shows up as 4 cpus, but with 2.6.14 it only shows 2 cpus.
>
> The relevent boot logs are:
>
> 2.6.10:
>
> DMI 2.3 present.
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> Processor #0 15:2 APIC version 20
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
> Processor #6 15:2 APIC version 20
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
> Processor #1 15:2 APIC version 20
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
> Processor #7 15:2 APIC version 20
> Using ACPI for processor (LAPIC) configuration information
> Intel MultiProcessor Specification v1.4
> Virtual Wire compatibility mode.
> <snip>
> Processors: 4
>
>
> 2.6.14:
>
> DMI 2.3 present.
> Intel MultiProcessor Specification v1.4
> Virtual Wire compatibility mode.
> OEM ID: INTEL Product ID: KingsCanyonC APIC at: 0xFEE00000
> Processor #0 15:2 APIC version 20
> Processor #6 15:2 APIC version 20
> <snip>
> Processors: 2
You snipped the important part of the log. It's not using ACPI in 2.6.14
for some reason, which you need for HT to be detected. Either you didn't
configure it in or it's failed to enable somehow. Please post the entire
dmesg.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-08-15 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.5IVbZBqVHBgyu8BpsYPjQ9pqQ5M@ifi.uio.no>
2007-08-15 23:35 ` Robert Hancock [this message]
2007-08-16 16:54 ` dual Xeon hyperthread system only showing up as 2 cpus Chris Friesen
2007-08-15 23:17 Chris Friesen
2007-08-16 0:07 ` Arjan van de Ven
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=46C38DB2.9040400@shaw.ca \
--to=hancockr@shaw.ca \
--cc=cfriesen@nortel.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