Followup-To: poster
Precedence: bulk
Has anyone experienced Machine Check errors that are "corrected by the processor"?
If so what might the general cause of such errors be? The general symptoms are
that approximately 18 hours after boot, the following syslog messages appear:
"vmunix: WARNING: too many processor corrected errors. Reporting suspended."
"vmunix: Machine Check error corrected by processor"
uerf reports the following:
uerf version 4.2-011 (122)
******************************* ENTRY 2. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 100. CPU EXCEPTION
SEQUENCE NUMBER 1.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Oct 27 01:16:23 1995
OCCURRED ON SYSTEM mail
SYSTEM ID x00020011
SYSTYPE x00000000
----- UNIT INFORMATION -----
UNIT CLASS CPU
The only suspect error message is the follow report at boot time:
vmunix: kn22a_eisa_handler_disable: bad key -1
Configuration is an Alpha Server 1000 4/200 running Digital Unix 3.2C
with Firmware Revision 3.0 and PALcode OSF version 1.35. The machine
also has 2 KSPZA adapters with firmware version DEC TZA SPO/A.14 and
a PCI FDDI adapter with firmware rev 2.46.
Other than the above two syslog errors and the uerf entry there are no
other symptoms. The machine has not crashed and continues to run.
Thanks in advance,
Greg
king_at_reston.ans.net
Received on Fri Oct 27 1995 - 22:39:07 NZDT