greetings everyone
this is about an issue i am facing with my Cisco 2960x switches. i did a firmware upgrade from 152-7.E10 to 152-7.E11 image which currently is the recommended one.
Unfortunately for some strange reason, after reboot the switch goes into an endless loop without completing the booting process properly. I tried several times to enter to ROMMON and when the time comes that it is asking me whether i want to proceed with default configuration or not, i choose yes but again it is continuously going into a loop.
below is the message i am getting. i have also attached the output during booting.
== Flushing messages (00:00:02 UTC Mon Jan 2 2006) ===
Buffered messages:
Queued messages:
*Jan 2 00:00:02.523: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
*Mar 1 00:00:58.356: Read env variable - LICENSE_BOOT_LEVEL =
*Jan 2 00:00:00.080: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c2960x_lanbase Next reboot level = lanbase and License = No valid license found
Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version 15.2(7)E11, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2024 by Cisco Systems, Inc.
Compiled Fri 23-Aug-24 13:25 by mcpre
Debug Exception (Could be NULL pointer dereference) Exception (0x2000)!
SRR0 = 0x02D8C074 SRR1 = 0x00029200 SRR2 = 0x03B91F50 SRR3 = 0x00029200
ESR = 0x00000000 DEAR = 0xD267131F TSR = 0x84000000 DBSR = 0x01000000
CPU Register Context:
Vector = 0x00002000 PC = 0x03B91F50 MSR = 0x00029200 CR = 0x39000033
LR = 0x03B91EE8 CTR = 0x007D12E8 XER = 0x80000077
R0 = 0x03B91EE8 R1 = 0x088D1B18 R2 = 0x00000000 R3 = 0x050E104C
R4 = 0x00000000 R5 = 0x00000000 R6 = 0x00000000 R7 = 0x00000025
R8 = 0x00000000 R9 = 0x05950000 R10 = 0x088AE748 R11 = 0x00000000
R12 = 0x39000039 R13 = 0x1F183AFC R14 = 0x007FB698 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 = 0x05660000
R28 = 0x00000009 R29 = 0x03B8CE78 R30 = 0x088C949C R31 = 0x00000000
Stack trace:
PC = 0x03B91F50, SP = 0x088D1B18
Frame 00: SP = 0x088D1B28 PC = 0x03B91EE8
Frame 01: SP = 0x088D1B30 PC = 0x034A13C0
Frame 02: SP = 0x088D1B38 PC = 0x034A0AF8
Frame 03: SP = 0x088D1B48 PC = 0x02D3C734
Frame 04: SP = 0x088D1B68 PC = 0x02D3C910
Frame 05: SP = 0x088D1B80 PC = 0x02D3CA88
Frame 06: SP = 0x088D1BB0 PC = 0x007FB45C
Frame 07: SP = 0x088D1CB0 PC = 0x007FB6F4
Frame 08: SP = 0x088D1CB8 PC = 0x03B9353C
Frame 09: SP = 0x00000000 PC = 0x03B8F22C
The password-recovery mechanism has been triggered, but
is currently disabled. Access to the boot loader prompt
through the password-recovery mechanism is disallowed at
this point. However, if you agree to let the system be
reset back to the default system configuration, access
to the boot loader prompt can still be allowed.
Would you like to reset the system back to the default configuration (y/n)?y
when i choose (yes), then same issue happens again,
Any idea please?
thank you
