From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@osdl.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: CPU boot problem on 2.6.0-test3-bk8
Date: 21 Aug 2003 08:28:08 -0700 [thread overview]
Message-ID: <1061479688.19036.1699.camel@nighthawk> (raw)
In-Reply-To: <200308210910.07722.habanero@us.ibm.com>
On Thu, 2003-08-21 at 07:10, Andrew Theurer wrote:
> Still looks like we have a problem (see attached boot log). Maybe we should
> change that for loop to:
>
> for (bit = 0; kicked < num_processors && bit < BITS_PER_LONG; bit++)
>
> So we only loop for the actual number processors found in mpparse.c? This
> seems to work for me.
You have something else wrong too:
[dave@nighthawk temp]$ egrep -c ^CPU\[0-9\]+: 260test3bk8patch1
20
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?
$ egrep ^CPU\[0-9\]+: 260test3bk8patch1
CPU0: Intel(R) Genuine CPU 1.50GHz stepping 01
CPU1: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU2: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU3: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU4: Intel(R) Genuine CPU 1.50GHz stepping 01
CPU5: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU6: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU7: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU8: Intel(R) Genuine CPU 1.50GHz stepping 01
CPU9: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU10: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU11: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU12: Intel(R) Genuine CPU 1.50GHz stepping 01
CPU13: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU14: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU15: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU16: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU17: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU18: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
CPU19: Intel(R) Xeon(TM) CPU 1.50GHz stepping 01
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-08-21 15:29 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 [this message]
2003-08-21 21:04 ` William Lee Irwin III
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=1061479688.19036.1699.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=habanero@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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