From: Ion Badulescu <ionut@badula.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, "Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [BUG] 2.5.63: ESR killed my box!
Date: Wed, 26 Feb 2003 15:47:38 -0500 [thread overview]
Message-ID: <200302262047.h1QKlcPt015577@buggy.badula.org> (raw)
In-Reply-To: <20030226072327.7936B2C04B@lists.samba.org>
On Wed, 26 Feb 2003 18:14:42 +1100, Rusty Russell <rusty@rustcorp.com.au> wrote:
> In message <9530000.1046238665@[10.10.2.4]> you write:
>> > SMP box, compiled for UP with CONFIG_LOCAL_APIC=y freezes on boot with
>> > last lines:
>> >
>> > POSIX conformance testing by UNIFIX
>> > masked ExtINT on CPU#0
>> > ESR value before enabling vector: 00000008
>> > [ Freeze here ]
I suspect the ESR is a red herring. The problem is that the kernel
assumes that the boot CPU is always CPU#0, and it also misprograms the
boot CPU's APIC.
What kind of SMP box is it (Intel/AMD)?
>> I put an esr_disable flag in there a while back ... does that workaround it?
>
> Yes. Hmm. Wonder if that helps my SMP wierness, too.
Does this patch (from Mikael) help? It fixed my problem on a dual AMD
box running a UP + local APIC kernel.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
--------------------------
--- linux-2.4.21-pre4/arch/i386/kernel/apic.c.~1~ 2003-02-23 15:55:31.000000000 +0100
+++ linux-2.4.21-pre4/arch/i386/kernel/apic.c 2003-02-23 16:03:50.000000000 +0100
@@ -649,7 +649,7 @@
}
set_bit(X86_FEATURE_APIC, &boot_cpu_data.x86_capability);
mp_lapic_addr = APIC_DEFAULT_PHYS_BASE;
- boot_cpu_physical_apicid = 0;
+ boot_cpu_physical_apicid = -1U;
if (nmi_watchdog != NMI_NONE)
nmi_watchdog = NMI_LOCAL_APIC;
@@ -1169,8 +1169,8 @@
connect_bsp_APIC();
- phys_cpu_present_map = 1;
- apic_write_around(APIC_ID, boot_cpu_physical_apicid);
+ BUG_ON(boot_cpu_physical_apicid != GET_APIC_ID(apic_read(APIC_ID)));
+ phys_cpu_present_map = 1 << boot_cpu_physical_apicid;
apic_pm_init2();
next prev parent reply other threads:[~2003-02-26 20:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 4:33 Rusty Russell
2003-02-26 5:51 ` Martin J. Bligh
2003-02-26 7:14 ` Rusty Russell
2003-02-26 7:27 ` William Lee Irwin III
2003-02-26 15:20 ` Linus Torvalds
2003-02-26 15:52 ` Martin J. Bligh
2003-02-26 16:37 ` Linus Torvalds
2003-02-26 16:52 ` Martin J. Bligh
2003-02-27 0:32 ` James Cleverdon
2003-02-27 11:11 ` Maciej W. Rozycki
2003-02-26 20:47 ` Ion Badulescu [this message]
2003-02-26 21:03 ` Martin J. Bligh
2003-02-26 21:16 ` Ion Badulescu
2003-02-26 21:23 ` Martin J. Bligh
2003-02-26 21:30 ` Linus Torvalds
2003-02-26 21:44 ` Ion Badulescu
2003-02-26 22:05 ` Linus Torvalds
2003-02-26 22:51 ` Martin J. Bligh
2003-02-26 23:07 ` Mikael Pettersson
2003-02-27 0:00 ` Linus Torvalds
2003-02-27 0:45 ` Martin J. Bligh
2003-02-27 1:20 ` Ion Badulescu
2003-02-27 1:33 ` Martin J. Bligh
2003-02-27 10:33 ` Mikael Pettersson
2003-02-27 1:26 ` Ion Badulescu
2003-02-27 1:40 ` Martin J. Bligh
2003-02-27 7:17 ` Rusty Russell
2003-02-26 8:43 Rusty Russell
2003-02-26 22:34 Grover, Andrew
2003-03-01 1:42 Mallick, Asit K
2003-03-01 3:07 Mallick, Asit K
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=200302262047.h1QKlcPt015577@buggy.badula.org \
--to=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®