linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "S. Kurt Newman" <knewman@globaldataguard.com>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Cc: linux-admin@vger.kernel.org
Subject: Re: 2.6.32.1 kernel configuration only seeing 1 core on Intel E5540 CPU
Date: Thu, 24 Jun 2010 08:39:11 -0500	[thread overview]
Message-ID: <4C235FFF.9030603@globaldataguard.com> (raw)
In-Reply-To: <201006240943.38529.carsten.aulbert@aei.mpg.de>

Hi Carsten.

Yes, the custom kernel is a 32-bit variant.  However, the Ubuntu and 
CentOS systems I loaded are also 32-bit.  Or so I think they are... I 
don't recall explicitly downloading the 64-bit variations of those OSs.

As far as using .1 instead of .15, I can try using a more recent 
revision to help fix bugs that may exist.. however due to some OS 
constraints I don't think I can go that far.  At least not without using 
custom patches.

For poserity's sake, let's assume all kernels I've used are 32-bit.  How 
would the 2.6.28 (and 2.6.18) kernels support them, but the 2.6.32 that 
I'm using wouldn't?

Thanks,
Kurt

Carsten Aulbert wrote:
> Hi Kurt
> 
> On Thursday 24 June 2010 00:53:46 Kurt Newman wrote:
>> I've loaded this same i7 Nehalem machine with CentOS 5.3
>> (2.6.18-128.el5PAE), Ubuntu 9.04 (2.6.28-11-generic), and a modified
>> distro with a custom kernel (2.6.32.1).
>>
>> The CentOS and Ubuntu kernels find all 4 cores just fine; however, my
>> custom kernel only finds 1.  I've enabled the following:
>>
>>  - SMP
>>  - X86_BIGSMP (systems with more than 8 cpus)
>>  - X86_EXTENDED_PLATFORM (extended x86 platform)
>>  - SCHED_SMT (hyper-threading)
>>  - SCHED_MC (Multi-core scheduler)
>>  - and varied between M686 (Pentium Pro) and MCORE2 (newer Xeon)
> 
> Just guessing, but could the CentOS and Ubuntu Kernel be a 64bit variant, 
> while your custom one is 32bit? (also .1 is heavily outdated .15 is the 
> current which apparently fixes several bugs).
> 
> I've not been using 32bit kernel for a couple of years and never with a multi-
> core system thus just poking into the dark here.
> 
> HTH
> 
> Carsten
> --
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2010-06-24 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 22:53 2.6.32.1 kernel configuration only seeing 1 core on Intel E5540 CPU Kurt Newman
2010-06-24  7:43 ` Carsten Aulbert
2010-06-24 13:39   ` S. Kurt Newman [this message]
2010-06-25 21:54   ` 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=4C235FFF.9030603@globaldataguard.com \
    --to=knewman@globaldataguard.com \
    --cc=carsten.aulbert@aei.mpg.de \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).