HP3000-L Archives

March 2002, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Cadier <[log in to unmask]>
Reply To:
Bill Cadier <[log in to unmask]>
Date:
Wed, 13 Mar 2002 10:52:39 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Hi Sylvia,

You should call your local Response Center for assistance with this.

Unfortunately, System Abort 0 is a generic abort used to indicate an
unusual condition in the MPE/iX kernel. There have been a few rare
instances and there are a few patches to correct specific occurances.
The Response Center should be able to assist in determining what
caused the SA0 you have experienced.

Best Regards,

Bill Cadier
HP/CSY


> 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 *

ATOM RSS1 RSS2