[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

3358.0. "some explanations, please..." by BERFS4::NORD () Wed Mar 13 1996 04:36


	Good morning, good evening and something betwwen for the rest of the
	world (you know my entry for some questions),


	I need some clarification about an entry at a DECswitch 900 EF:

	(I think, I've not ask this question befor)

	1. What is a "Test Id = DEAD"?

	2. Who to interprete "Timestamp"?

	3. Are the entries below alarming? 

	4. Is there a short description for the possible entries and their
	   meening (I've asked some entries befor about a internals-training,
	   but unfortunatly I got no answer)





DECswitch 900EF - slot 3
==============================================================================

                                DUMP ERROR LOG
                            Current Reset Count: 4

==============================================================================


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   = 8
Timestamp     =    0    0    0
Write Count   = 5
FRU Mask      = 0
Test ID       = DEAD
Error Data    = SR=2700 PC=03069360 Error Code=00000203 ProcCsr=4F69
Registers     = D0=00000064 D1=00000001 D2=00000005 D3=00000800
                D4=0007DC9C D5=00068B64 D6=00000000 D7=0000FFFF
                A0=00000004 A1=0004F430 A2=00055E1C A3=00000002
                A4=030020D8 A5=03020000 A6=0004B88C A7=0004B86C
Dump another entry [Y]/N? 
Entry #       = 0
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 10
Firmware Rev  = 1.4
Reset Count   = 4
Timestamp     =    0    0    0
Write Count   = 5
FRU Mask      = 0
Test ID       = DEAD
Error Data    = SR=2710 PC=000758E0 Error Code=0000200C ProcCsr=6F69
Registers     = D0=00000001 D1=FFFFFFFF D2=00000400 D3=00000800
                D4=00000002 D5=00000000 D6=00000000 D7=0000FFFF
                A0=00051F38 A1=00050238 A2=00062638 A3=0444E018
                A4=030020D8 A5=03020000 A6=000FD803 A7=0004A8BD
Dump another entry [Y]/N? 
==============================================================================

No more Error Log entries.
                       Press Return for Main Menu ...

DECswitch 900EF - slot 3
==============================================================================



	Many thanks in advance

	Wofgang Nord
	MCS at Berlin at Germany
T.RTitleUserPersonal
Name
DateLines
3358.1Some answers....NETCAD::BATTERSBYWed Mar 13 1996 12:3018
    I'll try to help answer some of your questions.
    
    Test Id = DEAD  - This indicates an error reported by the operational
                      firmware. Typically if you see a alphanumeric
                      followed by some "words" it means a diagnostic error.
    
    Timestamp       - The timestamp (as has been mentioned in here elsewhere)
                      is the timestamp since the last power up. A tick is
                      10 milliseconds.
    
    Your error log entries have been passed on to a firmware engineer to
    ascertain what they may be. I personally don't have a clue.
    
    As for internal training, I would recommend contacting Ed Buzzell
    (delni::buzzell).
    I hope this information is useful.
    
    Bob
3358.2NPSS::RAUHALAThu Mar 14 1996 18:0713
    The 203 error code is crashing because of an internal error
    detected by the operating system.  The 200C error code is
    a 68040 processor trap.  We have seen both of these and are
    working on a fix.

    They both happen as soon as the switch finishes diagnostics,
    at which point the switch will crash, run diags again, and
    then come on line.  While this is a problem, it's not that
    serious in that the 2nd attempt the switch will come online.
    Because it happens when a powerup or reset is triggered,
    most people will not notice it.  we are working on a fix...

    ken