cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8832
Views
2
Helpful
8
Replies

6509-E Last Reload Reason: bus error at PC

William Reed
Level 1
Level 1

Hello,

I am breaking in some old but new to me 6509-E with Sup 720 modules. Everything seems perfect expect the last reload reason. I have forced switchovers and hw-module reset both Supervisors and always one of them will come up with a 'last reload reason: bus error at PC 0x42818CFC, address 0x0'

Everything else seems great though. The switches do keep forwarding when I force a switchover so SSO is working. Also I ran intrusive diagnostics and everything passed.

Is this something to worry about? Here is a snippet

Router>en
Router#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISE_WAN-M), Version 12.2(33)SXJ10, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Fri 14-Aug-15 08:58 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)

 Router uptime is 10 hours, 55 minutes
Uptime for this control processor is 10 hours, 38 minutes
Time since Router switched to active is 22 minutes
System returned to ROM by Stateful Switchover at 04:44:23 UTC Thu Jan 7 2016 (SP by reload)
System image file is "disk0:s72033-adventerprise_wan-mz.122-33.SXJ10.bin"
Last reload reason: bus error at PC 0x42818CFC, address 0x0


cisco WS-C6509-E (R7000) processor (revision 1.4) with 458720K/65536K bytes of memory.
Processor board ID SMC1130001V
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 Virtual Ethernet interface
52 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102

Router#sh red
Router#sh redundancy
Redundant System Information :
------------------------------
       Available system uptime = 10 hours, 55 minutes
Switchovers system experienced = 2
              Standby failures = 0
        Last switchover reason = user forced

                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up

Current Processor Information :
-------------------------------
               Active Location = slot 6
        Current Software state = ACTIVE
       Uptime in current state = 22 minutes
                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISE_WAN-M), Version 12.2(33)SXJ10, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Fri 14-Aug-15 08:58 by prod_rel_team
                          BOOT = disk0:s72033-adventerprise_wan-mz.122-33.SXJ10.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102

Peer Processor Information :
----------------------------
              Standby Location = slot 5
        Current Software state = STANDBY HOT
       Uptime in current state = 15 minutes
                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISE_WAN-M), Version 12.2(33)SXJ10, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Fri 14-Aug-15 08:58 by prod_rel_team
                          BOOT = disk0:s72033-adventerprise_wan-mz.122-33.SXJ10.bin,12;
                   CONFIG_FILE =
                       BOOTLDR =
        Configuration register = 0x2102


Router#

8 Replies 8

Mark Malone
VIP Alumni
VIP Alumni

Could be a hardware issue bus errors on 65s are never good news , hopefully its just the software gone you could try another image.

Is there anything in the logs to indicate anything else

http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/7949-crashes-buserror-troubleshooting.html

things to check here whether its software or hardware that may have caused it 

http://routing-bits.com/2010/03/10/ts-cisco-6500-crash/

I went to 15.1 and the weird errors are gone.

Well I said that, now when on 15.1 code. I just did a 'reload' and the Standby RP says:

"Last reload reason: unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19"

The primary SP and RP as well as Standby SP say: "Last reload reason: reload"

Is this some bug I shouldn't be thinking into so hard? Or is something wrong?

As I said all diag pass and SSO is working just fine.

I would not put this switch in production unless you have a TAC ticket with Cisco and they confirm this is not a hardware and/or software issue.

HTH

Yeah I will open a case tomorrow.

This looks awfully familiar.

https://supportforums.cisco.com/document/17576/catalyst-6500-series-switches-supervisor-iii-runs-cisco-ios-resets-due-watchdog

Do you have a 6509-E you could login to and see what yours says?

I don't have 6500 to test with, but since the error start with "bus error"

you do want to open a ticket and have them look into it, because that error is not usually good. You don't want to see an unexpected reboot at 2:00am.

It no longer says bus error after the upgrade to 15.1 code. Read above.

Well I said that, now when on 15.1 code. I just did a 'reload' and the Standby RP says:

"Last reload reason: unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19"

The primary SP and RP as well as Standby SP say: "Last reload reason: reload" Those look normal.

Same issue posted 10 years ago. I am sure it is a bug.

https://supportforums.cisco.com/discussion/9782026/error-message-6509#comment-11054601

Review Cisco Networking products for a $25 gift card