HP3000-L Archives

April 2001, Week 3

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:
Christian Lheureux <[log in to unmask]>
Reply To:
Date:
Wed, 18 Apr 2001 16:52:52 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
OK, I figured the good ole' dumpreader (that's me) could bring a few
details. You wrote :

> One of our unsupported systems had the following
> halt message yesterday.  Only curious as to the
> meaning since it isn't in any of my error books:

> SYSTEM ABORT 1458 FROM SUBSYSTEM 102

Means process aborted while critical (shoulnd't have aborted, since it was
flagged by MPE/iX as critical, hence the system itself kind of committing
suicide) from Process Management (subsys 102). Seriously implies that
Process Management somehow manages processes. Not a big surprise, huh ?

> SECONDARY STATUS:INFO=-55,SUBSYS=107

That's an invalid pointer (-55), or more precisely, an invalid target
address alignment causing a data memory protection trap, from Virtual Space
Manager (the module of MPE which handles virtual addressing, including
pointers). Helps trace the root cause of the system abort. Or, at least,
tells the dumpreader (if there's a dump, that is ...) where to start.

> SYSTEM HALT 7,$O5B2.

Same as SA 1458, in hex form. Also indicates the system has logically come
to a halt due to software (halt 7)

> There is no interest in fixing it, just want to
> know what it means.

Too bad. Otherwise, I would have asked for a memory dump. It's very hard to
figure out what a general purpose system abort such as a 1458 can be without
a memory dump.

> Tracy Johnson
> MSI Schaevitz Sensors

Hope this clears the mud, somehow ...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2