MSFC1 crashes with a Cache Parity Exception error message

TCC_2 · ‎06-22-2009

Resolution

Multilayer Switch Feature Card 1 (MSFC1) does not contain Error-Correcting Code (ECC) memory protection. Therefore, the MSFC crashes if a parity error is detected. These error messages may occur in the following locations:

On the console:


*** System received a Cache Parity Exception *** 
signal= 0x14, code= 0xa405c428, context= 0x60dd1ee0 
PC = 0x6025b2a8, Cause = 0x6420, Status Reg = 0x34008002

In the output of the show version command:

<output truncated>

System returned to ROM by processor memory parity error at PC 0x6020F4D0, 
address 0x0 at 18:18:31 UTC Wed Aug 22 2001   

<output truncated>

In the crashinfo file recorded in the bootflash: or console:

Error: primary data cache, fields: data, SysAD

virtual addr 0x4B288202, physical addr(21:3) 0x288200, vAddr(14:12) 0x0000

virtual address corresponds to pcimem, cache word 0

Address: 0x4B288200 not in L1 Cache

Address: 0x4B288202 Can not be loaded into L1 Cach

If the parity errors occur more than once, the MSFC needs to be replaced. If the parity error happens only once, it could be a single event upset, and the MSFC should be monitored.

For more information on parity errors, refer to Processor Memory Parity Errors (PMPEs).