Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) mysterious pipeline reboot
Usually from my experience a Fatal Error 2 is a memory leak of some
kind, If the box can't allocate any available memory it reboots, Are
you doing anything weird on it by chance?
Jason Nealis
Director Internet Operations
Network Access
Erols Internet
On Sat, 31 Jan 1998, David M. Way wrote:
> Greetings,
>
> I had a Pipeline 50 mysteriously reboot on me about 10 minutes ago. Im
> trying to figure out why it did, as nothing out of the ordinary was
> going on, i.e.: not loading firmware, etc...
> I went into diagnostic mode and typed fatal and received the following
> message:
>
> > fatal
> FATAL ERROR: Index: 2 Load: b.p50 Revision: 5.1Ap9
> Location: 001a3c1c 00195f5c 0019621e 0019084a 001ac758 00119f50
>
> SYSTEM IS UP: Index: 100 Load: b.p50 Revision: 5.1Ap9
>
> Not knowing what that means, im hoping someone out there might. Also,
> if the fatal message doesn't shed light, is there any reason it would
> reboot out of the blue like that? Bad isdn line, so on and so
> forth.....?
>
> thanks in advance,
>
> David Way
> Operations Manager
> Way Architects, P.C.
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: