From: James Cleverdon <jamesclv@us.ibm.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-rc3-ac2 SMP
Date: Wed, 24 Jul 2002 20:34:01 -0700 [thread overview]
Message-ID: <200207242034.01605.jamesclv@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207241643010.17209-100000@linux-box.realnet.co.sz>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Wednesday 24 July 2002 08:26 am, Zwane Mwaikambo wrote:
[ Snip! ]
>raw_phys_apicid[]= 00 01 02 03 00 00 00 00 00 00 00 00 00 00 00 00 00
>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> cpu_2_logical_apicid[]= 01 01 02 08 FF FF FF FF FF FF FF FF FF FF FF FF FF
> FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
> cpu_2_physical_apicid[]= 02 00 01 03 FF FF FF FF FF FF FF FF FF FF FF FF FF
> FF F F FF FF FF FF FF FF FF FF FF FF FF FF FF
Ah ha! Note that while the CPU records in the {MPS,ACPI/MADT} table are in
numerical order (as preserved in raw_phys_apicid), the boot CPU is # 02. The
flat code in smp_boot_cpus assumes that the boot CPU will be the first record
in the list. Oops.
Try the attached patch and see if it helps.
[ Snip! ]
>
> Regards,
> Zwane
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com
[-- Attachment #2: 2.4.19-rc3-ac3_flat_hack.2002-07-24 --]
[-- Type: text/x-diff, Size: 715 bytes --]
--- ac3/arch/i386/kernel/smpboot.c.df Tue Jul 23 15:02:49 2002
+++ ac3/arch/i386/kernel/smpboot.c Wed Jul 24 18:02:24 2002
@@ -1077,6 +1077,7 @@
*/
Dprintk("CPU present map: %lx\n", phys_cpu_present_map);
+ cpu = 1;
for (bit = 0; bit < NR_CPUS; bit++) {
if (!(phys_cpu_present_map & (1UL << bit)))
continue;
@@ -1093,7 +1094,7 @@
else if (clustered_apic_logical)
log_apicid = ((bit >> 2) << 4) | (1 << (bit & 0x3));
else
- log_apicid = 1u << bit;
+ log_apicid = 1u << cpu;
do_boot_cpu(phys_apicid, log_apicid);
@@ -1104,6 +1105,8 @@
(phys_cpu_present_map & (1ul << bit)))
printk("CPU #%d not responding - cannot use it.\n",
bit);
+ else
+ ++cpu;
}
/*
next prev parent reply other threads:[~2002-07-25 3:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 4:21 Summit patch for 2.4.19-rc3-ac2 James Cleverdon
2002-07-23 8:51 ` Lech Szychowski
2002-07-23 12:03 ` 2.4.19-rc3-ac2 SMP Zwane Mwaikambo
2002-07-23 12:11 ` Zwane Mwaikambo
2002-07-23 18:50 ` James Cleverdon
2002-07-24 15:26 ` Zwane Mwaikambo
2002-07-24 22:50 ` James Cleverdon
2002-07-25 3:34 ` James Cleverdon [this message]
2002-07-25 7:11 ` Zwane Mwaikambo
2002-07-25 20:29 ` James Cleverdon
2002-07-25 13:26 ` Zwane Mwaikambo
2002-07-23 13:30 ` Summit patch for 2.4.19-rc3-ac2 James Bourne
2002-07-23 13:42 ` Steven Cole
2002-07-23 14:34 ` Philippe Gramoullé
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 17:28 2.4.19-rc3-ac2 SMP Mikael Pettersson
2002-07-25 20:48 ` James Cleverdon
2002-07-26 10:31 ` Zwane Mwaikambo
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=200207242034.01605.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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