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: Fri, 15 Aug 2008 16:07:02 +0200 [thread overview]
Message-ID: <20080815140702.GD14103@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0808151830170.19924@boston.corp.fedex.com>
* Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>>> 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");
>>> - }
>>
>> could you post the full dmesg? And the modified patch that you've tested
>> to both have 8 CPUs without bigsmp and which also shows the printk?
>>
>> Ingo
>>
>
> Attached. cpu.8
> CONFIG_X86_32=y
> CONFIG_X86_PC=y
> CONFIG_X86=y
> CONFIG_NR_CPUS=8
>
> Attached. cpu.16
> CONFIG_X86_32=y
> CONFIG_X86_PC=y
> CONFIG_X86=y
> CONFIG_NR_CPUS=16
>
> Attached cpu.16.big
> CONFIG_X86_32=y
> CONFIG_X86=y
> CONFIG_X86_GENERICARCH=y
> CONFIG_X86_BIGSMP=y
> # CONFIG_X86_PC is not set
> CONFIG_NR_CPUS=16
>
> Attached cpu.16.nobig (same as cpu.16 except with modifed patch)
> CONFIG_X86_32=y
> CONFIG_X86_PC=y
> CONFIG_X86=y
> CONFIG_NR_CPUS=16
>
> Attached is the modified patch to make the warning appears. It's
> Yinghai's patch modified to just display the error and continue to
> boot.
thanks. To make sure it's all sorted out you might want to boot today's
tip/master and check whether it just does the right thing by default.
(it really should)
Ingo
next prev parent reply other threads:[~2008-08-15 14:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 10:34 2.6.27rc1 cannot boot more than 8CPUs Jeff Chua
2008-08-15 14:07 ` Ingo Molnar [this message]
2008-08-18 3:07 ` Jeff Chua
2008-08-18 8:00 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
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
2008-08-14 8:59 ` Yinghai Lu
2008-08-14 9:07 ` 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=20080815140702.GD14103@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox