Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 6.1.7 and repeated Fatal Error 1
On Wed, 16 Sep 1998 00:21:05 -0400 (EDT), "Chris A. Epler" wrote:
>On Wed, 16 Sep 1998, Thaddaeus Slany wrote:
>
>> I have never had any problems with my max 2012 running febk.m20 Rev. 6.1.7,
>> but today I have got two repeated fatal errors with index 1 showing exactly
>> same location. Before this had happened, I noticed very bad net
>> performance. Is there any coincidence?
>>
>> What does "Index: 1" mean?
^^^
Still unanswered. Is this any sort of a memory problem? e.g memory access
violation? It would be nice if someone had a description of most common
fatal errors for MAX TAOS 6.1.x.
>Did you 'fclear' the unit before loading 6.1.7?
No, I updated from febk.m20 rev. 6.1.0 to febk.m20 v. 6.1.7 with one step
(not using a restricted load). I only did 'fsave' and 'nvramclear'
according to the update instructions.
>Try tsave -am'ing your
>config, fclearing, trestoring the config and then restarting...this might
>help, I know it did on one of our boxes...
Thank you for this tip. I hope, I will not see this fatal error 1 again.
Best regards
--
Thaddaeus Slany, Technik Buergernetzverein Guenzburg e.V.
http://www.bnv-gz.baynet.de
Internet Mail: <highway@eikon.e-technik.tu-muenchen.de> or
<Thaddaeus.Slany@bnv-gz.baynet.de>
++ 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: