Cisco 2621XM Router automatic reboots

Unanswered Question
Aug 7th, 2008
User Badges:


i have cisco 2621Xm router,when power up this router its automatically reboots and shown the following error in console.


Unexpected exception to CPUvector 100, PC = 8

-Traceback= 80024C20 80027654 8002349C 8043555C 804319C0 80431AB8 803EA588 80325

7C0 803259C8 803F5020

Free space check for flash:crashinfo_19930301-000005 failed (0/303)

Queued messages

*** System received a SegV exception ***

signal= 0xb, code= 0x100, context= 0x80fd063c

PC = 0x80024c20, Vector = 0x100, SP = 0x81121d98

Please help me to resolve this

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
graemeporter Thu, 08/07/2008 - 03:06
User Badges:
  • Bronze, 100 points or more

Hi there,

Has this just started happening all of a sudden, or is it something that's been getting worse?

Have you made any hardware changes (DRAM/Flash upgrades/WIC installs/removes), software changes (IOS or SDM upgrades), or configuration changes recently?

What version of IOS is on the router? How much memory and flash do you have in the router?

Is the router able to boot into IOS at all, or does it constantly crash and reboot, crash and reboot (etc)?

If you can't get into IOS, can you send a break signal to the router during power-on and get into ROMMON mode?

In the meantime, please give this a try:

If you can get into ROMMON, try using XMODEM to copy a new IOS image (either a new version, or if there is no newer version, download a fresh copy of this one from CCO, delete the existing one from flash, and copy your new copy back to flash).

Let us know how you get on.

Kind regards,


Richard Burts Thu, 08/07/2008 - 04:07
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN


The traceback message is an indicator of a software problem. This message:

Free space check for flash:crashinfo_19930301-000005 failed (0/303)

indicates that IOS was attempting to create a crashinfo file (and failed) which is another sign of a problem with the IOS.

Graeme asks some good questions and knowing the answers might be helpful. But the most important thing that Graeme says is the suggestion to replace the IOS, which I believe is the real problem here.




This Discussion