diff options
| author | Bartlomiej Zolnierkiewicz <[email protected]> | 2009-07-28 21:52:54 +0000 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2009-08-17 08:17:02 +0000 |
| commit | c7f6fa44115d401e89db730f357629d39f8e4ba6 (patch) | |
| tree | 2b2c0c9508b16cd9f85b122355e6a8868f76ca50 /lib/find_next_bit.c | |
| parent | x86: Annotate section mismatch warnings in kernel/apic/x2apic_uv_x.c (diff) | |
| download | kernel-c7f6fa44115d401e89db730f357629d39f8e4ba6.tar.gz kernel-c7f6fa44115d401e89db730f357629d39f8e4ba6.zip | |
x86, mce: don't log boot MCEs on Pentium M (model == 13) CPUs
On my legacy Pentium M laptop (Acer Extensa 2900) I get bogus MCE on a cold
boot with CONFIG_X86_NEW_MCE enabled, i.e. (after decoding it with mcelog):
MCE 0
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 0 BANK 1 MCG status:
MCi status:
Error overflow
Uncorrected error
Error enabled
Processor context corrupt
MCA: Data CACHE Level-1 UNKNOWN Error
STATUS f200000000000195 MCGSTATUS 0
[ The other STATUS values observed: f2000000000001b5 (... UNKNOWN error)
and f200000000000115 (... READ Error).
To verify that this is not a CONFIG_X86_NEW_MCE bug I also modified
the CONFIG_X86_OLD_MCE code (which doesn't log any MCEs) to dump
content of STATUS MSR before it is cleared during initialization. ]
Since the bogus MCE results in a kernel taint (which in turn disables
lockdep support) don't log boot MCEs on Pentium M (model == 13) CPUs
by default ("mce=bootlog" boot parameter can be be used to get the old
behavior).
Signed-off-by: Bartlomiej Zolnierkiewicz <[email protected]>
Reviewed-by: Andi Kleen <[email protected]>
Signed-off-by: H. Peter Anvin <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'lib/find_next_bit.c')
0 files changed, 0 insertions, 0 deletions