mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Newman <knewman@globaldataguard.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.32.1 kernel unable to use more than 2 of 16 CPUs on Intel E5540 (i7)
Date: Thu, 24 Jun 2010 16:45:13 -0500	[thread overview]
Message-ID: <4C23D1E9.9050007@globaldataguard.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm posting here to get a bit of help to figure out this issue, or find
advice on a better mailing list or location to post this question.

The linux-smp and linux-config lists don't get many posts, while
linux-admin hasn't yielded much (perceived) help.

- ------------------------

My problem and question is:

I've tried 2.6.31.13 and 2.6.32.1, but none of these compilations find
all 16 CPUs on this E5540 (2 cpus, 4 cores each, 2 HT threads each).
However, using these same custom kernels on an Intel 5130, shows all 4
"cpus" (2 cpus, 2 cores each, no HT).  I've also tried older kernels
from common distros that find all 16 cpus just fine.  I'm guessing they
patched in support for additional hardware.

Q: What am I doing wrong, that prevents this kernel from seeing all
CPUs?  Or, could someone point me in the right direction?

- ------------------------

Relevant background information:

1) I am limited to a 32-bit OS and an older kernel because of some
software limitations.

2) While I've enabled CONFIG_HOTPLUG_CPU, I've confirmed that I'm not
passing any kernel args that would limit what is used (e.g. maxcpus=).

3) From the things I've looked at (e.g. /sys), the kernel seems to know
that there's 16 CPUs, but will only use 2.

4) I'm attaching my kernel config, dmesg output, /sys output, and
/proc/cpuinfo output to help.  NOTE: I've tried using CONFIG_MCORE2 and
CONFIG_M686, neither of these changes anything.

Thank you for your time,
Kurt

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkwj0eQACgkQ0rcig5YkL7E3vgCghDRO1VXMh9kap1yUhBoOSw7I
UV8An35Zqt7cf3v5vJqKrh43lbYXyqVv
=VLnf
-----END PGP SIGNATURE-----

[-- Attachment #2: config-2.6.32.1_GDG01.gz --]
[-- Type: application/x-gzip, Size: 15245 bytes --]

[-- Attachment #3: cpuinfo-2.6.32.1_GDG01.gz --]
[-- Type: application/x-gzip, Size: 597 bytes --]

[-- Attachment #4: dmesg-2.6.32.1_GDG01.gz --]
[-- Type: application/x-gzip, Size: 15086 bytes --]

[-- Attachment #5: sys-devices-2.6.32.1_GDG01.gz --]
[-- Type: application/x-gzip, Size: 191 bytes --]

             reply	other threads:[~2010-06-24 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 21:45 Kurt Newman [this message]
2010-06-24 22:05 ` Roland Dreier
2010-06-25  0:23   ` Robert Hancock
2010-06-25 21:51   ` Kurt Newman

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=4C23D1E9.9050007@globaldataguard.com \
    --to=knewman@globaldataguard.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

all inboxes | Powered by JetHome®