Linux 2.6.2, AMD kernel: MCE: The hardware reports a non fatal, correctable incident
What about this message?. Note that the system works. I have not had to reboot. What meens the below message?.
Do not hesitate ask for more information.
Regards,
Davi Leal
Message from syslogd@AMD at Tue Mar 2 11:27:00 2004 ...
AMD kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Message from syslogd@AMD at Tue Mar 2 11:27:00 2004 ... AMD kernel: Bank 1: 9400400000000152
$ cat /proc/version Linux version 2.6.2 (root@AMD) (gcc version 3.3.3 20040125 (prerelease) (Debian)) #1 Wed Feb 4 19:26:25 CET 2004
$ cat /proc/version Linux version 2.6.2 (root@AMD) (gcc version 3.3.3 20040125 (prerelease) (Debian)) #1 Wed Feb 4 19:26:25 CET 2004 davi@AMD:/Compartida$ davi@AMD:/Compartida$ davi@AMD:/Compartida$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2400+ stepping : 0 cpu MHz : 2010.002 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 3956.73 $
Quoted 3 lines · Davi Leal
What about this message?. Note that the system works. I have not had to reboot. What meens the below message?.
The original plan behind that option was to find hardware faults early, but it seems to trigger a lot of false positives for various reasons. Part of this problem is that MCEs can also be generated on some hardware by doing something silly like reading from a reserved part of your motherboard chipset..
There are also CPU errata that can cause them to falsely trigger in some unusual cases, but I've not had time to go through the various errata datasheets to blacklist affected CPUs unfortunatly.
I'm toying with the idea of marking it CONFIG_BROKEN for 2.6, and fixing it up later.
Dave
Quoted 11 lines · Dave Jones
Quoted 3 lines · Davi Leal
What about this message?. Note that the system works. I have not had to reboot. What meens the below message?.
The original plan behind that option was to find hardware faults early, but it seems to trigger a lot of false positives for various reasons. Part of this problem is that MCEs can also be generated on some hardware by doing something silly like reading from a reserved part of your motherboard chipset..
Quoted 6 lines
There are also CPU errata that can cause them to falsely trigger in some unusual cases, but I've not had time to go through the various errata datasheets to blacklist affected CPUs unfortunatly.
I'm toying with the idea of marking it
CONFIG_BROKENfor 2.6, and fixing it up later.
I'm unsure if it's a good idea it's broken only on broken HW, people wanting stable box try to buy sane HW and don't enable CONFIG_BROKEN so they will never see if their HW are starting to be out of spec.
Perhaps rewording the option help and the error message to say it's known to report false positive...
regards,
Phil
Quoted 10 lines · Dave Jones
Quoted 3 lines · Davi Leal
What about this message?. Note that the system works. I have not had to reboot. What meens the below message?.
The original plan behind that option was to find hardware faults early, but it seems to trigger a lot of false positives for various reasons. Part of this problem is that MCEs can also be generated on some hardware by doing something silly like reading from a reserved part of your motherboard chipset..
The MCE stuff truly did find a hardware fault early for me; my
Athlon system was MCE'ing and I ignored it, and later I got sig11 errors and fs corruption, which I finally traced to a failing stick of memory.
Quoted 6 lines
There are also CPU errata that can cause them to falsely trigger in some unusual cases, but I've not had time to go through the various errata datasheets to blacklist affected CPUs unfortunatly.
I'm toying with the idea of marking it
CONFIG_BROKENfor 2.6, and fixing it up later.
I wouldn't be so quick to write off MCEs as bugs or errata,
especially if the exceptions have only just begun showing up. Running CPUBurn, memtest86 and the like is still probably a good idea, especially if you value the data on your file system.
--
Joseph Fannin
[email protected]
"Anyone who quotes me in their sig is an idiot." -- Rusty Russell.