OpenSolaris

Printable Version Enter a New Search
Bug ID 6617959
Synopsis logging errors left after BIOS has run produces false alarms
State 10-Fix Delivered (Fix available in build)
Category:Subcategory kernel:fm
Keywords fma_s10u5
Responsible Engineer Gavin Maltby
Reported Against
Duplicate Of
Introduced In solaris_nevada
Commit to Fix snv_77
Fixed In snv_77
Release Fixed solaris_nevada(snv_77) , solaris_10u5(s10u5_05) (Bug ID:2155807)
Related Bugs
Submit Date 17-October-2007
Last Update Date 13-November-2007
Description
The improved cpu.generic putback to build 76 includes code to log any valid
error telemetry it finds in the MCA banks at init time.  Intel volume 3A says that
this should not be done for processor family 0x6, and for extended processor
families it should only be done on warm-reset since the BIOS clears errors
on power-on reset.  Currently we're doing this unconditionally, and on older Pentium 3
systems this is picking up an uncorrectable dcache error from BIOS probe (I guess)
and leads us to fault the cpu;  the systems on which this was observed was a
family 0x6 cpu.

AMD documentation for K7 and K8/K8F says that system software should log any
valid telemetry found at initialization time.  Some BIOS versions will log and clear,
while others may leave data there for the OS to find.  Either way the claim is that
all telemetry should be valid.
Work Around
N/A
Comments
N/A