From: Andrew Morton <akpm@linux-foundation.org>
To: david@lang.hm
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: only a single core (out of 8) initialized
Date: Thu, 4 Jun 2009 20:29:33 -0700 [thread overview]
Message-ID: <20090604202933.d7c24c3d.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0906041949030.7953@asgard>
On Thu, 4 Jun 2009 19:52:36 -0700 (PDT) david@lang.hm wrote:
> this is 2.6.30-rc7
Were any earlier kernels OK?
> with a patch added to debug a nv sata driver
> incompatibility with the Intel SSDs on a tyan motherboard
>
> on one system it sees all 8 cores, on the other system it only initializes
> one core.
>
> can anyone help me spot what's going wrong in the one that's only seeing a
> single core? If I'm reading things correctly it's seeing both sockets for
> the NUMA setup, but then only initializing one core on the first socket.
good:
SMP: Allowing 8 CPUs, 4 hotplug CPUs
bad:
SMP: Allowing 1 CPUs, 0 hotplug CPUs
perhaps due to
ACPI: No APIC-table, disabling MPS
You could have a poke around in arch/x86/kernel/smpboot.c() and find
out what happened here. I'd be suspecting this code triggered:
/* no processor from mptable or madt */
if (!num_processors)
num_processors = 1;
because ACPI doesn't like that board.
Did you look into updating the BIOS?
next prev parent reply other threads:[~2009-06-05 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 2:52 only a single core (out of 8) initialized david
2009-06-05 3:13 ` Yinghai Lu
2009-06-05 3:29 ` Andrew Morton [this message]
2009-06-05 3:52 ` david
2009-06-06 1:24 ` Robert Hancock
2009-06-05 16:47 ` david
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=20090604202933.d7c24c3d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@lang.hm \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.