Re: 2600 Router Crash

welch_michael · ‎06-02-2006

My 2600 crashed and it won't reboot propperly. It isses the following error durring startup and then restarts again:

*** System received a SegV exception ***

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

PC = 0x80464078, Vector = 0x100, SP = 0x82aca3d8

Any ideas? I tried reloading the IOS using tftp via rommon. didn't work

Thanks

-Michael

Here is the full output from the console:

==================================================

System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)

TAC:Home:SW:IOS:Specials for info

C2600 platform with 65536 Kbytes of main memory

program load complete, entry point: 0x80008000, size: 0xf47040

Self decompressing the image : ###################################################################################################################################################################################################################################################################### [OK]

Smart Init is enabled

smart init is sizing iomem

ID MEMORY_REQ TYPE

000094 0X000B3B80 C2600 Single Fast Ethernet

000043 0X00027A80 Single port Ethernet CPU

0X00098670 public buffer pools

0X00211000 public particle pools

TOTAL: 0X00384C70

If any of the above Memory Requirements are

"UNKNOWN", you may be using an unsupported

configuration or there is a software problem and

system operation may be compromised.

Rounded IOMEM up to: 4Mb.

Using 6 percent iomem. [4Mb/64Mb]

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph

(c) of the Commercial Computer Software - Restricted

Rights clause at FAR sec. 52.227-19 and subparagraph

(c) (1) (ii) of the Rights in Technical Data and Computer

Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

Cisco Internetwork Operating System Software

IOS (tm) C2600 Software (C2600-IK9O3S3-M), Version 12.3(17a), RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Mon 12-Dec-05 14:13 by evmiller

Image text-base: 0x80008098, data-base: 0x81A044A4

00:00:09 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 100, PC = 80464078

-Traceback= 80464078 8001D440 8001D4D0 8002A10C 804DD5DC 804DD6D0 8045B27C 80373E04 80374004 80462868 80465F08

Writing crashinfo to flash:crashinfo_19930301-000009

=== Flushing messages (00:00:09 UTC Mon Mar 1 1993) ===

Queued messages:

*Mar 1 00:00:09.539: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

*Mar 1 00:00:04.659: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up

*** System received a SegV exception ***

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

PC = 0x80464078, Vector = 0x100, SP = 0x82aca3d8

Roberto Salazar · ‎06-02-2006

Hello,

Unfortunately, the tracebacks needs to be decoded. You need to get TAC decode it and analyze it.

or You can try another image to boot it might be corrupted.

Anand Narayana · ‎06-03-2006

Hi Micheal,

Explanation: Debugging or informational messages are being generated faster than they can be displayed on the console. To ensure that the messages could be seen, the rest of the system has been paused until the console output catches up. This condition might cause an interruption in time-critical operations (for example,maintaining an ISDN link).

Recommended Action: To reduce the number of debugging or informational messages that are displayed, use conditional debugging and turn off console logging. Enter the no logging console guaranteed command, or turn off link-state messages for some other interfaces.

hope this helps.

rate this post.