Thanks to all the people who answered (Arrigo Triulzi, Nikola Milutinovic,
Dr. Tom Blinn and Chad Price). The opinion seems unanimous, it is really an
hardware fault.
I'd like to add the box has been rebooted and is at service under close
watch. No other problems have been observed.
On Tue, Dec 21, 1999 at 11:55:45AM +0000, Carlos Morgado wrote:
>
> Some days ago an Alpha1000 4/266 had a crash and halted. This looks to me
> like a memory error or such. Could this be software induced ?
> About a month ago the box was upgraded from DU3.2 to DU4.0E and firmware
> upgrade to 5.4-101.
> This never happened before, so I'm wondering if it had something to do with
> recent upgrades
>
> tkx
>
> Dec 15 07:04:34 titanic vmunix: panic (cpu 0): Machine check - Hardware error
> Dec 15 07:04:34 titanic vmunix: syncing disks...
> Dec 15 07:04:34 titanic vmunix: trap: invalid memory read access from kernel mode
> Dec 15 07:04:34 titanic vmunix:
> Dec 15 07:04:34 titanic vmunix: faulting virtual address: 0x0000000000000008
> Dec 15 07:04:35 titanic vmunix: pc of faulting instruction: 0xfffffc0000451fa8
> Dec 15 07:04:35 titanic vmunix: ra contents at time of fault: 0xfffffc0000451fa0
> Dec 15 07:04:35 titanic vmunix: sp contents at time of fault: 0xffffffff843df420
>
--
Carlos Morgado <chbm_at_cprm.net>
My views are my own and do not bind my employer.
Received on Tue Dec 21 1999 - 15:01:32 NZDT