[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

4327.0. "DECbridge900MX reseting" by KERNEL::FREKES (Like a thief in the night) Wed Apr 02 1997 12:30

Entry # = 1
Entry Status = 0 (valid)
Entry ID = 10
Firmware rev = 1.4
reset count = 29
Timestamp = 0 0
Write Count = 7
FRU Mask = 0
Test ID = DEAD
Error Data = SR=2104 PC=03035916 Error Code=0000202c Proc CSR=756D

D0 = 00000000
D1 = 00002100
D2 = 00000001
D3 = 00002000
D4 = 0004a8c0
D5 = 00000000
D6 = 00000002
D7 = 0000FFFF
A0 = 0000002C
A1 = 04033025
A2 = 0004A870
A3 = 000615A8
A4 = 030030D8
A5 = 03020000
A6 = 0004A84  <- this was only a 7 digit error code
A7 = 0004A868


The error data from another dump is shown below, but the customer did not mail
me the full registers.

Error Code SR=2100 PC=030358EA Error Code=00002010 Proc CSR=756D

I am aware that the customer is running an old version of firmware, but he would
like to know if he is looking at a hardware issue, before he attempts to 
upgrade.

Regards
	Steven Freke
T.RTitleUserPersonal
Name		DateLines
4327.1Upgrade the image, it's probably not the hardware...NETCAD::BATTERSBYWed Apr 02 1997 15:0210
    I vaguely remember a firmware related problem with that old
    rev of firmware that had something to do with those error
    codes of 2010 and 202C, and how it may have been related to module
    resets occuring. I'm confident that it's not a hardware problem and 
    I'd reccommend upgrading to a more current of firmware, before
    worrying about shipping hardware back.
    If it turns out to be the old rev of firmware, the customer has
    saved the hassle of having to pack up and ship back the hardware.
    
    Bob
4327.2NETCAD::HOPPEWed Apr 02 1997 15:1918
    I don't have the map file for V1.4 handy, so I don't know
    where the module reset.  But, I can tell you that error code
    202c is referring to the processor trying to execute an unimplemented
    opcode.  Error code 2010 is referring to an illegal opcode
    error.
    
    Is your module resetting often?  Are there any specific conditions
    that you are aware of that coincide with the module resetting?
    (setting a filter, certain traffic, etc?)
    
    I recommend upgrading to the latest firmware (V1.7.0) and
    watching to see if these errors still occur.  You probably
    have run into a firmware bug in V1.4.  I could give you
    more information if you obtain a similar error log
    with V1.7.0.
    
    Chris
4327.3Upgrade to latest rev should cure these methinks too...NETCAD::BATTERSBYWed Apr 02 1997 16:5412
    Looking through some old mail, and reading the release notes
    associated with the follow-on release v1.5X, I think I've
    determined that the error code 2010 was related to an old uart
    code routine  problem which may have caused the module to reset. 
    The 202C error code I think was related to an old code problem 
    where the module would crash if pinged by a 1500 byte packet.
    I'm lacking some clarity in the details of both these error codes,
    but also feel confortable with saying that upgrading to a current 
    rev of DECswitch firmware (V1.70) should most likely eliminate 
    these two error codes from re-occuring.
    
    Bob