From: Bryan Daniel (danielb@telus.net)
Date: Wed Mar 19 2003 - 16:09:56 EST
Dear Managers:
This morning our DS20 running tru64 V4.0F had an apparent problem which
initiated an immediate reboot. (Of course this happened on a day when I
am home very ill) The machine booted normally and appears to be
functioning properly now with both cpu working. I checked the messages
log and found the following, which seems to indicate a possible cpu
problem:
Should I be initiating a hardware service call immediately? Has anyone
seen this kind of thing previously?
---------------------------------------
Mar 19 12:00:25 granite vmunix: Machine check code = 0x1000000a0
Mar 19 12:00:25 granite vmunix: Ibox Status
= 0000000000000000
Mar 19 12:00:25 granite vmunix: Dcache Status
= 0000000000000008
Mar 19 12:00:25 granite vmunix: Cbox Address
= 00000000003f32c0
Mar 19 12:00:25 granite vmunix: Fill Syndrome 1
= 0000000000000000
Mar 19 12:00:25 granite vmunix: Fill Syndrome 0
= 0000000000000001
Mar 19 12:00:25 granite vmunix: Cbox Status
= 000000000000000c
Mar 19 12:00:25 granite vmunix: EV6 captured status of Bcache
mode = 0000000000000005
Mar 19 12:00:25 granite vmunix: EV6 Exception Address
= fffffc00003f3200
Mar 19 12:00:25 granite vmunix: EV6 Interrupt Enablement and
Current Processor mode = 00000022e0000000
Mar 19 12:00:26 granite vmunix: EV6 Interrupt Summary Register
= 0000000080000000
Mar 19 12:00:26 granite vmunix: EV6 TBmiss or Fault status
= 0000000000000280
Mar 19 12:00:26 granite vmunix: EV6 PAL Base Address
= 0000000000018000
Mar 19 12:00:26 granite vmunix: EV6 Ibox control
= fffffffc03304396
Mar 19 12:00:26 granite vmunix: EV6 Ibox Process_context
= 0000440000000004
Mar 19 12:00:26 granite vmunix: O/S Summary flag
= 0000000000000004
Mar 19 12:00:26 granite vmunix: Cchip Base Address (phys)
= 00000801a0000000
Mar 19 12:00:26 granite vmunix: Cchip Device Raw Interrupt
Request = 0000000000000000
Mar 19 12:00:26 granite vmunix: DRIR Register Decode:
Mar 19 12:00:26 granite vmunix: PCI Device Interrupt
Mask = 0000000000000000
Mar 19 12:00:26 granite vmunix: Cchip Miscellaneous Register
= 0000000000000000
Mar 19 12:00:26 granite vmunix: Misc Register Decode:
Mar 19 12:00:26 granite vmunix: Cchip Revision: 00
Mar 19 12:00:26 granite vmunix: ID of CPU performing
read: 00
Mar 19 12:00:26 granite vmunix: Pchip 0 Base Address (phys)
= 0000080180000000
Mar 19 12:00:26 granite vmunix: Pchip 0 Error Register
= 0000000000000000
Mar 19 12:00:26 granite vmunix: Pchip Error Register Decode:
Mar 19 12:00:26 granite vmunix: PCI Xaction Start
Address = 0000000000000000
Mar 19 12:00:26 granite vmunix: PCI Command: Interrupt
Acknowledge
Mar 19 12:00:26 granite vmunix: Pchip 1 Base Address (phys)
= 0000080380000000
Mar 19 12:00:26 granite vmunix: Pchip 1 Error Register
= 0000000000000000
Mar 19 12:00:26 granite vmunix: Pchip Error Register Decode:
Mar 19 12:00:27 granite vmunix: PCI Xaction Start
Address = 0000000000000000
Mar 19 12:00:27 granite vmunix: PCI Command: Interrupt
Acknowledge
Mar 19 12:00:27 granite vmunix: panic (cpu 0): Processor Machine Check
Mar 19 12:00:27 granite vmunix: device string for dump = RAID 1 8 0 0 0
0 0.
Mar 19 12:00:27 granite vmunix: DUMP.prom: dev RAID 1 8 0 0 0 0 0, block
2226193
Mar 19 12:00:27 granite vmunix: device string for dump = RAID 1 8 0 0 0
0 0.
Mar 19 12:00:27 granite vmunix: DUMP.prom: dev RAID 1 8 0 0 0 0 0, block
2226193
Mar 19 12:00:28 granite vmunix: Alpha boot: available memory from
0x49e2000 to 0xdfff6000
Mar 19 12:00:28 granite vmunix: Digital UNIX V4.0F (Rev. 1229); Sun Sep
22 10:34:18 PDT 2002
Mar 19 12:00:28 granite vmunix: physical memory = 3584.00 megabytes.
Mar 19 12:00:28 granite vmunix: available memory = 3509.41 megabytes.
Mar 19 12:00:28 granite vmunix: using 13752 buffers containing 107.43
megabytes of memory
Mar 19 12:00:28 granite vmunix: Master cpu at slot 0.
---------------------------------------------
reboot is normal after this
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:12 EDT