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: Mon, 18 Aug 2008 10:00:50 +0200 [thread overview]
Message-ID: <20080818080050.GJ30694@elte.hu> (raw)
In-Reply-To: <b6a2187b0808172007u69243abewb357fd8ec4a01e57@mail.gmail.com>
* Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> On Fri, Aug 15, 2008 at 10:07 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> > 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)
>
> Yes, verified and it's working now. The warnings show up.
and the system is up with ~8 cores active [not just 1 or 2], right?
ah, indeed:
> checking TSC synchronization [CPU#0 -> CPU#7]: passed.
> Brought up 8 CPUs
> Total of 8 processors activated (29790.66 BogoMIPS).
great - thanks for testing!
Ingo
next prev parent reply other threads:[~2008-08-18 8:01 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
2008-08-18 3:07 ` Jeff Chua
2008-08-18 8:00 ` Ingo Molnar [this message]
-- 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=20080818080050.GJ30694@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