Digital Equipment DECstation 5000/100 Series, Руководство по обслуживанию

Страница: 70 / 392

***************** ENTRY 2 **********************
--------------EVENT INFORMATION ------------
EVENT CLASS
OPERATIONAL EVENT
OS EVENT TYPE 250 ASCII MSG
SEQUENCE NUMBER 6
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Jan 22 14:58:40 1991
OCCURRED ON SYSTEM ft3
SYSTEM ID x82030230 HW REV: x30
FW REV: x2
CPU TYPE: R4000
PROCESSOR TYPE KN04-BA
MESSAGE ioasicint: memory read error
Analyzing the Memory Error Example
The following list describes
the useful information in ENTRY 1 and ENTRY 2. Since this
is a memory error, the last entries under MEM REG in ENTRY
1 are of particular interest because they identify which SIMM
failed.
The ERROR SYNDROME field indicates that this is a
memory parity error.
The following MEM REG fields list details about the
memory failure:
The CNT fields list the count of hard (recurred on both
read and write operations), soft (recurred on read, but
cleared on write), and transient (didn’t recur on read)
errors.
The DATA BIT IN ERROR statement indicates that a
data bit (rather than a parity bit) failed.
The BYTE IN ERROR can be either high or low.
The MEMORY PARITY ERROR field lists the type
(hard, soft, transient) of error for this entry.
D0-15 indicates that the low SIMM failed. The low
SIMM is the left SIMM in a bank, looking from the
front, labeled D0-15 on the system module. The value
D16-31 in this position indicates that the high SIMM
failed. The high SIMM is the right SIMM in a bank,
labeled D16-31 on the module. BANK tells which bank
of memory failed. The eight banks are labeled 0 to 7
on both sides of the memory SIMMs. To replace the
3–14 Troubleshooting Tools