[9422] in Hotline Meeting
m1-115-3 is reporting memory errors....
daemon@ATHENA.MIT.EDU (epeisach@Athena.MIT.EDU)
Tue Jun 16 10:36:09 1992
From: epeisach@Athena.MIT.EDU
Date: Tue, 16 Jun 92 10:35:51 -0400
To: hotline@Athena.MIT.EDU
I have a report from DSlogger that m1-115-3 reported some memory
problems yesterday:
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 101. MEMORY ERROR
SEQUENCE NUMBER 8.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Mon Jun 15 15:29:28 1992 EDT
OCCURRED ON SYSTEM m1-115-13
SYSTEM ID x82011601 HW REV: x1
FW REV: x16
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN01
----- UNIT INFORMATION -----
UNIT CLASS MEMORY
UNIT TYPE PMAX MEMORY
ERROR SYNDROME MEMORY PARITY ERROR
----- MEMORY INFO -----
MEMREG x5A000100 HARD CNT 0.
SOFT CNT 1.
TRAN CNT 0.
DATA BIT IN ERROR
HIGH BYTE IN ERROR
MEMORY PARITY ERROR: SOFT
SIMM # 5.
PHYSICAL ADDR x00857E1A
EPC x00411780
BAD VIRT ADR x7FFFBE1A
********************************* ENTRY 12. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 9.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Mon Jun 15 15:29:28 1992 EDT
OCCURRED ON SYSTEM m1-115-13
SYSTEM ID x82011601 HW REV: x1
FW REV: x16
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN01
PROCESSOR COUNT 779381101.
PROCESSOR WHO LOGGED x00000000
MESSAGE pid 321 (timed) was killed on memory
_parity error
********************************* ENTRY 13. *********************************
********************************* ENTRY 15. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 101. MEMORY ERROR
SEQUENCE NUMBER 12.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Mon Jun 15 17:09:05 1992 EDT
OCCURRED ON SYSTEM m1-115-13
SYSTEM ID x82011601 HW REV: x1
FW REV: x16
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN01
----- UNIT INFORMATION -----
UNIT CLASS MEMORY
UNIT TYPE PMAX MEMORY
ERROR SYNDROME MEMORY PARITY ERROR
----- MEMORY INFO -----
MEMREG x5A000200 HARD CNT 0.
SOFT CNT 2.
TRAN CNT 0.
DATA BIT IN ERROR
HIGH BYTE IN ERROR
MEMORY PARITY ERROR: SOFT
SIMM # 5.
PHYSICAL ADDR x00857E18
EPC x004573A0
BAD VIRT ADR x10003E18
********************************* ENTRY 16. *********************************
********************************* ENTRY 21. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 101. MEMORY ERROR
SEQUENCE NUMBER 4.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Mon Jun 15 17:20:47 1992 EDT
OCCURRED ON SYSTEM m1-115-13
SYSTEM ID x82011601 HW REV: x1
FW REV: x16
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN01
----- UNIT INFORMATION -----
UNIT CLASS MEMORY
UNIT TYPE PMAX MEMORY
ERROR SYNDROME MEMORY PARITY ERROR
----- MEMORY INFO -----
MEMREG x5A000100 HARD CNT 0.
SOFT CNT 1.
TRAN CNT 0.
DATA BIT IN ERROR
HIGH BYTE IN ERROR
MEMORY PARITY ERROR: SOFT
SIMM # 5.
PHYSICAL ADDR x00857E1A
EPC x00411780
BAD VIRT ADR x7FFFBE1A
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 5.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Mon Jun 15 17:20:47 1992 EDT
OCCURRED ON SYSTEM m1-115-13
SYSTEM ID x82011601 HW REV: x1
FW REV: x16
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN01
MESSAGE pid 321 (timed) was killed on memory
_parity error
