cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
303
Views
0
Helpful
2
Replies

7206 Unexpected exception s, started after IOS upgrade

dlostboy
Level 1
Level 1

We have a 7206 in service. We began having a problem every couple of days where the router would crash and require a power cycle to fix the problem. Some people I've spoken to suggest bad ram but this occured immediately after we upgraded from 7200-is-mz.121-8 to 7200-is-mz.121-13a. Unless the newer image pushed the memory usage up beyond levels it ever had reached before (with months in service), I find that to be rather coincidental.

#show mem

Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)

Processor 61854740 226146496 95805484 130341012 130169452 130173088

I/O F000000 16777216 3495484 13281732 13188856 13269660

I'm attaching the crash information below, does anyone have any thoughts on this?

Thanks for any ideas,

John

Unexpected exception, CPU signal 10, PC = 0x6055B5A0

$0 : 00000000, AT : 200DD609, v0 : 00000000, v1 : 00000038

a0 : 00000001, a1 : 3D800000, a2 : 00000002, a3 : 00000000

t0 : 6059FC98, t1 : 3400F900, t2 : FFFFFFFD, t3 : EED48571

t4 : 600DD604, t5 : 80000000, t6 : C03B2B93, t7 : 00000201

s0 : 617F2920, s1 : 00000200, s2 : 3D800000, s3 : 00000000

s4 : 00000001, s5 : 00000000, s6 : 61B6C0B0, s7 : 00000000

t8 : 6055A048, t9 : 00000000, k0 : 617EEBC0, k1 : 00000014

gp : 61674A60, sp : 61605958, s8 : 00000000, ra : 60563960

EPC : 6055B5A0, ErrorEPC : 600DD604, SREG : 3400F902

Cause 00004018 (Code 0x6): Instruction Bus Error exception

-Traceback= 6055B5A0 60563960

=== Flushing messages (16:14:00 EDT Mon Oct 13 2003) ===

Buffered messages:

Queued messages:Free space check for bootflash:crashinfo_20031013-201400 failed

(1/32768)

-Traceback= 6055B5A0 60563960

*** System received a Bus Error exception ***

signal= 0xa, code= 0x18, context= 0x617f0e04

PC = 0x6055db98, Cause = 0x4420, Status Reg = 0x34008002

2 Replies 2

vkapoor5
Level 5
Level 5

You can probably remove the modules and try to isolate the problem. Also check for minimum recommended RAM, if you suspect it to be an issue.

I wish I could; this is in production and we don't have a spare chassis for this application so taking a module out and waiting a week to see if it dies isn't an option.

Thanks for the suggestion tho'. I'm glad to see people trying to help.

John