Re: crashdump 1 - - -on a catalyst 4006

srooplal · ‎07-10-2002

Is there a tool that can diagose the output of a "sh crashdump 1" of a catalyst 4006 - - - -- just like the stack decoder?

Prashanth Krishnappa · ‎07-10-2002

We do not have one on CCO. You'll need to open a TAC case. Provide sh tech, sh crashdump 1 and show env 1 for CatOS 5.x and show nvramenv 1 for CatOS 6.x /7.x outputs to the TAC Engineer

bsivasub · ‎07-10-2002

IMHO cat4006 sup2 has few real software crashes. Just because you have some values in the crashdump doesn't mean the switch actually crashed. it may be unintiliazed values. Also power failures can cause the crashdump to have certain invalid values which again doesn't mean the switch crashed. Please post the output of the command.

There is no stack decoder since it hardly will be ever used ...:)

srooplal · ‎07-22-2002

Here is the crashdump info:

FS-4006-01> (enable) sh crashdump 1

Version and date:

GSP: 7.1(1.0) NMP: 7.1(1) YMD 02/07/08 time 09:44

Register contents:

meteor reset cause 0x000000c2

epc 0x00000000304bfd44 sp 0x00000000413fefe8

ra 0x0000000030195c64 at 0x0000000030ba0000

v0 0x0000000000000002 v1 0x000000000000000a

hi 0x00000000005e1040 lo 0x0000000000000056

a0 0x0000000000000002 a1 0x0000000000000010

a2 0x0000000055555555 a3 0x0000000000000000

sr 0xffffffffb400ac33 badva 0x0000000000000006

cause 0x0000000000004010 gp 0x0000000030918f20

t0 0x0000000040883990 t1 0x000000000000000e

t2 0x0000000000000003 t3 0x0000000000000000

t4 0x0000000000000000 t5 0x000000000000c1c8

t6 0x00000000308c2ce8 t7 0x0000000000000000

t8 0x00000000413fed30 t9 0x00000000409f0af4

s0 0x00000000308fec40 s1 0x0000000040883990

s2 0x00000000405a7e10 s3 0x0000000000000002

s4 0xffffffffffffffff s5 0x0000000000000019

s6 0x0000000000000019 s7 0x0000000075650000

s8 0x00000000413fefe8

feir 0x0000000030cec478 fcsr 0x0000000001000000

f0 0x5374617456616c75 f1 0x655074723a3a746f

f2 0x74616c56616c7565 f3 0x0000000000000000

f4 0x5374617456616c75 f5 0x655074723a3a7661

f6 0x6c75657350657253 f7 0x65636f6e64355365

f8 0x6300000000000000 f9 0x5374617456616c75

f10 0x655074723a3a7661 f11 0x6c75657350657253

f12 0x65636f6e64314d69 f13 0x6e00000000000000

f14 0x5374617456616c75 f15 0x655074723a3a7661

f16 0x6c75657350657253 f17 0x65636f6e64486f75

f18 0x7200000000000000 f19 0x5374617456616c75

f20 0x655074723a3a7661 f21 0x6c75655261746535

f22 0x5365630000000000 f23 0x5374617456616c75

f24 0x655074723a3a7661 f25 0x6c75655261746531

f26 0x4d696e0000000000 f27 0x5374617456616c75

f28 0x655074723a3a7661 f29 0x6c75655261746548

f30 0x6f75720000000000 f31 0x7ff8000000000000

Exception Handlers Executing: 0

Thread flags: 0x0000000000000049

Stack contents:

Popped part:

0x00000001 0x413fef60 0x413feef8 0x304c002c

0x409533b0 0x00000000 0x00000000 0x00000000

0x00000000 0x304c3160 0x413fef18 0x304b8814

0x00000000 0x00000001 0x409533b0 0x413fef60

0x00000000 0x00000000 0x00000011 0x00000011

0x413fef40 0x413fef90 0x413fef48 0x40262ed0

0x00000006 0x00000001 0x409533b0 0x413fef60

0x00000000 0x000007d2 0x00000002 0x304115c8

0x00000000 0x404e78a4 0x405a7e04 0x00000000

0x00000000 0x00000000 0x408ae724 0x40883990

0x413fef90 0x305d1648 0x405a7e04 0x00000010

0x413fefa0 0x304be420 0x405a7e04 0x405a7da4

0x405a7e24 0x00000000 0x00000000 0x00000010

0x405a7e80 0x0000000c 0x308fec40 0x40883990

0x405a7e10 0x00000002 0xffffffff 0x00000019

0x00000019 0x413fefe8 0x304bfda4 0x000003b6

Pushed part:

0x405a7e10 0xffffffff 0x308fb814 0x413ff040

0x413ff070 0x30195c64 0x00000002 0x000000a0

0x413ff040 0x00000017 0x00000000 0x4025a9cd

0x6f666645 0x6e764f74 0x68657228 0x31290002

0x00d40320 0x00000002 0x00000002 0x00000002

0x00000019 0x30174764 0x00000001 0x00000001

0x0000000d 0x30ceabe0 0x00000001 0x00000000

0x78000000 0x56616c75 0x65770000 0x56616c75

0x3a3a6e65 0x3057d540 0x30906a3c 0x00000003

0x00000001 0x4025a92d 0x01000f80 0x00340000

0x1e008a00 0x61742d78 0x413ff098 0x3057c650

0x1e008a00 0x30679470 0x00d00300 0x00000000

0x00000000 0x00000000 0x013abb48 0x00d00300

0x00000000 0x00000000 0x413ff0c8 0x3058eaac

0x1e008a00 0x61742d78 0x303ae6ac 0x61742d78

0x00000000 0x61742d78 0x1e008a00 0x3000aecc

0x00000000 0x61742d78 0x00000000 0x413ff100

0x305db734 0x305db63c 0x3a3a6e65 0x75650000

0x413ff128 0x30679370 0x00004000 0x56616c75

0x00000001 0x61742d78 0x413ff128 0x305e89c8

0x00000000 0x00000000 0xfffffffe 0x00000001

0x413ff140 0x305e80f8 0x00000000 0x00000000

0x00000000 0x00000000 0x413ff158 0x3000cf90

0x00000000 0x00000000 0x00000000 0x00000000

0x00000000 0x306763e8 0x00000000 0x00000000

0x00000000 0x00000000 0x00000000 0x00000000

Saved checksum: 0x96a80997 Computed checksum: 0x96a80997

Prashanth Krishnappa · ‎07-22-2002

Are you running the K8(weak Crypto) or the K9(strong crypto)?. I see that you are running 7.1(1) which was the first release in 7.x. I suggest that you consider upgrading to 7.2(2)

bsivasub · ‎07-22-2002

This is a valid crashdump (meaning it is a software crash). please open a TAC case so that TAC can decode the crash for you and recommend the next course of action.

srooplal · ‎07-23-2002

Case opened C929321 - - thank you