From: Frank Cusack <fcusack@fcusack.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2nd proc not seen
Date: Sun, 28 Sep 2003 20:50:46 -0700 [thread overview]
Message-ID: <20030928205045.B21288@google.com> (raw)
In-Reply-To: <20030904091437.A25107@google.com>; from fcusack@fcusack.com on Thu, Sep 04, 2003 at 09:14:37AM -0700
On Thu, Sep 04, 2003 at 09:14:37AM -0700, Frank Cusack wrote:
> On Thu, Sep 04, 2003 at 02:11:13AM -0700, Frank Cusack wrote:
> > I think I've seen some recent talk about this problem. I have an HPAQ
> > xw6000 w/ 2xP4 CPUs. A RH kernel finds both CPUs (4 if I enable HT). A
> > kernel.org kernel only finds 1 (2 if I enable HT).
This turned out to be a CPU numbering issue. The HPAQ machine numbers
the cpus #0 and #6. I had NR_CPUS set to 2. That only works if the CPUs
are physically numbered 0 and 1.
So NR_CPUS is a little misleading. I could suggest a Config.help change
if you like.
/fc
next prev parent reply other threads:[~2003-09-29 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 9:11 2nd proc not seen Frank Cusack
2003-09-04 16:14 ` Frank Cusack
2003-09-29 3:50 ` Frank Cusack [this message]
2003-09-29 8:58 ` J.A. Magallon
2003-09-29 9:13 ` Mikael Pettersson
2003-09-29 20:51 ` 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=20030928205045.B21288@google.com \
--to=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
/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