| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi all networkers and nightworkers,
Can that be a hardware related fault ?
Should I swap the switch ?
Problem occured when DEFBA was mounted with a DEChub ONE power supply
and the console port was just plugged with a cable to a terminal.
The DEFBA just crashed after some <CR> <Enter> where pressed.
I tested the DECswitch 900EF in the office and could not make it crash
again. The DEFBA is back in customer's configuration and didn't crash
since. Customer is a little bit worried that it happens again.
Any experience or interpretation is warmly welcomed
Walter
----------------------------------------------------------------------
DECswitch 900EF
=======================================================================
DUMP ERROR LOG
Current Reset Count: 14
=======================================================================
Entry # = 1
Entry Status = 0 [0=valid, 1=write_error, 2= invalid, 3=empty,
4=crc_error
Entry ID = 10
Firmware Rev. = 1.5
Reset Count = 12
Timestamp = 0 3C 6D68
Write Count = 5
FRU Mask = 0
Test ID = DEAD
Error Data = SR=2000 PC=03071E30 Error Code=00003000 ProcCsr=7D6D
Line # = 327
File = util.c
Dump another entry [Y]/N? y
Entry Status = 0
Entry ID = 10
Firmware Rev. = 1.5
Reset Count = 11
Timestamp = 0 92 8D23
Write Count = 5
FRU Mask = 0
Test ID = DEAD
Error Data = SR=2000 PC=03071E30 Error Code=00003000 ProcCsr=756D
Line # = 327
File = util.c
No more Error Log entries
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3673.1 | Some interpretation, but need more information.... | NETCAD::BATTERSBY | Don't use time/words carelessly | Tue Jul 02 1996 13:38 | 19 |
Can you go into menu 3 and provide us with the hardware rev
and firmware rev of the DEFBA? The error log dump indicates
some fault/failure in a ultility routine piece of common code
called util.c
The major rev of the firmware appears to be 1.5, but It would be
very helpful to know what the minor rev is IE: 1.5.X
^
The timestamps indicate that prior to the first error log entry
labeled Entry #1 that the module had been up for about 11 hours
prior to the first crash. The timestamp on the second error log
indicates it was up for about 26 hours prior to its crash.
I'm not familiar with the util.c routine, so it would take someone
familiar with this piece of code to explain what might be happening.
Is there anything about how the DEFBA when connected to the DEChub
ONE was being used prior to the crash that occured. IE: Were there
any ports connected to other devices, or network connections?
any additional information you can provide might prove helpful.
Bob
| |||||
| 3673.2 | Infos requested, hopefully answered | LEMAN::BRUNNER | FF Frame Finder | Thu Jul 11 1996 14:25 | 8 |
Hi Bob,
Thanks for taking care on that one...
Rev is V1.5.2 and there were 4 Ethernet ports and the FDDI port SAS
connected, other 2 Ethernet ports were free.
Regards, Walter
| |||||
| 3673.3 | What the util.c code does might hold an answer.... | NETCAD::BATTERSBY | Don't use time/words carelessly | Thu Jul 11 1996 15:11 | 9 |
Well I can't help much beyond this point. The firmware rev is
a proven shippable rev (1.5.2), which at least suggests that
the hardware rev is also a probable shipping rev.
The analysis of how the error code of 3000 is related to the
util.c code where the crash occured, is probably the key, and
I don't have access to that code. Someone with access to the
util.c code routine will have to provide some insight.
Bob
| |||||