Re: [SLUG] errors in warn.log

From: Paul Hostetler (phostetl@columbus.rr.com)
Date: Mon May 13 2002 - 19:29:25 EDT

Next message: Andrew Wyatt: "Re: [SLUG] Best all-around laptop for Linux"
Previous message: R P Herrold: "Re: [SLUG] Suspicions confirmed!"
In reply to: Patrick Grantham \(Marriott Vacationclub Int'l\): "[SLUG] errors in warn.log"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This seems to plauge overclockers, and certain types of motherboards.

http://www.tldp.org/HOWTO/SMP-HOWTO-4.html

" A message like:

APIC error interrupt on CPU#0, should never happen.
... APIC ESR0: 00000002
... APIC ESR1: 00000000

indicates a 'receive checksum error'. This cannot be caused by
Linux as the APIC message checksumming part is completely in hardware.
It might be marginal hardware. As long as you dont see any instability,
they are not a problem - APIC messages are retried until delivered.
(Ingo Molnar)
"

Paul

Patrick Grantham (Marriott Vacationclub Int'l) wrote:

> Any idea what these entries mean in warn.log?
>
> May 13 06:41:43 suselinux2 kernel: APIC error on CPU0: 08(02)
> May 13 06:46:10 suselinux2 kernel: APIC error on CPU1: 04(08)
> May 13 06:46:10 suselinux2 kernel: APIC error on CPU0: 02(04)
> May 13 06:47:07 suselinux2 kernel: APIC error on CPU0: 04(04)
> May 13 06:47:07 suselinux2 kernel: APIC error on CPU1: 08(02)
>
>
>
>

Next message: Andrew Wyatt: "Re: [SLUG] Best all-around laptop for Linux"
Previous message: R P Herrold: "Re: [SLUG] Suspicions confirmed!"
In reply to: Patrick Grantham \(Marriott Vacationclub Int'l\): "[SLUG] errors in warn.log"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:24:14 EDT