From: Guyler, Rik (rguyler@shp-dayton.org)
Date: Fri Mar 31 2006 - 12:48:43 GMT-3
Victor, have you used the Output Interpretor on CCO? I find it pretty
useful for arcane messages like this one. I always include the actual error
message, the config and the "show version" info.
Rik
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Victor Cappuccio
Sent: Sunday, March 26, 2006 2:13 AM
To: Monty
Cc: CCIE LAB
Subject: Re: Unexpected exception
Ok Here you go, Do you need the tech-support ?? it's very long... I want to
learn how to read all that messages Thanks :D
Rack1R5#show context
S/W Version: Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-J1S3-M), Version 12.2(15)T16, RELEASE
SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 19-Apr-05 12:2
Exception occurred at: 03:07:56 UTC Mon Mar 1 1993
*Exception type: Bus Error (0x0200) *
CPU Register Context:
PC = 0x8002BD70 MSR = 0x00009032 CR = 0x22000008 LR = 0x8002BD00
CTR = 0x8000AAD0 XER = 0x0000FF48 DAR = 0x40800014 DSISR = 0x00000909
DEC = 0x1A9EBF69 TBU = 0x00000006 TBL = 0x65614079 IMMR = 0x68010031
R0 = 0x8300FDDE R1 = 0x82BA0D48 R2 = 0x825E0000 R3 = 0x829DD230
R4 = 0x00000BB8 R5 = 0x00000BB8 R6 = 0x00000001 R7 = 0x68010000
R8 = 0x00000000 R9 = 0x40800000 R10 = 0x03B79000 R11 = 0x829DEB1C
R12 = 0x00AC0EF9 R13 = 0xFFF48A24 R14 = 0x00000000 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x00000000
R24 = 0x00000001 R25 = 0x00000000 R26 = 0x00000001 R27 = 0x829DD090
R28 = 0x00000000 R29 = 0x82B266C8 R30 = 0x829DD090 R31 = 0x829DE838
Stack trace:
Frame 00: SP = 0x82BA0D48 PC = 0x8002BD00
Frame 01: SP = 0x82BA0D90 PC = 0x8002C35C
Frame 02: SP = 0x82BA0DA8 PC = 0x8033950C
Frame 03: SP = 0x82BA0DD8 PC = 0x8049976C
Frame 04: SP = 0x82BA0E28 PC = 0x8049841C
Frame 05: SP = 0x82BA0E60 PC = 0x804987A4
=======
Rack1R5#show stacks
Minimum process stacks:
Free/Size Name
5724/6000 HPI Logger
2588/3000 allegro libretto init
11396/12000 Router Init
8776/12000 Init
5440/6000 RADIUS INITCONFIG
5248/6000 BGP Open
5764/6000 BGP Accepter
Interrupt level stacks:
Level Called Unused/Size Name
1 48873 8520/9000 Network interfaces
2 0 9000/9000 Timebase Reference Interrupt
3 0 9000/9000 PA Management Int Handler
6 2717 8884/9000 16552 Con/Aux Interrupt
7 3373577 8920/9000 MPC860 TIMER INTERRUPT
System was restarted by bus error at PC 0x8002BD70, address 0x8002BD70
C2600 Software (C2600-J1S3-M), Version 12.2(15)T16, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Compiled Tue 19-Apr-05 12:23 by ssearch (current version)
Image text-base: 0x80008098, data-base: 0x81960AA0
Stack trace from system failure:
FP: 0x82BA0D48, RA: 0x8002BD00
FP: 0x82BA0D90, RA: 0x8002C35C
FP: 0x82BA0DA8, RA: 0x8033950C
FP: 0x82BA0DD8, RA: 0x8049976C
FP: 0x82BA0E28, RA: 0x8049841C
FP: 0x82BA0E60, RA: 0x804987A4
FP: 0x82BA0E90, RA: 0x804987D0
FP: 0x82BA0EA0, RA: 0x8073C658
***************************************************
******* Information of Last System Crash **********
***************************************************
The last crashinfo failed to be written.
Please verify the exception crashinfo configuration
the filesytem devices, and the free space on the
filesystem devices.
Using crashinfo_FAILED.
%Error opening crashinfo_FAILED (No such file or directory)
Monty escribis:
> Unless this box has not adsl card on it, it might cause by hardward or
> software problem. Especially the interrupt type from the post is
> different from the the bug below. show context, show stack and show
> tech might help cisco finding the root cause.
>
> Monty
> ----- Original Message ----- From: "I will Be a CCIE"
> <1willbeaccie@gmail.com>
> To: "Victor Cappuccio" <cvictor@protokolgroup.com>
> Cc: "CCIE LAB" <ccielab@groupstudy.com>
> Sent: Sunday, March 26, 2006 12:39 AM
> Subject: Re: Unexpected exception
>
>
>>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/prod_release_note0918
6
>>
>> a00801677be.html
>>
>>
>> CSCea64751
>>
>> Symptoms: A Cisco 2600 series may unexpectedly reload, or report
>> "badshare"
>> tracebacks, or do both. When the router reloads, the router generates
>> messages similar to the following:
>>
>> Unexpected exception to CPUvector 1200, PC = 818C8B80
>>
>> -Traceback= 818C8B80 818C9454 818C9848 818CD814 818CA814 818C7A28
>> 818BC7B4
>> 801E64B8 801E5D30 801D9A44 804F8CBC 8047FD74 804EB824 804EB824 8047FE34
>> 804EBCC0
>>
>> When "badshare" tracebacks occur, the router generates messages
>> similar to
>> the following:
>>
>> %SYS-2-BADSHARE: Bad refcount in pak_enqueue, ptr=8316E0F8, count=0
>>
>> -Traceback= 80406718 80407C38 818CC900 8026A9A0 80271EC4 8002258C
>> 804FB374
>> 804F8C84 8047FD74 804EB824 804EB824 8047FE34 80651388
>>
>> %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=8316E0F8, count=0
>>
>> -Traceback= 80403848 80407E68 818CC900 8026A9A0 80271EC4 8002258C
>> 804FB374
>> 804F8C84 8047FD74 804EB824 804EB824 8047FE34 80651388
>>
>> %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=8316E0F8, count=0
>>
>> Conditions: These symptoms are observed when the following two
>> conditions
>> occur:
>>
>> The Cisco 2600 series is configured with an asymmetric digital
>> subscriber
>> line (ADSL) or symmetric high-bit rate digital subscriber line
>> (SHDSL) WAN
>> interface card (WIC) that is installed in an onboard slot such as
>> slot 0/0
>> or slot 0/1.
>>
>> The upstream traffic rate exceeds the line rate, and this traffic is
>> routed
>> through the ADSL or SHDSL WIC. (The line rate is the maximum speed
>> allowed
>> by the digital subscriber line access multiplexer [DSLAM]).
>>
>> Workaround: Do not use onboard slots.
>>
>> Alternate workaround: Ensure that the router traffic rate is below
>> the line
>> rate.
>>
>>
>>
>> On 3/25/06, Victor Cappuccio <cvictor@protokolgroup.com> wrote:
>>>
>>> Hello All, I have seen many routers with an Unexpected Exception, like
>>> this one...
>>>
>>> Unexpected exception to CPUvector 200, PC = 8002BD70
>>> -Traceback= 8002BD70 8002C35C 8033950C 8049976C 8049841C 804987A4
>>> 804987D0 8073C658 803AC474
>>> Free space check for flash:crashinfo_19930301-030756 failed (68/13152)
>>>
>>> Is there something I can do (before opening a SR on the TAC) to know
>>> what is really happening??
>>> Thanks
>>> Victor.
>>>
>>> Rack1R5#show flash:
>>>
>>> System flash directory:
>>> File Length Name/status
>>> 1 15188900 c2600-j1s3-mz.122-15.T16.bin
>>> 2 335016 crashinfo_19930302-083749 [deleted]
>>> 3 305916 crashinfo_19930301-004752 [deleted]
>>> 4 352060 crashinfo_19930302-021157 [deleted]
>>> 5 57903 crashinfo_19930301-121819 [deleted]
>>> 6 12679 crashinfo_19930301-083337 [deleted]
>>> [16252860 bytes used, 68 available, 16252928 total]
>>> 16384K bytes of processor board System flash (Read/Write)
>>>
>>> Rack1R5#more flash:crashinfo_19930301-083337
>>> %Error opening flash:crashinfo_19930301-083337 (No such file or
>>> directory
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:40 GMT-3