From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
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: Thu, 14 Aug 2008 01:10:36 +0800 [thread overview]
Message-ID: <b6a2187b0808131010u7481f663n94d8e005b9dac2d1@mail.gmail.com> (raw)
In-Reply-To: <20080813141629.GD19397@elte.hu>
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?
More than 8 CPUs detected - skipping them.
Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
More than 8 CPUs detected - skipping them.
Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
More than 8 CPUs detected - skipping them.
Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
More than 8 CPUs detected - skipping them.
Use CONFIG_X86_GENERICARCH and CONFIG_X86_BIGSMP.
Booting processor 8/1 ip 6000
Initializing CPU#8
Calibrating delay using timer specific routine.. 3723.88 BogoMIPS (lpj=7447763)
CPU: L1 I cache: 32Kb, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU8: Intel(8) Xeon(R) CPU L7345 @ 1.86GHz stepping 0b
checking TSC synchronization [CPU#0 -> CPU#8]: passed.
*** HANGS HERE ***
Thanks,
Jeff.
next prev parent reply other threads:[~2008-08-13 17:11 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 [this message]
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
-- 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=b6a2187b0808131010u7481f663n94d8e005b9dac2d1@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®