Hi Cory
We had the same problem last friday and tried to do a memory dump, but it
would begin with a start norecovery, we donīt know why. Also we are real
busy right now and the memory dump takes too long. It takes about 1:30 hrs.
I was hoping somebody had this happen to them. The response center is
already on it.
Thanks
-----Original Message-----
From: Black, Cory [mailto:[log in to unmask]]
Sent: Wednesday, March 13, 2002 9:58 AM
To: Sylvia Almeida
Subject: RE: system failure
I would echo what Bill just posted, we've had good luck with the HPRC on the
rare occasions we crash. You'll want to get a memory dump next time it
happens. Then HP will be able to look at it and ID the offending program or
hardware.
-----Original Message-----
From: Sylvia Almeida [mailto:[log in to unmask]]
Sent: Wednesday, March 13, 2002 11:34 AM
To: [log in to unmask]
Subject: system failure
Hi
We just had the following happen on an N4000-300
We are running 7.0 express 1
System Abort 0 from subsystem 107
Secondary Status: info=0, subsys=107
System Halt 7, $000
*****System Alert*****
System name: GSP-NS4000-e3000
Date 03/13/2002 time: 16:30:51
Alert Level: 12= software failure
Reason for alert
Source: 0=unknown, no source stated
Source Detail: 0=unknown, no source stated sourceID=0
Problem Detail: 0=no problem detail
What is System Abort 0?
We started the system, and everything is running normally right now.
This happened last friday too, and the problem was a processor, but we did
check them on GSP and they are configured and functional.
Help
Sylvia
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
