[c-nsp] 2960-X Reboot Loop
Christopher Werny
cwerny at ernw.de
Tue Nov 8 07:37:58 EST 2016
Hello,
may I query the wisdom of this list for feedback regarding an issue we have
with a 2960-X
Since today, our 2960-X is in a rebooting loop and I see the following error
messages on the local console during the boot process:
Initializing Flash...
mifs[5]: 12 files,Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Err: Interrupt: Machine check (0x200): Data access error:
PC: 0x1f19f8bc, MSR: 0x00021000, ESR: 0x00000000, MCSR: 0x84800000
(Bailed out.)
Panic: Too many exceptions: Turn off Machine Check interrupt!!
1 directories
mifs[5]: Total bytes : 1806336
mifs[5]: Bytes used : 834560
mifs[5]: Bytes available : 971776
mifs[5]: mifs fsck took 2 seconds.
mifs[6]: 1 files, 1 directories
mifs[6]: Total bytes : 3870720
mifs[6]: Bytes used : 971264
mifs[6]: Bytes available : 2899456
mifs[6]: mifs fsck took 1 seconds.
mifs[7]: 5 files, 1 directories
mifs[7]: Total bytes : 258048
mifs[7]: Bytes used : 8192
mifs[7]: Bytes available : 249856
mifs[7]: mifs fsck took 0 seconds.
mifs[8]: 5 files, 1 directories
mifs[8]: Total bytes : 258048
mifs[8]: Bytes used : 8192
mifs[8]: Bytes available : 249856
mifs[8]: mifs fsck took 0 seconds.
mifs[9]: 9 files, 2 directories
mifs[9]: Total bytes : 122185728
mifs[9]: Bytes used : 48398848
mifs[9]: Bytes available : 73786880
mifs[9]: mifs fsck took 45 seconds.
...done Initializing Flash.
Loading "flash:c2960x-universalk9-mz.152-4.E1.bin"...Verifying image
flash:c2960x-universalk9-mz.152-4.E1.bin....................................
............n
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@
File "flash:c2960x-universalk9-mz.152-4.E1.bin" uncompressed and installed,
entry point: 0x3000
executing...
: Unexpected exception to CPUvector 200, PC = 36A0484
-Traceback= 0x36A0484z
=== Flushing messages () ===
Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version
15.2(4)E1, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Thu 28-Jan-16 15:56 by prod_rel_team
Machine Check Exception (0x0200)!
ESR: 0x00000000
SRR0: 0x036A0484 SRR1: 0x00029200 SRR2: 0x02F35B70 SRR3: 0x00028000
MCSR: 0x84800000
L2MCSR: 0x00000000
CPU Register Context:
Vector = 0x00000200 PC = 0x036A0484 MSR = 0x00029200 CR = 0x00000000
LR = 0x0369C1A4 CTR = 0x0369421C XER = 0xE000007E
R0 = 0x00000000 R1 = 0x0779DD88 R2 = 0x00000000 R3 = 0x00000000
R4 = 0x036A0484 R5 = 0x00029200 R6 = 0xBEEFCAFE R7 = 0xBEEFCAFE
R8 = 0x00400080 R9 = 0x00000001 R10 = 0x07791160 R11 = 0x07791150
R12 = 0x33003033 R13 = 0x1F1828CC R14 = 0x02918E6C R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x00000000
R24 = 0x00000000 R25 = 0x00000000 R26 = 0x00000000 R27 = 0x00000000
R28 = 0x00000000 R29 = 0x00000000 R30 = 0x00000000 R31 = 0x00000000
Stack trace:
PC = 0x036A0484, SP = 0x0779DD88
Frame 00: SP = 0x00000000 PC = 0x02951BEC
The only thing I was able to find was a post on the support forum with the
same issue, but with no resolution. I wasn't able to find bug id that would
indicate an IOS bug (but my search skills may have failed me).
https://supportforums.cisco.com/discussion/13092381/cisco-switch-2960-x-seri
es-error
I need to check with TAC, but from your point of view, does it look more
like a hardware failure or a potential IOS bug?
Thanks in advance for your feedback
Cheers,
Christopher
More information about the cisco-nsp
mailing list