Juergen Wilke wrote:
> > Now I'm testing 2.3.39, and I have found that it is much more stable (at
> > least netfilter is stable)
> Ok, perhaps I should give 2.3.39 a try.
> [...]
> Well, if it was only the X server... In my case, the machine just
> freezes from one moment to the other and is instantly dead (doesn't even
> respond to ping). Normally, I would suppose it to be some hardware
> issue, but why then did it run perfectly stable under 2.0.38?
In the meantime, I've tested 2.3.39, and it tells me I do have a
hardware problem. Instead of freezing my machine, 2.3.39 pumps up my
logfiles with the following:
> an 17 10:42:11 becks kernel: APIC error interrupt on CPU#1, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000008
> Jan 17 10:42:11 becks kernel: ... APIC ESR1: 00000008
> Jan 17 10:42:11 becks kernel: ... bit 3: APIC Receive Accept Error.
> Jan 17 10:42:11 becks kernel: APIC error interrupt on CPU#0, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000002
> Jan 17 10:42:11 becks kernel: ... APIC ESR1: 00000002
> Jan 17 10:42:11 becks kernel: ... bit 1: APIC Receive CS Error (hw problem).
> Jan 17 10:42:11 becks kernel: APIC error interrupt on CPU#0, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000002
> Jan 17 10:42:11 becks kernel: ... APIC ESR1: 00000002
> Jan 17 10:42:11 becks kernel: ... bit 1: APIC Receive CS Error (hw problem).
> Jan 17 10:42:11 becks kernel: APIC error interrupt on CPU#1, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000008
> Jan 17 10:42:11 becks kernel: ... APIC ESR1: 00000008
> Jan 17 10:42:11 becks kernel: ... bit 3: APIC Receive Accept Error.
> Jan 17 10:42:11 becks kernel: APIC error interrupt on CPU#0, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000002
> Jan 17 10:42:11 becks kernel: ... APIC ESR1: 00000002
> Jan 17 10:42:11 becks kernel: ... bit 1: APIC Receive CS Error (hw problem).
> Jan 17 10:42:11 becks kernel: APIC error interrupt on CPU#1, should never happen.
> Jan 17 10:42:11 becks kernel: ... APIC ESR0: 00000008
> Jan 17 10:42:12 becks kernel: ... APIC ESR1: 00000008
> Jan 17 10:42:12 becks kernel: ... bit 3: APIC Receive Accept Error.
etc. etc. etc., until I reboot my machine.
Now, what sort of hw problem does this indicate? Can I fix it easily, or
do I have to burn my mobo? And: why the hell did it work with 2.0.38?
Regards,
Juergen
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
