From: Kurt Newman <knewman@globaldataguard.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.32.1 kernel unable to use more than 2 of 16 CPUs on Intel E5540 (i7)
Date: Fri, 25 Jun 2010 16:51:15 -0500 [thread overview]
Message-ID: <4C2524D3.9070509@globaldataguard.com> (raw)
In-Reply-To: <adahbksqe71.fsf@roland-alpha.cisco.com>
Roland Dreier wrote:
> Your config seems to have CONFIG_PM and therefore CONFIG_ACPI disabled.
> So the kernel is relying on mptable information. Unsurprisingly on a
> modern system, that info is probably broken -- since everything would
> have been tested with ACPI.
>
> Try turning on CONFIG_ACPI and see if that helps at all.
Turning on ACPI solved the problem. I don't understand why ACPI needs
to be turned on, but after reading the power management ldp it confirms
what you said. I just didn't think that this would have mattered.
Thanks for the help,
Kurt
For anyone else with this problem, here's something to read:
Some SMP system manufacturers may have omitted the pre-ACPI tables used
for SMP configurations. In this case, ACPI is required.
If you have a newer system that supports Hyper-Threading, you will need
to enable ACPI (and, of course, SMP). Without it, your Linux system may
be unable to discover and initialize all of the virtual processors.
IA64 machines require ACPI as well. Additionally, NUMA servers are
starting to require it for proper initialization.
Source: http://tldp.org/HOWTO/Battery-Powered/powermgm.html#HYPERTHREAD
prev parent reply other threads:[~2010-06-25 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 21:45 Kurt Newman
2010-06-24 22:05 ` Roland Dreier
2010-06-25 0:23 ` Robert Hancock
2010-06-25 21:51 ` Kurt Newman [this message]
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=4C2524D3.9070509@globaldataguard.com \
--to=knewman@globaldataguard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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®