From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Theurer <habanero@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: CPU boot problem on 2.6.0-test3-bk8
Date: Thu, 21 Aug 2003 14:04:49 -0700 [thread overview]
Message-ID: <20030821210449.GH4306@holomorphy.com> (raw)
In-Reply-To: <1061479688.19036.1699.camel@nighthawk>
On Thu, Aug 21, 2003 at 08:28:08AM -0700, Dave Hansen wrote:
> It looks like you booted 20 processors, successfully.
> You have 5 "Geniune" cpus and 16 "Xeon" cpus. Are you using plain
> summit, or generic arch support?
AFAICT the only way we can see that is if we kick the same ones twice.
Using max_cpus= the exact number of cpus you have or CONFIG_NR_CPUS=
the exact number of cpus you have will get testers able to boot until
it's fixed.
It shouldn't be too hard to find the faulty code; all 5 "Genuine"
entries are bogus and alias the entries we actually want (the Xeons).
-- wli
prev parent reply other threads:[~2003-08-21 21:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 21:58 CPU boot problem on 2.6.0-test3-bk8 Andrew Theurer
2003-08-21 1:02 ` Dave Hansen
2003-08-21 1:13 ` Andrew Theurer
2003-08-21 3:42 ` Dave Hansen
2003-08-21 14:10 ` Andrew Theurer
2003-08-21 14:58 ` Dave Hansen
2003-08-21 15:56 ` Andrew Theurer
2003-08-21 16:09 ` Dave Hansen
2003-08-21 17:02 ` Andrew Theurer
2003-08-21 21:13 ` William Lee Irwin III
2003-08-21 21:33 ` William Lee Irwin III
2003-08-21 22:17 ` William Lee Irwin III
2003-08-21 22:45 ` William Lee Irwin III
2003-08-21 23:10 ` William Lee Irwin III
2003-08-22 17:16 ` William Lee Irwin III
2003-08-22 18:16 ` Andrew Theurer
2003-08-22 19:11 ` Andrew Theurer
2003-08-21 15:28 ` Dave Hansen
2003-08-21 21:04 ` William Lee Irwin III [this message]
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=20030821210449.GH4306@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=habanero@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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.