cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
361
Views
0
Helpful
1
Replies

Cat c6509 E with Supervisor vs-s720-10g reload and Cache error detected!

Can you help me Cat c6509-E reload 


connect console  I see :

 

Initializing ATA monitor library...

Self extracting the image... [OK]
Self decompressing the image : ############################# [OK]

              Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706

 

Cisco IOS Software, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXI1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Sat 28-Mar-09 10:48 by prod_rel_team
Image text-base: 0x40101328, data-base: 0x421FFA10

 

Cache error detected!
  CPO_ECC     (reg 26/0): 0x000000B6
  CPO_CACHERI (reg 27/0): 0x84000000
  CP0_CAUSE   (reg 13/0): 0x00004800

Real cache error detected.  System will be halted.

Error: Primary data cache, fields: , 1st dword
Actual physical addr 0x00000000,
virtual address is imprecise.

 Imprecise Data Parity Error

 Imprecise Data Parity Error

 22:12:30 UTC Tue Mar 24 2015: Interrupt exception, CPU signal 20, PC = 0x413EB310

 

--------------------------------------------------------------------
   Possible software fault. Upon reccurence, please collect
   crashinfo, "show tech" and contact Cisco Technical Support.
--------------------------------------------------------------------


-Traceback= 414EDA90 
$0 : 00000000, AT : 42510000, v0 : 00000000, v1 : 00000001
a0 : 43757CC4, a1 : 00040110, a2 : 45762ECE, a3 : 00000000
t0 : 44997CF0, t1 : 00000000, t2 : D5303A40, t3 : 00003A40
t4 : 0000004F, t5 : 0000005F, t6 : 68C8F600, t7 : 00000000
s0 : BEDA4010, s1 : 00000000, s2 : 00000000, s3 : 44086D60
s4 : 45762ECC, s5 : 00000001, s6 : 00000080, s7 : 44080000
t8 : 45762ECC, t9 : 00000000, k0 : 841E6970, k1 : 02951800
gp : 4250FC60, sp : 44997D48, s8 : 4499848E, ra : 413EB310
EPC  : 414EDA90, ErrorEPC : 413EB310, SREG     : 3400F105
MDLO : 00159DC0, MDHI     : 00000000, BadVaddr : 00000000
DATA_START : 0x421FFA10
Cause 00004800 (Code 0x0): Interrupt exception
File bootflash:crashinfo_20150324-221230 Device Error :No such device


%Software-forced reload


 22:12:30 UTC Tue Mar 24 2015: Breakpoint exception, CPU signal 23, PC = 0x4171F5E0

 

--------------------------------------------------------------------
   Possible software fault. Upon reccurence, please collect
   crashinfo, "show tech" and contact Cisco Technical Support.
--------------------------------------------------------------------


-Traceback= 4171F5E0 4171D184 40F4F26C 40F4F450 40F4F670 4171282C 
$0 : 00000000, AT : 42510000, v0 : 441D0000, v1 : 424C0000
a0 : 00000000, a1 : 00008100, a2 : 00000000, a3 : 00000000
t0 : 0000FF00, t1 : 3401FF01, t2 : 41712918, t3 : FFFF00FF
t4 : 41712918, t5 : 73206265, t6 : 65746563, t7 : 20546865
s0 : 00000000, s1 : 424C0000, s2 : 00000000, s3 : 08000000
s4 : 42380000, s5 : 42380000, s6 : 41D90000, s7 : 00000001
t8 : 506D5CC4, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 4250FC60, sp : 50012420, s8 : 41D90000, ra : 4171D184
EPC  : 4171F5E0, ErrorEPC : 413EB310, SREG     : 3401FF03
MDLO : 00000000, MDHI     : 00000003, BadVaddr : 00000000
DATA_START : 0x421FFA10
Cause 00000024 (Code 0x9): Breakpoint exception


=== Flushing messages (22:12:30 UTC Tue Mar 24 2015) ===

Buffered messages:
Queued messages:
*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.


Firmware compiled 19-Feb-09 20:18 by weizhan Build [100]

 


*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Error address Lo=0x4010
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Error address Hi=0x1EDA
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Interrupt Hi reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Interrupt lo reg=0x8000000
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-DUMP: System controller Global Registers Dump
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: global hazard reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: soft reset cfg reg=0x10FFFF
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: global cfg reg=0x20
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: init status reg=0x8
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl cfg reg=0xE
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: prio map cfg reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ecc error log reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: parity error log reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: jtag idcode reg=0x5013102F
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: work status reg hi=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: work status reg lo=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc rxstat reg=0x11FE
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc txstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc mac cfg reg=0xE24
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: inbound rxstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: inbound txstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: io int stat reg=0x408
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: pcmcia cfg reg=0x1A0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: pcmcia stat reg=0x3C
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: bist go stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: bist done stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 0=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 1=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 2=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: obl debug reg 0=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: obl debug reg 1=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: rxq debug reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: txq debug reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: gigmac cfg reg=0x1001
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: gigmac stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-FATAL: An unrecoverable error has been detected. The system is being reset.
*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.

*Mar 24 22:12:30.695: %OIR-6-CONSOLE: Changing console ownership to switch processor

 

*** System received a Cache Parity Exception ***
signal= 0x14, code= 0x84000000, context= 0x441ce024
PC = 0x4171295c, Cause = 0x820, Status Reg = 0x34018002

System Bootstrap, Version 8.5(3)
Copyright (c) 1994-2008 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory

Autoboot: failed, BOOT string is empty
Autoboot executing command: "boot "

 

 

1 Reply 1

Hello Abubaker,

 

It crashed due to a parity error.

 

 Imprecise Data Parity Error

 Imprecise Data Parity Error

 

Which in other words means, a temporary error in memory. On single occurence adivice is to monitor the supervisor for re-occurence of such failure again. You can monitor it for 24 - 48 hours and if its a hard failure , the likelyhood of issue coming again is more and you need to replace supervisor. If it does not repeat you can consider this as a one time issue and contnue using it. 

Hope this helps and please always rate useful posts.

Thanks,

Madhu

 

 

Review Cisco Networking for a $25 gift card