f



System received a Bus Error exception

One of my Cisco 3640 routers keep crashing lately, giving the
following on the console--

-Traceback= 610561EC 610688F4 610484D4
*** System received a Bus Error exception ***
signal= 0xa, code= 0xc, context= 0x61c87ab0
PC = 0x6043542c, Cause = 0x420, Status Reg = 0x34018002

A 'show region' is below:

Region Manager:

      Start         End     Size(b)  Class  Media  Name
 0x03A00000  0x03FFFFFF     6291456  Iomem  R/W    iomem
 0x30000000  0x30FFFFFF    16777216  Flash  R/O    flash
 	0x60000000  0x639FFFFF    60817408  Local  R/W    main
 0x60008950  0x61155ABF    18141552  IText  R/O    main:text
 0x61156000  0x61AE71DF    10031584  IData  R/W    main:data
 0x61AE71E0  0x61D5151F     2532160  IBss   R/W    main:bss
 0x61D51520  0x639FFFFF    30075616  Local  R/W    main:heap
 0x80000000  0x839FFFFF    60817408  Local  R/W    main:(main_k0)
 0xA0000000  0xA39FFFFF    60817408  Local  R/W    main:(main_k1)


Can someone please confirm what may be the cause of the problem? Thanks

0
nlcny (1)
10/19/2007 3:58:46 PM
comp.dcom.sys.cisco 25310 articles. 0 followers. Post Follow

8 Replies
715 Views

Similar Articles

[PageSpeed] 37

as Peter has said it is ahardware fault of some sort

see Cisco doc "Troubleshooting Bus Error Crashes"

http://cco.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800cdd51.shtml

for some troubleshooting hints and procedures


If you have a SmartNet support contract for the unit, then open a case
with the Cisco TAC

0
Merv
10/19/2007 6:37:59 PM
Greetings...

On Fri, 19 Oct 2007 15:58:46 UTC,  nlcny@yahoo.com wrote:

> One of my Cisco 3640 routers keep crashing lately, giving the
> following on the console--
> 
> -Traceback= 610561EC 610688F4 610484D4
> *** System received a Bus Error exception ***
> signal= 0xa, code= 0xc, context= 0x61c87ab0
> PC = 0x6043542c, Cause = 0x420, Status Reg = 0x34018002
> 
> A 'show region' is below:
> 
> Region Manager:
> 
>       Start         End     Size(b)  Class  Media  Name
>  0x03A00000  0x03FFFFFF     6291456  Iomem  R/W    iomem
>  0x30000000  0x30FFFFFF    16777216  Flash  R/O    flash
>  	0x60000000  0x639FFFFF    60817408  Local  R/W    main
>  0x60008950  0x61155ABF    18141552  IText  R/O    main:text
>  0x61156000  0x61AE71DF    10031584  IData  R/W    main:data
>  0x61AE71E0  0x61D5151F     2532160  IBss   R/W    main:bss
>  0x61D51520  0x639FFFFF    30075616  Local  R/W    main:heap
>  0x80000000  0x839FFFFF    60817408  Local  R/W    main:(main_k0)
>  0xA0000000  0xA39FFFFF    60817408  Local  R/W    main:(main_k1)
> 
> 
> Can someone please confirm what may be the cause of the problem? Thanks

The key is 

	> *** System received a Bus Error exception ***

This is indicative of a Hardware failure. I have seen something 
similar with an old 4700 Router, it would crash at random intervals, 
anything between 4 hours to 4 weeks of operation, regardles of any 
obvious operation. Replacing the router cured the problem.

Cisco H/W failures are not always common, but they do happen......;-)

Cheers............pk.

-- 
Peter from Auckland.
0
Peter
10/19/2007 7:38:55 PM
Post output of show version and show stack


0
Merv
10/19/2007 8:34:34 PM
Also Cisco docs on troubleshooting bus errors also suggest trying to
upgrade IOS software in the event the issue is osftware rleated

0
Merv
10/20/2007 8:30:53 AM
On Oct 19, 4:34 pm, Merv <merv.hr...@rogers.com> wrote:
> Post output of show version and show stack

Here they here, thanks. I know the IOS is old but we don't have
support to get the upgrade and the router has been operating without
issues for over 2 years.

------------------ show version ------------------

Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-IS-M), Version 12.2(1), RELEASE SOFTWARE
(fc2)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Fri 27-Apr-01 03:19 by cmong
Image text-base: 0x60008950, data-base: 0x61156000

ROM: System Bootstrap, Version 11.1(20)AA2, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc1)

uptime is 13 hours, 40 minutes
System returned to ROM by bus error at PC 0x610561EC, address 0x1
System image file is "flash:c3640-is-mz.122-1.bin"

cisco 3640 (R4700) processor (revision 0x00) with 59392K/6144K bytes
of memory.
Processor board ID 26388688
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
1 FastEthernet/IEEE 802.3 interface(s)
1 ATM network interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102



------------------ show stacks ------------------


Minimum process stacks:
 Free/Size   Name
 5604/6000   DHCPD Receive
 8116/12000  Init
 5288/6000   RADIUS INITCONFIG
 8720/12000  Virtual Exec

Interrupt level stacks:
Level    Called Unused/Size  Name
  1    40679547   7964/9000  Network interfaces
  2       11608   8620/9000  DMA/Timer Interrupt
  3           0   9000/9000  PA Management Int Handler
  4          47   8616/9000  Console Uart
  5           0   9000/9000  External Interrupt
  7    12310505   8604/9000  NMI Interrupt Handler

System was restarted by bus error at PC 0x610561EC, address 0x1
3600 Software (C3640-IS-M), Version 12.2(1), RELEASE SOFTWARE (fc2)
Compiled Fri 27-Apr-01 03:19 by cmong (current version)
Image text-base: 0x60008950, data-base: 0x61156000


Stack trace from system failure:
FP: 0x61E41358, RA: 0x610561EC
FP: 0x61E413D0, RA: 0x610688F4
FP: 0x61E41408, RA: 0x610484D4


***************************************************
******* Information of Last System Crash **********
***************************************************

0
nlcny
10/22/2007 5:35:25 PM

System was restarted by bus error at PC 0x610561EC, address 0x1

the above message with an invalid memory address suggest that the
issue is potentially a software bug.

Not that you software is old but it is the first release of 12.2

are all of your 3640's running the same release ?

You really should get a minimal support contract ( 8 x 5 NBD ) so you
can upgrade the software

has anything changed in your environment lately in terms of volume or
type of traffic that is hitting this box ?

Any config changes ?

do you have an OC3 ATM interface in the 3640 ???

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

The failure was caused by a software defect.Note that this is a bus
error crash
and can also be hardware related.Please read Troubleshooting Bus Error
Crashes
for more details,especially if no bug from the list seems to match
your issue.

The stack trace decoded symbols are:
	rs8234_data_receive_complete
	rs8234_data_receive_complete
	rs8234_data_receive_complete
	atmoc3_rs8234_interrupt
	atmoc3_pm5346







0
Merv
10/22/2007 6:48:47 PM
On Oct 22, 2:48 pm, Merv <merv.hr...@rogers.com> wrote:
> System was restarted by bus error at PC 0x610561EC, address 0x1
>
> the above message with an invalid memory address suggest that the
> issue is potentially a software bug.
>
> Not that you software is old but it is the first release of 12.2
>
> are all of your 3640's running the same release ?
>
> You really should get a minimal support contract ( 8 x 5 NBD ) so you
> can upgrade the software
>
> has anything changed in your environment lately in terms of volume or
> type of traffic that is hitting this box ?
>
> Any config changes ?
>
> do you have an OC3 ATM interface in the 3640 ???
>
> =============================================
>
> The failure was caused by a software defect.Note that this is a bus
> error crash
> and can also be hardware related.Please read Troubleshooting Bus Error
> Crashes
> for more details,especially if no bug from the list seems to match
> your issue.
>
> The stack trace decoded symbols are:
>         rs8234_data_receive_complete
>         rs8234_data_receive_complete
>         rs8234_data_receive_complete
>         atmoc3_rs8234_interrupt
>         atmoc3_pm5346


Are you experiencing a lot of errors of the ATM interfce

post show interface for the ATM interface

then clear counters and monitor

how many ATM PVC's are configured on interface ?



0
Merv
10/22/2007 7:42:09 PM
Merv, thanks so much for your replies and insights. Much appreciate
it.

Yea, all our 3640's are running the same IOS release. The one that's
having issues does have an ATM interface that's connected via DS3 to a
disaster recovery site. The config hasn't been changed, nor has
traffic increased since it went live 2 years ago. I'll see if I can
get the IOS upgraded.

Thanks again.

The partial show int is below:

ATM0/0 is up, line protocol is up
  Hardware is RS8234 ATM DS3
  Internet address is x.x.x.x/30
  MTU 4470 bytes, sub MTU 4470, BW 45000 Kbit, DLY 190 usec,
     reliability 255/255, txload 3/255, rxload 2/255
  Encapsulation ATM, loopback not set
  Keepalive not supported
  Encapsulation(s): AAL5
  1024 maximum active VCs, 1 current VCCs
  VC idle disconnect time: 300 seconds
  Last input 00:00:22, output 00:00:00, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:
1041
  Queueing strategy: Per VC Queueing
  30 second input rate 362000 bits/sec, 148 packets/sec
  30 second output rate 699000 bits/sec, 148 packets/sec
     73141416 packets input, 4166298791 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     85323223 packets output, 265472058 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 output buffer failures, 0 output buffers swapped out


On Oct 22, 2:48 pm, Merv <merv.hr...@rogers.com> wrote:
> System was restarted by bus error at PC 0x610561EC, address 0x1
>
> the above message with an invalid memory address suggest that the
> issue is potentially a software bug.
>
> Not that you software is old but it is the first release of 12.2
>
> are all of your 3640's running the same release ?
>
> You really should get a minimal support contract ( 8 x 5 NBD ) so you
> can upgrade the software
>
> has anything changed in your environment lately in terms of volume or
> type of traffic that is hitting this box ?
>
> Any config changes ?
>
> do you have an OC3 ATM interface in the 3640 ???
>
> =============================================
>
> The failure was caused by a software defect.Note that this is a bus
> error crash
> and can also be hardware related.Please read Troubleshooting Bus Error
> Crashes
> for more details,especially if no bug from the list seems to match
> your issue.
>
> The stack trace decoded symbols are:
>         rs8234_data_receive_complete
>         rs8234_data_receive_complete
>         rs8234_data_receive_complete
>         atmoc3_rs8234_interrupt
>         atmoc3_pm5346


0
nlcny
10/24/2007 1:57:23 PM
Reply: