cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

4900m crash/reboot issue

enpingado
Beginner
Beginner

I have a 4900m with IOS 12.2(53) SG2.

Over the past 6 months, there have been about 5 instances where the switch has rebooted itself.  Most of them occuring within the last few weeks. So it seems to be getting worse. 

dumping the log data showed this at the end

Jawa Crash Data:

Interrupt Mask: 0xE100

Interrupt: 0x2000

Forerunner CRC Error

Is this telling me i am having possible hardware failures like RAM?

13 REPLIES 13

Reza Sharifi
Hall of Fame Expert Hall of Fame Expert
Hall of Fame Expert

You should open a ticket with TAC and send them the crash file and any other info you have.  It maybe a memory issue.

HTH

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend
Over the past 6 months, there have been about 5 instances where the switch has rebooted itself.

Sounds like an IOS issue.

Can you attach/post the crashinfo files?

InayathUlla Sharieff
Cisco Employee
Cisco Employee

Hi,

Please send me the  show tech . or show ver/show platform crashdump.

Regards

Inayath

here is crash dump, sorry i have it only as scanned images.

I have a report from a second crash. 

similar to the previous dump with a few exceptions;

Machine Check Interrupt Count: 1c9910b

L1 Instruction Cache Parity Errors: 0

L1 Instruction Cache Parity Errors (CPU30): 0

L1 Data Cache Parity Errors: 1c9910b

Jawa Crash Data:

Interrupt Mask: 0xe100

Interrupt: 0x1000

The L1 info, is that related to CPU L1 cache?  It is looking like its a hardware issue not a software issue.

      

I found this on the 12.2 (54)SG release notes:

Parity errors in the CPU's cache cause IOS to crash with a crashdump file like the following:
Switch# show platform crashdump
VECTOR 0
*** CRASH DUMP ***
02/09/2009 10:10:30
Last crash: 02/09/2009 10:10:30
Build: 12.2(20090206:234053) IPBASE
buildversion addr: 13115584
MCSR: 40000000 <--- non-zero value!
.
The key pieces of data are "VECTOR 0" and a MCSR value of 40000000, 20000000, or 10000000.

Workaround: Enter the show platform cpu cache command to lanuch an IOS algorithm that
detects and recovers from parity errors in the CPU's cache. You will obtain a running count of the
number of CPU cache parity errors that have been successfully detected and corrected on a running
system:

Switch# show platform cpu cache
L1 Instruction Cache: ENABLED
L1 Data Cache: ENABLED
L2 Cache: ENABLED
Machine Check Interrupts: 5
L1 Instruction Cache Parity Errors: 3
L1 Instruction Cache Parity Errors (CPU30): 1
L1 Data Cache Parity Errors: 1

CSCsx15372

I get a similar return with non zero Parity errors.  Is the workaround saying that running the command "show platform cpu cache" will fix the errors? Or is that a temporary thing related to the IOS. 

I am wondering if i should update the IOS to solve this or if the issue is really a hardware problem.

Thanks