Router 3640 Constantly rebooting

[newnetman]

Hi All,

Can someone please help me out as this router is just rebooting after every single decompression. Part of the messages is here included maybe this could help you help me?

Thanks

Cisco IOS Software, 3600 Software (C3640-JK9O3S-M), Version 12.4(10b), RE-

Possible software fault. Upon reccurence, please collect

crashinfo, "show tech" and contact Cisco Technical Support.

--------------------------------------------------------------------

Traceback=

$0 : 00000000, AT : 00000000, v0 : 00000000, v1 : 00000000

a0 : 00000000, a1 : 00000000, a2 : 00000000, a3 : 00000000

t0 : 00000000, t1 : 00000000, t2 : 00000000, t3 : 00000000

t4 : 00000000, t5 : 00000000, t6 : 00000000, t7 : 00000000

s0 : 00000000, s1 : 00000000, s2 : 00000000, s3 : 00000000

s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 00000000

t8 : 00000000, t9 : 00000000, k0 : 00000000, k1 : 00000000

gp : 00000000, sp : 00000000, s8 : 00000000, ra : 00000000

EPC : 00000000, ErrorEPC : 00000000, SREG : 00000000

MDLO : 00000000, MDHI : 00000000, BadVaddr : 00000000

Cause 00000000 (Code 0x0): Interrupt exception

No fault history 0xFFFFFFFF. Need 11.1 (2) or higher ROM

SYSTEM INIT: INSUFFICIENT MEMORY TO BOOT THE IMAGE!

%Software-forced reload

00:00:13 UTC Fri Mar 1 2002: Breakpoint exception, CPU signal 23, PC = 0x604F20

3C

--------------------------------------------------------------------

Possible software fault. Upon reccurence, please collect

crashinfo, "show tech" and contact Cisco Technical Support.

--------------------------------------------------------------------

-Traceback= 0x604F203C 0x604F06E4 0x6050D0E8 0x6050E1F0 0x605CE908 0x605CEA28 0x

605D0C38 0x6052D074 0x605298D0 0x6044E020 0x6044E83C 0x6044F684 0x604F9F14 0x604

F2E84 0x604F3000 0x604F8C90

$0 : 00000000, AT : 63E10000, v0 : 00000028, v1 : 00000000

a0 : 00000000, a1 : 00008000, a2 : 00000000, a3 : 62B00000

t0 : 63E434C0, t1 : 64050000, t2 : 604F8D90, t3 : FFFF00FF

t4 : 62B00234, t5 : FFFFFFFF, t6 : 00000000, t7 : 00000000

s0 : 00000007, s1 : 00000000, s2 : 639F0000, s3 : 63A00000

s4 : 603BF770, s5 : 00000000, s6 : 00000000, s7 : 62B00000

t8 : 64050000, t9 : FFFFFFF5, k0 : 00000018, k1 : 00000000

gp : 63E13B20, sp : 645C7E90, s8 : 00000000, ra : 604F06E4

EPC : 604F203C, ErrorEPC : BFC04560, SREG : 3401FF03

MDLO : 00000000, MDHI : 00000006, BadVaddr : 77ABFF7F

Cause 00000024 (Code 0x9): Breakpoint exception

-Traceback= 0x604F203C 0x604F06E4 0x6050D0E8 0x6050E1F0 0x605CE908 0x605CEA28 0x

605D0C38 0x6052D074 0x605298D0 0x6044E020 0x6044E83C 0x6044F684 0x604F9F14 0x604

F2E84 0x604F3000 0x604F8C90

Writing crashinfo to flash:crashinfo_20020301-000013

*** System received an unknown failure ***

signal= 0x0, code= 0x0, context= 0x6404a088

PC = 0x604fa18c, Cause = 0x20, Status Reg = 0x3401c102

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

Self decompressing the image : #################################################

################################################################################

################################## [OK]

Smart Init is enabled

smart init is sizing iomem

ID MEMORY_REQ TYPE

000037 0X00056400 Combination Single Ethernet 2 WAN

000043 0X00027A80 Single Port Ethernet

0X00209770 public buffer pools

0X00211000 public particle pools

TOTAL: 0X004985F0

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: 5Mb.

Using 3 percent iomem. [5Mb/128Mb]

[Richard Burts]

Thanks for posting the console output. It is helpful. I see a couple of things that may help identify what is going on. I see this message in the output:

SYSTEM INIT: INSUFFICIENT MEMORY TO BOOT THE IMAGE!

%Software-forced reload

this error would seem to indicate a problem that there is not sufficient physical memory to load the image.

I also see several traceback messages. A traceback is almost always a sign of a software problem.

Both of these observations lead me to wonder whether this software has run on this router successfully before? Is this a new image version on this router? (or is it possibly a new router?)

My first suggestion would be to try a different version of code - perhaps an older version or a lower feature set which might have less memory requirements.

My second suggestion would be to open a case with TAC if the router is under maintenance. The messages indicate that it wrote a crash info file. The TAC will have the ability to examine the file and determine what it indicates about the nature of the problem.

HTH

Rick