From: Frank Cusack <fcusack@fcusack.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2nd proc not seen
Date: Thu, 4 Sep 2003 09:14:37 -0700 [thread overview]
Message-ID: <20030904091437.A25107@google.com> (raw)
In-Reply-To: <20030904021113.A1810@google.com>; from fcusack@fcusack.com on Thu, Sep 04, 2003 at 02:11:13AM -0700
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).
Works with 2.4.22. If anyone is interested, I'll followup with the exact
change from 2.4.21 that makes this work (I need to figure that out anyway).
It's NOT the recent apic.c changes (local APIC), at least not by itself.
/fc
next prev parent reply other threads:[~2003-09-04 16:15 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 [this message]
2003-09-29 3:50 ` Frank Cusack
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=20030904091437.A25107@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