If your Supervisor module has DRAM of 128MB, then in order to resolve this issue, upgrade the memory to 256MB or more. Upgrade the switch to the latest Cisco IOS Software release unaffected by the bug in order to resolve this issue. %PM_SCP-1-LCP_FW_ERR This message indicates that the firmware of the Composite Reset Reason = (0xa) Level 1 Watch Dog time out Level 2 Watch Dog time out Conditions: Occurs randomly after upgrade to this release. ndcbbnpendc0103#sh region Region Manager: Start End Size(b) Class Media Name 0x08000000 0x0BFFFFFF 67108864 Iomem R/W iomem 0x08B69D40 0x08C77813 1104596 Criti R/W iomem:Critical I/O 0x40000000 0x4BFFFFFF 201326592 Local R/W main 0x40101040 0x42D8FFFF
The bootflash was filled with old crash info, just did a squeeze and captured another and am moving it to me right now. Already a member? If you see an error message that is not in one of the common error messages, refer to: Message and Recovery Procedures - Catalyst 6500 Series Cisco IOS System Message I'm currently reviewing Cisco bug list for this problem to see if any could relate to my situation.
Do not confuse this with the program counter (PC) value above. do anyone got chance to dig in? Jump to content Sign In Create Account Sadikhov IT Forums View New Content Sadikhov.com Forums Members Calendar Blogs Chat More Sadikhov IT Certification forums → CERTIFICATION → CISCO Conditions: Nat is configured.
This is a software problem so there is no need to check with the show region command. All of the devices used in this document started with a cleared (default) configuration. no snmp-server Disable possible SNMP queries to this device from the Network Management Stations. Cisco Bus Error In the output, look for line that starts with System returned to ROM by .
The Software Advisor (registered customers only) gives you the minimum versions of Cisco IOS software needed for hardware. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are The hardware issueis most likely related to the corresponding component. I've been browsing through Bug Tool, and stumbled across something interesting: Oddly enough, CSCdk64476 describes identical symptoms for RSP with various 11.3 trains (mainline, T, and several oddballs).
If your switch shows such a software exception, issue the dir bootflash: command, which displays the MSFC (route processor [RP]) bootflash device, and the dir slavebootflash: command in order to check System Returned To Rom By Error - A System Error size req. 512 %SCHED-SP-STDBY-2-SEMNOTLOCKED: L2 bad entry (7fff/0) purge proc attempted to unlock an unlocked semaphore -Traceback= 4018A300 403F0400 403EDD7C 403F0A48 SP-STDBY: EARL Driver:lyra_purge_search:process_push_event_list failed %SYS-SP-STDBY-2-MALLOCFAIL: Memory allocation of 1400 bytes System returned to ROM by bus error at PC 0x6323F398, address 0xB0D0B39 Answered Question Peter von Nostrand Jan 27th, 2012 Hi, I have an 3845 router:Cisco IOS Software, 3800 Software (C3845-ADVIPSERVICESK9-M), Compiled Thu 11-Jul-02 22:09 by pwade Image text-base: 0x60008940, data-base: 0x61088000 ROM: System Bootstrap, Version 12.0(19990210:195103) [12.0XE 105], DEVELOPMENT SOFTWARE BOOTLDR: 7200 Software (C7200-BOOT-M), Version 12.0(2)XE2, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. Refer to Cisco bug ID CSCdx92013 (registered customers only) for more information. System Returned To Rom By Address Error At Pc Jul 8 14:18:27 CEST: %C6KPWR-SP-4-PSOK: power supply 2 turned on. Bus Error Linux For this the crashinfo is vital.
A bus error can be identified from the output of the show version command provided by the router if not power-cycled or manually reloaded. If the error message occurs once, then it is a transient issue. On the other hand, if the address falls within one of the ranges in the show region output, it means that the router accessed a valid memory address, but the hardware Monitor the MSFC2. Sp By Bus Error At Pc
I'm going out on an unauthoratitive limb, but PC 0x00000000 looks like an indirect function call attempt dereferenced a NULL pointer -- which shouldn't happen. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. For lower-end platforms such as the 3600 or 4000 router, reseat the network modules/network processors. Refer to Creating Core Dumps for more information and for the procedure to collect core dump from the device.
This show log command output shows an exception that was recorded at the time of the last reboot. Bus Error (load) Exception Verify that your configuration is supported in the Cisco IOS software and by the hardware. I feel your pain trying to upgrade the old code to Safe Harbor.
They swapped line cards into another 7206 and are still having the below errors. If you see an error message that is not in one of the common error messages, refer to Messages and Recovery Procedures - Catalyst 6500 Series System Message Guide, 8.4. This indicatesa hardware problem. How To Solve Bus Error In Linux These error messages might display: On the console: *** System received a Bus Error exception *** signal= 0xa, code= 0x10, context= 0x60ef02f0 PC = 0x601d22f8, Cause = 0x2420, Status Reg
If the DFC reset matches the crashinfo timestamp, issue the more dfc#module#-bootflash:filename command. The reboot time matches in the Last software reset field. The information in this document was created from the devices in a specific lab environment. Workaround: NoneD)Bug ID CSCee63116 Bus error @ ipnat_destroy_all_seq_delta_pairs.Symptoms: A Cisco router that runs Cisco IOS Release 12.3(5a) may reloadbecause of a bus error.
It is recommended that you re-seator firmly push the memory chips into the slot.For more information, see Troubleshooting Bus Error Crashes.2. End with CNTL/Z. 6500_IOS(config)#config-register 0x2102 6500_IOS(config)#end Issue the show bootvar command in order to verify the configuration register value at the next reload. 6500_IOS#show bootvar BOOT variable = slot0:c6sup12-ps-mz.121-13.E14,1 CONFIG_FILE variable If you are uncertain which bug ID may match or which Cisco IOS software version contains the fix for the problem, upgrading your Cisco IOS software to the latest version in Scott "Thrown to the Wolves" McNeilwww.epproach.net RE: Bus error crashes, need help interpreting... 2 burtsbees (Programmer) 4 Mar 08 20:50 The following hyperlinks are headings for the supported commands that yousubmitted.
Components Used The information in this document is based on the Cisco Catalyst 6000/6500 Series Switch Supervisors and MSFC modules. If you have restarted the switch after any suspected crash, issue the show version command. Recover Catalyst Switches that run CatOS from Booting Failures Refer to Recover the Catalyst 6500/6000 with Supervisor Engine I or II in order to recover Cisco Catalyst 6000/6500 with Supervisor If you have the output of a show context command from your Cisco device, you can use Cisco CLI Analyzer to display potential issues and fixes.
The "XJ" builds should be considered unstable, short-lived releases containing only recently introduced functionality that was later reintegrated into T trains and ultimately into stable IOS versions.Best regards,Peter See More 1 Refer to Processor Memory Parity Errors (PMPEs) for more information on parity errors. %MISTRAL-3-ERROR If your MSFC2 crashes and you have a crashinfo file in your bootflash device, issue These are some of the errors that you can see when this occurs: On the console, you see: *** System received a Cache Parity Exception *** signal= 0x14, code= 0xa405c428, The show region output is part of the show tech-support output from Cisco IOS Software Release 12.0(9).
Processor board ID 14534708 R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache 6 slot VXR midplane, Version 2.0 Last reset from power-on X.25 software, Version 3.0.0. Uptime is 7 days, 4 hours, 27 minutes sup2a> (enable)show log Network Management Processor (ACTIVE NMP) Log: Reset count: 1 Re-boot History: Jan 06 2003 10:35:56 0 Bootrom Checksum Failures: Please send it to [email protected] happened to crash dump info? The system is being reset. %Software-forced reload Faulty Fan Causes the Supervisor to Crash When a fan tray fails or a power supply is turned off, the Cisco Catalyst
Bus error crashes, need help interpreting... You can also issue the dir slavesup-bootflash: command in order to display the standby Supervisor Engine bootflash device. You should also consider upgrading the Cisco IOS software release to a version which has a fix for CSCdv68388 - "Change cache error exception handler to resume not crash" which has A system bus error occurred when the processor tried accessing something that doesn't exist.