Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on resume!

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Vegard Nossum
Date: Thursday, August 21, 2008 - 4:18 am

On Thu, Aug 21, 2008 at 11:27 AM, Maciej W. Rozycki
<macro@linux-mips.org> wrote:

Hi,

I've also seen this a lot, so I have now written (I think) such a
debug patch (it's very crude) and tested it on my laptop, which
exhibits this problem.

The patch and full dmesg (with debug output) can be found here:

http://userweb.kernel.org/~vegard/bugs/20080821-apic/

The output looks like this (with register annotations by me; CPU id is
the second column)

APIC error on CPU0: 00(40)
Last 16 APIC writes:
0: 1: [00000380] = 00001f79
1: 1: [000000b0] = 00000000
2: 1: [00000380] = 00001f7e
3: 1: [000000b0] = 00000000
4: 1: [00000380] = 00001fa5
5: 1: [000000b0] = 00000000
6: 1: [00000380] = 00001f8c
7: 1: [000000b0] = 00000000
8: 1: [000000b0] = 00000000
9: 1: [00000380] = 00001e4e
10: 1: [000000b0] = 00000000
11: 1: [00000380] = 00001fa5
12: 1: [000000b0] = 00000000
13: 1: [00000380] = 00001f87 # Initial Count Register (for Timer)
14: 0: [00000280] = 00000000 # Error Status Register
15: 0: [000000b0] = 00000000 # EOI Register

The order is from oldest (0) to newest (15) write. I don't see any
writes to ICR in there, which means that IPIs can be ruled out? It
seems that it is the write to Timer that causes it. In another place,
we have this:

13: 1: [00000320] = 000100ef # LVT Timer Register
14: 0: [00000280] = 00000000
15: 0: [000000b0] = 00000000

This would be APIC_LVT_MASKED | LOCAL_TIMER_VECTOR.

The APIC error is seen approximately every 3 minutes.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Rafael J. Wysocki, (Wed Aug 20, 12:38 pm)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Rafael J. Wysocki, (Wed Aug 20, 2:56 pm)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Maciej W. Rozycki, (Thu Aug 21, 2:27 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Vegard Nossum, (Thu Aug 21, 4:18 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Maciej W. Rozycki, (Thu Aug 21, 4:51 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Maciej W. Rozycki, (Thu Aug 21, 5:01 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Maciej W. Rozycki, (Thu Aug 21, 5:57 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Mikael Pettersson, (Thu Aug 21, 6:15 am)
Re: 2.6.27-rc3: 'APIC error on CPU1: 00(40)', but only on ..., Maciej W. Rozycki, (Sat Aug 30, 1:16 pm)