Re: Fwd: Re: Working nforce2, was Re: Fixes for nforce2 hard lockup,apic, io-apic, udma133 covered

[Maciej W. Rozycki]

On Sat, 13 Dec 2003, Bob wrote:

> APIC error on CPU0: 02(02)
> what?? no crash though.
[...]
> bob@where cat /proc/interrupts
>            CPU0      
>   0:    3350153    IO-APIC-edge  timer
>   1:       5775    IO-APIC-edge  i8042
>   2:          0          XT-PIC  cascade
>   8:          1    IO-APIC-edge  rtc
>   9:          0   IO-APIC-level  acpi
>  12:       5385    IO-APIC-edge  i8042
>  14:         10    IO-APIC-edge  ide0
>  15:         10    IO-APIC-edge  ide1
>  16:    1717957   IO-APIC-level  ide2, ide3, eth0
>  19:     472929   IO-APIC-level  ide4, ide5
>  21:          0   IO-APIC-level  NVidia nForce2
> NMI:        822
> LOC:    3350073
> ERR:         35
> MIS:      15818

 It looks like the infamous APIC delivery bug -- the "MIS" counter shows
how many level-triggered interrupts has been erronously delivered as
edge-triggered ones.  No wonder the system shows instability -- you have 
noise problems at the APIC bus.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@xxxxxxxxxxxxx, PGP key available        +
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/