4-8
Service Manual
4.5
Sample Error Log Entries
4.5.1
Machine Check 660 Error
You can identify problem FRUs in an error log entry by checking the
contents of the registers against the parse trees.
The following steps (relating to the callouts in Example 4-5) isolate the error
and the FRU most likely responsible.
Table 4–3 Parsing a Sample 660 Error (Example 4-5)
➊
This line identifies the error log entry as a machine check 660 error.
➋
The parse tree for machine check 660 errors starts with the C_STAT
register. DOUBLE BIT FILL ERR is set.
➌
The TLBER register is next in the parse tree. UNCORRECTABLE DATA
ERROR is set.
➍
The TLBER register on the memory module is set to an
UNCORRECTABLE DATA ERROR, indicating that the source of the 660
is a memory module.
Example 4-5 Sample Machine Check 660 Error Log Entry
**************** ENTRY 1 ***********************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 8.
Timestamp of occurrence 01-OCT-1999 22:12:32
Host name clyp01
System type register x0000000C AlphaServer GS60E67/700
Number of CPUs (mpnum) x00000002
CPU logging event (mperr) x00000000
Event validity 1. O/S claims event is valid
Event severity 1. Severe Priority
Entry type 100. Machine Check Error - (major class)
1. - (minor class)