01-07-2013 07:09 PM - edited 03-07-2019 10:57 AM
One of my blade switch 3120 running version 122-50.SE3 crashed and recorded the following erroe message:
System returned to ROM by bus error at PC 0x5B5EA78, address 0x0
Can someone help to find the root cause of the crash?
Many thanks
Solved! Go to Solution.
01-08-2013 08:27 AM
Hi,
From the "show stacks" it seems to be an error on accessing specific memory address 0x0:
Using flash:/crashinfo/crashinfo_1. Cisco IOS Software, CBS31X0 Software (CBS31X0-UNIVERSAL-M), Version 12.2(50)SE3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Wed 22-Jul-09 09:10 by prod_rel_team Instruction Access Exception (0x0400)!
Since 0x0 is a valid address in "main" region, the error likely to be a parity problem. The mostly meaningless stack trace corresponds with such root cause.
------------------ show region ------------------ Region Manager: Start End Size(b) Class Media Name 0x00000000 0x0FFFFFFF 268435456 Local R/W main
Parity errors are related to HW problems and with first occurrence it is recommended to monitor the blade.
At the same time, I suggest to check extended crashinfo for more symptoms.
------------------ show flash: ------------------ Directory of flash:/ 3 drwx 512 Jan 6 2013 06:59:18 +08:00 crashinfo_ext
Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.
01-07-2013 07:17 PM
12.2(50)SE3
I wouldn't be using this IOS version.
The "sh tech" didn't give me much information. If the blade crashed then there should be some crashinfo files/folder. Attached the latest 3.
01-08-2013 08:27 AM
Hi,
From the "show stacks" it seems to be an error on accessing specific memory address 0x0:
Using flash:/crashinfo/crashinfo_1. Cisco IOS Software, CBS31X0 Software (CBS31X0-UNIVERSAL-M), Version 12.2(50)SE3, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Wed 22-Jul-09 09:10 by prod_rel_team Instruction Access Exception (0x0400)!
Since 0x0 is a valid address in "main" region, the error likely to be a parity problem. The mostly meaningless stack trace corresponds with such root cause.
------------------ show region ------------------ Region Manager: Start End Size(b) Class Media Name 0x00000000 0x0FFFFFFF 268435456 Local R/W main
Parity errors are related to HW problems and with first occurrence it is recommended to monitor the blade.
At the same time, I suggest to check extended crashinfo for more symptoms.
------------------ show flash: ------------------ Directory of flash:/ 3 drwx 512 Jan 6 2013 06:59:18 +08:00 crashinfo_ext
Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide