From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Shaun Q" <shaun@c-think.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual cores on Core2Duo not detected?
Date: Mon, 13 Nov 2006 15:00:39 +0100 [thread overview]
Message-ID: <9a8748490611130600m3b63349eu53b437da5c75a775@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSO.4.64.0611122322060.30536@ref.nmedia.net>
On 13/11/06, Shaun Q <shaun@c-think.com> wrote:
> Hi there everyone --
>
> I'm trying to build a custom kernel for using both cores of my new
> Core2Duo E6600 processor...
>
> I thought this was simply a matter of enabling the SMP support in the
> kernel .config and recompiling, but when the kernel comes back up, still
> only one core is detected.
>
> With the default vanilla text-based SuSE 10.1 install, it does find both
> cores...
>
> Anyone have any pointers for me on what I might be missing?
>
This is probably not your problem, but it could be, so worth checking.
Are you booting with maxcpus=1 on your kernel commandline?
Another thing could be that you need to set CONFIG_NR_CPUS to
something more than 2. at least in the past some people observed that
depending on hov CPUs/cores got numbered CONFIG_NR_CPUS needed to be
set at least as high as the highest numbered core. Try setting it to 8
and see if that makes a difference.
On a related note; you probably also want to enable CONFIG_SCHED_MC in
addition to just SMP support.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-11-13 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 7:24 Shaun Q
2006-11-13 13:46 ` Stephen Clark
2006-11-13 15:52 ` Shaun Q
2006-11-13 16:03 ` Jesper Juhl
2006-11-13 16:17 ` Shaun Q
2006-11-13 16:27 ` Arjan van de Ven
2006-11-13 16:33 ` Stephen Clark
2006-11-13 16:57 ` Shaun Q
2006-11-13 14:00 ` Jesper Juhl [this message]
2006-11-13 15:54 ` Shaun Q
2006-11-13 14:44 ` Mark Lord
2006-11-13 15:51 ` Shaun Q
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=9a8748490611130600m3b63349eu53b437da5c75a775@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaun@c-think.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®