Skip to contentSkip to conversation

Hardware reports non-fatal error

2.6.1 MCE falseness? Niel Lambrechts 3 participants 3 messages Jan 18, 2004 – Jan 21, 2004

lore
Share & tools
lore

Niel Lambrechts

author
#0 lore raw

I get the following problem with 2.6.1 consistently after apm resuming:

"ksyrium kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.

Message from syslogd@ksyrium at Wed Jan 14 13:33:06 2004 ... ksyrium kernel: Bank 1: f2000000000001c5"

It does not happen on any other kernels I use (vanilla 2.4.24, SuSE 9 2.4.21-166) - even though CONFIG_X86_MCE=y for both. The equipment is brand-new - an IBM Thinkpad R50P - and it passes all IBM's s/w diagnostic.

I'd appreciate help with the parameters for parsemce to interpret the problem...not sure if my usage is correct? ;)

# ./parsemce -b 1 -a 0 -e f2000000000001c5
Status: (f2000000000001c5) Machine Check in progress.
Restart IP valid.

Is this really hardware (maybe a bug in the BIOS?) or are false positives possible with 2.6 MCE code?

-Niel

#1 lore raw
Quoted 6 lines · Niel Lambrechts

I get the following problem with 2.6.1 consistently after apm resuming:
"ksyrium kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.

Message from syslogd@ksyrium at Wed Jan 14 13:33:06 2004 ... ksyrium kernel: Bank 1: f2000000000001c5"

As it only happens when you resume from APM, I'm inclined to believe its a BIOS bug. With the output of dmidecode, we could blacklist this box to not do the nonfatal checking.

Quoted 4 lines

It does not happen on any other kernels I use (vanilla 2.4.24, SuSE 9 2.4.21-166) - even though CONFIG_X86_MCE=y for both. The equipment is brand-new - an IBM Thinkpad R50P - and it passes all IBM's s/w diagnostic.

None of the other kernels you mention have this, its a new feature of 2.6

Dave

#2 lore raw
Quoted 7 lines · On Sun, 18 Jan 2004 02:03:01 +0000 Dave Jones <[email protected]> wrote:
Quoted 4 lines · Niel Lambrechts

I get the following problem with 2.6.1 consistently after apm resuming:
"ksyrium kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.

Quoted 6 lines
Quoted 2 lines

Message from syslogd@ksyrium at Wed Jan 14 13:33:06 2004 ... ksyrium kernel: Bank 1: f2000000000001c5"

As it only happens when you resume from APM, I'm inclined to believe its a BIOS bug. With the output of dmidecode, we could blacklist this box to not do the nonfatal checking.

My Thinkpad T22 produces a similar warning on resume using APM:

kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
kernel: Bank 1: f200000000000104

dmidecode output starts with:

# dmidecode 2.3
SMBIOS 2.3 present.
46 structures occupying 1585 bytes.
Table at 0x1FFF0000.
Handle 0x0000
        DMI type 0, 20 bytes.
        BIOS Information
                Vendor: IBM
                Version: 16ET31WW (1.11 )
                Release Date: 03/20/2003
	.
	.
Handle 0x0001
        DMI type 1, 25 bytes.
        System Information
                Manufacturer: IBM
                Product Name: 26475EA
Signature · 3 lines
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/