Thanks go to,
Goebel, Greg [ggoebel_at_grci.com]
V.S. Glukhov [glukhov_at_sequence.Stanford.EDU]
Dr. Tom Blinn, 603-884-0646 [tpb_at_doctor.zk3.dec.com]
alan_at_nabeth.cxo.dec.com
Kym Schwarz [schwarz_at_stl.dec.com]
It appears that the problem was a fault (possibly cache) on CPU 0. We had
the DEC service guy move the CPU 0 card from slot 0 to slot 1. Even though
the machine stopped crashing, the errors still occured. In the end we
replaced the CPU board and haven't had an error since.
Btw, when I wrote this message, I said it was an AS 4100 when in reality it
was actually an AS 2100. Some days I just don't think hard enough :)
Damien.
> -----Original Message-----
> From: Malczewski, Damien
> Sent: Monday, November 23, 1998 10:07 AM
> To: 'alpha-osf-managers_at_ornl.gov'
> Subject: Strange crashes on a Alpha 4100
>
>
> Managers,
>
> I have a machine (Alpha 4100, DU 4.0D) that is crashing at seemingly
> random intervals with no obvious reason. Does anyone know what the
> following crash data could mean?
>
> The uerf entry at the time shows a "panic (cpu 0): kernel memory fault".
>
> --->
> Machine Check error corrected by processor
> Machine Check error corrected by processor
> Machine Check error corrected by processor
>
> trap: invalid memory read access from kernel mode
>
> faulting virtual address: 0x000000000007a13c
> pc of faulting instruction: 0xfffffc0000417d08
> ra contents at time of fault: 0xfffffc0000417d58
> sp contents at time of fault: 0xffffffffa906f4e0
>
> panic (cpu 0): kernel memory fault
> syncing disks... device string for dump = RAID 0 2009 0 0 0 0 0.
> DUMP.prom: dev RAID 0 2009 0 0 0 0 0, block 262813
> device string for dump = RAID 0 2009 0 0 0 0 0.
> DUMP.prom: dev RAID 0 2009 0 0 0 0 0, block 262813
> <---
>
> Ideas? A RAM problem?
>
> Thanks,
> Damien.
>
>
Received on Sun Dec 06 1998 - 23:40:59 NZDT