RE: XP1000 667 mhz locking up.

[Mike Foley <Mike Foley alpha-processor com>]

	Sounds like that one didn't survive the power hit
	very well. I'm gonna hazard a guess that the motherboard
	is messed up.
								mike

-----Original Message-----
From: Todd Henderson [mailto:Todd_Henderson@readwo.com]
Sent: Thursday, December 16, 1999 2:50 PM
To: axp-list@redhat.com
Subject: XP1000 667 mhz locking up.


I have 34 identically configured XP1000's and recently one of them began
to lock up spewing this information to the console:

 +0 8000000000000080 5800000018
 +10 100000086 0
 +20 8 2baaa40
 +30 0 f1
 +40 3 4
 +50 0 4
 +60 0 0
 +70 0 0
TSUNAMI machine check NOT expected
tsunami_machine_check: vector=0x630 la_ptr=0xfffffc0000006000
                 pc=0x120230514 size=0x80 procoffset=0x18 sysoffset 0x58

TSUNAMI_pci_clr_err: PERROR after read 0x0
TSUNAMI_pci_clr_err: PERROR after read 0x0


This all started after we had a UPS/power failure for the whole computer
room.  I've rebuilt the system drive.  Is there an indication here as to
where to look?  The kernel version is 2.2.5-16.

Thanks,
Todd


-- 
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com