I have an DEC 3000-300 V3.2C system that keeps crashing over night when no one
is on it with the following info. Has anyone else seen a problem like this?
When it says 'Hardware error' can anyone tell me what hardware it is talking
about?
Excerpt from error log:
uerf version 4.2-011 (122)
********************************* ENTRY 1. ********************************
*
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 100. CPU EXCEPTION
SEQUENCE NUMBER 1.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Nov 3 21:57:12 1995
OCCURRED ON SYSTEM betty
SYSTEM ID x00020007 CPU TYPE: DEC 3000
SYSTYPE x00000000
----- UNIT INFORMATION -----
UNIT CLASS CPU
********************************* ENTRY 2. ********************************
*
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 302. PANIC
SEQUENCE NUMBER 2.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Nov 3 21:57:12 1995
OCCURRED ON SYSTEM betty
SYSTEM ID x00020007 CPU TYPE: DEC 3000
SYSTYPE x00000000
MESSAGE panic (cpu 0): Machine check -
_Hardware error
*******************************************************************************
*
This is what is displayed on the console when it crashes:
vmunix: MACHINE CHECK type 0x660 Machine check abort
vmunix: ptr[0-1] = 0000000100000014 ffffffff85f88000
vmunix: ptr[2-3] = 000002f800000004 0000000000000001
...
vmunix: ptr[30-31] = 0000000000000001 0000000001fbba58
vmunix: exc_addr = fffffc0000432b50
vmunix: exc_sum = 0000000000000000
...
vmunix: ident = 14
vmunix: mcr_stat = 40404040
vmunix: intr = 20000000
vmunix: tc_status = 00000010
vmunix: config = 00000000
vmunix: panic (cpu 0): Machine check - Hardware error
vmunix: syncing disks...
--
Thanks for any help,
Tom Barkanic
E-Systems, ECI Division
St. Petersburg, FL
mailto:tb_at_eci-cec.com
Received on Wed Nov 08 1995 - 22:53:14 NZDT