From: James Cleverdon <jamesclv@us.ibm.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-rc3-ac2 SMP
Date: Tue, 23 Jul 2002 11:50:14 -0700 [thread overview]
Message-ID: <200207231150.14141.jamesclv@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207231409000.32636-100000@linux-box.realnet.co.sz>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Tuesday 23 July 2002 05:11 am, Zwane Mwaikambo wrote:
> On Tue, 23 Jul 2002, Zwane Mwaikambo wrote:
> > Around here the machine gets a vector 0x31 (timer) interrupt on CPU0 then
> > locks up since the destination cpu bitmask is 0, It also seems that the
> > code is trying to use logical apic id in places instead of the physical
> > apic id, i saw attempted deliveries to physical apic id 4 and 8, this can
> > possibly explain the APIC receive errors people were reporting?
>
> Correction, the logical/physical apic id problem doesn't appear to be
> there with the summit patch. What i'm currently seeing is a destination of
> 0 with a non flat/physical destination format.
Drat! I thought I had all the logical vs. physical stuff straightened out.
Could you give this patch a try? It dumps all kinds of APIC state info.
You'll need to put a call to apic_state_dump() into check_timer() just after
the TIMER: printk.
(Hmmm.... Must clean up this patch and submit it to kdb as two new commands,
one for I/O APICs and one for local APICs....)
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com
[-- Attachment #2: apic_error.2.4.19-rc1-ac7 --]
[-- Type: text/x-diff, Size: 3371 bytes --]
--- 2.4.19-rc1-ac7/arch/i386/kernel/apic.c Wed Jul 17 12:02:50 2002
+++ ac7/arch/i386/kernel/apic.c Thu Jul 18 19:41:57 2002
@@ -1131,13 +1131,100 @@
smp_processor_id());
}
+static spinlock_t apic_dump_lock = SPIN_LOCK_UNLOCKED;
+
+static void
+apic_bit_vector_dump(unsigned long addr, char *name)
+{
+ int n;
+
+ printk("%s:", name);
+ for (n = 256 / 32; --n >= 0; addr += 0x10) {
+ printk(" %08lX", apic_read(addr));
+ }
+ printk("\n");
+}
+
+void
+print_ioapic_rtes(void)
+{
+ register int apic, rte, rte_max;
+
+ for (apic = 0; apic < nr_ioapics; apic++) {
+ printk("I/O APIC # %d:", apic);
+ rte_max = nr_ioapic_registers[apic];
+ for (rte = 0; rte < rte_max; rte++) {
+ if ((rte & 0x3) == 0)
+ printk("\n%02X:", rte);
+ printk(" %08X:%08X",
+ io_apic_read(apic, 0x10 + rte*2),
+ io_apic_read(apic, 0x10 + 1 + rte*2));
+ }
+ printk("\n");
+ }
+}
+
+/* Set breakpoint here. */
+void
+apic_state_dump_bp(void)
+{
+ cpu_relax();
+}
+
+/*
+ * apic_state_dump -- Print large amounts of APIC and related info.
+ */
+
+void
+apic_state_dump(void)
+{
+ register int v;
+ unsigned long flags;
+
+ spin_lock_irqsave(&apic_dump_lock, flags);
+
+ printk("ID=0x%08lX, LVR=0x%08lX, TPR=0x%08lX, ARB=0x%08lX, PROCPRI=0x%08lX\n", apic_read(APIC_ID), apic_read(APIC_LVR), apic_read(APIC_TASKPRI), apic_read(APIC_ARBPRI), apic_read(APIC_PROCPRI));
+ printk("DFR=0x%08lX, LDR=0x%08lX, ICR=0x%08lX\n", apic_read(APIC_DFR), apic_read(APIC_LDR), apic_read(APIC_ICR));
+ printk("SPIV=0x%08lX, ICR=0x%08lX, ICR2=0x%08lX, LVTT=0x%08lX, LVTPC=0x%08lX\n", apic_read(APIC_SPIV), apic_read(APIC_ICR), apic_read(APIC_ICR2), apic_read(APIC_LVTT), apic_read(APIC_LVTPC));
+ printk("LVT0=0x%08lX, LVT1=0x%08lX, LVTERR=0x%08lX\n", apic_read(APIC_LVT0), apic_read(APIC_LVT1), apic_read(APIC_LVTERR));
+ apic_bit_vector_dump(APIC_ISR, "ISR");
+ apic_bit_vector_dump(APIC_TMR, "TMR");
+ apic_bit_vector_dump(APIC_IRR, "IRR");
+ printk("clustered_apic_mode=%d, esr_disable=%d, target_cpus=0x%02X\n", clustered_apic_mode, esr_disable, (u32)target_cpus);
+ printk("apic_broadcast_id=0x%02X\n", (u32)apic_broadcast_id);
+ printk("raw_phys_apicid[]= ");
+ for (v = 0; v < NR_CPUS; v++) {
+ printk(" %02X", raw_phys_apicid[v]);
+ }
+ printk("\n");
+ printk("cpu_2_logical_apicid[]= ");
+ for (v = 0; v < NR_CPUS; v++) {
+ printk(" %02X", cpu_2_logical_apicid[v]);
+ }
+ printk("\n");
+ printk("cpu_2_physical_apicid[]=");
+ for (v = 0; v < NR_CPUS; v++) {
+ printk(" %02X", cpu_2_physical_apicid[v]);
+ }
+ printk("\n");
+ print_ioapic_rtes();
+
+ spin_unlock_irqrestore(&apic_dump_lock, flags);
+ apic_state_dump_bp();
+}
+
/*
* This interrupt should never happen with our APIC/SMP architecture
*/
+static spinlock_t smp_error_intr_lock = SPIN_LOCK_UNLOCKED;
+
asmlinkage void smp_error_interrupt(void)
{
unsigned long v, v1;
+ unsigned long flags;
+
+ spin_lock_irqsave(&smp_error_intr_lock, flags);
/* First tickle the hardware, only then report what went on. -- REW */
v = apic_read(APIC_ESR);
@@ -1158,6 +1245,11 @@
*/
printk (KERN_ERR "APIC error on CPU%d: %02lx(%02lx)\n",
smp_processor_id(), v , v1);
+ apic_state_dump();
+ /* APICs tend to spasm when they get errors. Disable the error intr. */
+ apic_write_around(APIC_LVTERR, ERROR_APIC_VECTOR | APIC_LVT_MASKED);
+
+ spin_unlock_irqrestore(&smp_error_intr_lock, flags);
}
/*
next prev parent reply other threads:[~2002-07-23 18:49 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 [this message]
2002-07-24 15:26 ` Zwane Mwaikambo
2002-07-24 22:50 ` James Cleverdon
2002-07-25 3:34 ` James Cleverdon
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=200207231150.14141.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