From: Len Brown <len.brown@intel.com>
To: Eduard Bloch <edi@gmx.de>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4)
Date: 24 Nov 2003 01:19:07 -0500 [thread overview]
Message-ID: <1069654747.2812.689.camel@dhcppc4> (raw)
In-Reply-To: <20031123204532.GA6093@zombie.inka.de>
On Sun, 2003-11-23 at 15:45, Eduard Bloch wrote:
> #include <hallo.h>
> * Brown, Len [Sun, Nov 23 2003, 03:16:11PM]:
> > > weird 1+2xHT mode.
Please try CONFIG_NR_CPUS=8, or apply the patch below to 2.4.23.
smp_boot_cpus() incorrectly assumes that Local APIC ID's are handed out
0,1,2...
But they're handed out 0,1,6,7 on your system. #6 happens to be your
boot CPU, smp_boot_cpus() brings up #0 and #1, and never asks to boot #7
-- thus 3 logical processors. If #0 happened to be your boot processor,
you'd get only 2 logical processors.
cheers,
-Len
===== arch/i386/kernel/smpboot.c 1.17 vs edited =====
--- 1.17/arch/i386/kernel/smpboot.c Mon Nov 3 08:48:33 2003
+++ edited/arch/i386/kernel/smpboot.c Mon Nov 24 01:06:26 2003
@@ -1106,7 +1106,7 @@
*/
Dprintk("CPU present map: %lx\n", phys_cpu_present_map);
- for (bit = 0; bit < NR_CPUS; bit++) {
+ for (bit = 0; bit < MAX_APICS; bit++) {
apicid = cpu_present_to_apicid(bit);
/* don't try to boot BAD_APICID */
next prev parent reply other threads:[~2003-11-24 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 20:16 not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4) Brown, Len
2003-11-23 20:45 ` Eduard Bloch
2003-11-24 6:19 ` Len Brown [this message]
2003-11-24 7:00 ` William Lee Irwin III
2003-11-24 16:49 ` Len Brown
2003-11-24 22:55 ` William Lee Irwin III
2003-11-30 9:28 ` Eduard Bloch
-- strict thread matches above, loose matches on Subject: below --
2003-11-15 15:40 2.4.22 SMP kernel build for hyper threading P4 Job 317
2003-11-15 16:40 ` Eduard Bloch
2003-11-23 15:06 ` not fixed in 2.4.23-rc3 (was: Re: 2.4.22 SMP kernel build for hyper threading P4) Eduard Bloch
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=1069654747.2812.689.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=davej@redhat.com \
--cc=edi@gmx.de \
--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