[c-nsp] Software forced crash on 2651XM/12.3(6e)
christopher.a.kane at jpmchase.com
christopher.a.kane at jpmchase.com
Wed Sep 27 14:44:29 EDT 2006
> Put 'sh stack' in the crash decoder on CCO and see if it gets
> you any meaningful bug matches.
> Or upgrade to the latest 12.3 mainline code and see if it goes away.
Not to pick on you Rodney.....but I'd like to better understand why this
statement gets uttered so much. For those of us in large enterprises
(maybe the smaller ones too), code upgrades are rarely permitted on whim.
> Or open a TAC case and provide, sh stack, sh run, and any crashinfo
> file from bootflash.
On Wed, Sep 27, 2006 at 06:11:26PM +0100, Jee Kay wrote:
>> Just had this show up on a 2600:
>>
>> System returned to ROM by error - a Software forced crash, PC
>> 0x80709D4C at 12:02:40 CDT Wed Sep 27 2006
>> System image file is "flash:c2600-advipservicesk9-mz.123-6e.bin"
>>
>>
>> Anyone know what that means and/or how I might start to debug it?
>>
>> Thanks,
>> Ras
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
More information about the cisco-nsp
mailing list