From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"David Miller" <davem@davemloft.net>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs
Date: Thu, 14 Aug 2008 15:16:58 +0800 [thread overview]
Message-ID: <b6a2187b0808140016m63c7d9d9s960014ec5cd9f3c5@mail.gmail.com> (raw)
In-Reply-To: <86802c440808131133o133e1dfftdfcc076a1100afb6@mail.gmail.com>
On Thu, Aug 14, 2008 at 2:33 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>>>> > With 16 CPUs, it still hangs, but now the console is showing the
>>>> > errors as intended.
>>>> > ... but it is supposed to hang?
> please check the attached patch. it should fix the new regression and
> will not hang.
Ok, booted up and not hanged, but those messages below don't show up
anywhere. I've tested with CONFIG_NR_CPUS=16 and 8 as well. Just got 8
cpus
More than 8 CPUs detected - skipping them.
Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
# cat /sys/devices/system/cpu/possible
0-7
CONFIG_X86_32=y
CONFIG_X86_PC=y
Looks like it's not going into this condition
+ if (def_to_bigsmp && nr_cpu_ids > 8) {
Shall this be put back so that it'll show the message?
- if (def_to_bigsmp && apicid > 8) {
- printk(KERN_WARNING
- "More than 8 CPUs detected - skipping them.\n"
- "Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.\n");
- }
Thanks,
Jeff.
next prev parent reply other threads:[~2008-08-14 7:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 11:09 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
2008-08-13 17:46 ` Yinghai Lu
2008-08-13 18:33 ` Yinghai Lu
2008-08-14 7:16 ` Jeff Chua [this message]
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=b6a2187b0808140016m63c7d9d9s960014ec5cd9f3c5@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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®