From: Ingo Molnar <mingo@elte.hu>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
David Miller <davem@davemloft.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs
Date: Wed, 13 Aug 2008 19:39:40 +0200 [thread overview]
Message-ID: <20080813173940.GA32214@elte.hu> (raw)
In-Reply-To: <b6a2187b0808131033m25a7e147x98235a48abd3eb3c@mail.gmail.com>
* Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Thu, Aug 14, 2008 at 1:10 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> > On Wed, Aug 13, 2008 at 10:16 PM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> >> btw., could you please check that v2.6.27-rc3 (or later) kernels boot
> >> fine (with about 8 cpus) even if you have genericarch/bigsmp disabled,
> >> and do not silently hang as it happened on your box before?
> >
> > With 16 CPUs, it still hangs, but now the console is showing the
> > errors as intended.
> > ... but it is supposed to hang?
>
> I tried with just CONFIG_NR_CPUS=8 and this time it booted, but stange
> thing is I only see 2 CPUs! To be more precise, it's without both
> CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
>
> And when I tried to enable the CPUs, it complained about:
>
> # cat cpu6/online
> 0
> # echo 1 > cpu6/online
> More than 8 CPUs detected - skipping them.
> Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
> -bash: echo: write error: Input/output error
>
> Prior to the patch, the system booted with all 8 CPUs.
>
> Again, if I enable both CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP,
> I get all 16 CPUs.
Yinghai, could the APIC ID enumeration be nonsequential and we skip CPUs
starting at the third one already? I think we should accept all CPUs
that are within our support range.
Ingo
next prev parent reply other threads:[~2008-08-13 17:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 11:09 2.6.27rc1 cannot boot more than 8CPUs Jeff Chua
2008-08-06 16:13 ` Yinghai Lu
2008-08-06 16:34 ` Jeff Chua
2008-08-11 19:54 ` Ingo Molnar
2008-08-13 14:16 ` Ingo Molnar
2008-08-13 17:10 ` Jeff Chua
2008-08-13 17:33 ` Jeff Chua
2008-08-13 17:39 ` Ingo Molnar [this message]
2008-08-13 17:46 ` Yinghai Lu
2008-08-13 18:33 ` Yinghai Lu
2008-08-14 7:16 ` Jeff Chua
2008-08-14 8:59 ` Yinghai Lu
2008-08-14 9:07 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-08-15 10:34 Jeff Chua
2008-08-15 14:07 ` Ingo Molnar
2008-08-18 3:07 ` Jeff Chua
2008-08-18 8:00 ` Ingo Molnar
2008-08-06 3:15 Jeff Chua
2008-08-06 3:31 ` Max Krasnyansky
2008-08-06 3:50 ` Jeff Chua
2008-08-06 3:54 ` Max Krasnyansky
2008-08-06 4:06 ` Jeff Chua
2008-08-06 4:48 ` Max Krasnyansky
2008-08-06 4:53 ` Li Zefan
2008-08-06 20:11 ` Max Krasnyansky
[not found] ` <86802c440808052050u489264beo30812523669ef4df@mail.gmail.com>
2008-08-06 4:05 ` Jeff Chua
2008-08-06 5:19 ` David Miller
2008-08-06 6:42 ` Jeff Chua
2008-08-06 7:18 ` David Miller
2008-08-06 9:33 ` Jeff Chua
2008-08-06 9:36 ` David Miller
2008-08-06 9:50 ` Jeff Chua
2008-08-06 8:49 ` Yinghai Lu
2008-08-06 9:35 ` Jeff Chua
2008-08-06 9:42 ` Jeff Chua
2008-08-06 6:01 ` Linus Torvalds
2008-08-06 6:42 ` Jeff Chua
2008-08-06 15:33 ` Jeff Chua
2008-08-11 19:59 ` Ingo Molnar
2008-08-11 20:03 ` Yinghai Lu
2008-08-11 20:08 ` Ingo Molnar
2008-08-11 20:12 ` Yinghai Lu
2008-08-11 20:36 ` Yinghai Lu
2008-08-11 20:44 ` Ingo Molnar
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=20080813173940.GA32214@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.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 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.