08-29-2012 02:00 AM - edited 03-04-2019 05:24 PM
Teh following output is generated by sh context
System was restarted by bus error at PC 0x41FE4988, address 0x813B at 10:07:23 EEST Wed Aug 29 2012
2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(20)T1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Compiled Wed 24-Sep-08 14:37 by prod_rel_team
Image text-base: 0x400783C8, data-base: 0x43DC3FC0
Stack trace from system failure:
FP: 0x47D46830, RA: 0x41FE4988
FP: 0x47D46888, RA: 0x41FDFF34
FP: 0x47D468C0, RA: 0x41E1337C
FP: 0x47D46920, RA: 0x41E15CC4
FP: 0x47D46998, RA: 0x41E16650
Fault History Buffer:
2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(20)T1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Compiled Wed 24-Sep-08 14:37 by prod_rel_team
Signal = 10, Code = 0x46D40000, Uptime 1d16h
$0 : 00000000, AT : 000000BA, v0 : 00000007, v1 : 00000008
a0 : FFFFFFFF, a1 : 47545AD4, a2 : 4008DAC0, a3 : 00000000
t0 : 00000008, t1 : FFFFFFFF, t2 : 00000001, t3 : 00000815
t4 : 00000814, t5 : 00010000, t6 : FFFFFFFF, t7 : 00000002
s0 : 0000FFFF, s1 : 47545AD4, s2 : 4008DAC0, s3 : 00000814
s4 : 00000000, s5 : 46AF0000, s6 : 46980000, s7 : 3F201898
t8 : 46530000, t9 : 46D338F0, k0 : 3040A801, k1 : A000F000
gp : 46986C40, sp : 47D46830, s8 : 00000000, ra : 41FDFF34
EPC : 41FE4988, SREG : 3400FF03, Cause : 00000010
Error EPC : BFC00E8C, BadVaddr : 0000813B
CacheErr : 903FFFC0, DErrAddr0 : 07069DC8,
DErrAddr1 : 07EABCE0
DATA_START : 0x43DC3FC0
Is this a hardware or software problem?
08-29-2012 02:15 AM
Hi Milen,
This is the problem with IOS.
Upgrading the IOS will solve this problem.
here is the link of troubleshotting:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800cdd51.shtmlhttp://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800cdd51.shtml
Regards
Please rate if it helps.
08-29-2012 02:31 AM
This router has to be updated. 12.4.(20)T1 is really old, in that release T6 is the actual version (that's five rounds of Bugfixing).
If you don't need the features from 12.4.20, I would go for 12.4(15)T17. That release is running on many of my customers routers without problems.
--
Don't stop after you've improved your network! Improve the world by lending money to the working poor:
http://www.kiva.org/invitedby/karsteni
08-29-2012 02:58 AM
Signal = 10,
IOS failure or bug.
08-29-2012 07:13 AM
Hi Leo,
Only if the adress is out of the valid memory range. We need to check if the address 0x813B is in a list of valid addresses from "show region".
In case the address is valid - it is HW issue.
Kind Regards,
Ivan
08-29-2012 03:59 PM
Only if the adress is out of the valid memory range. We need to check if the address 0x813B is in a list of valid addresses from "show region".
C'mon, Ivan! Y'know I don't have the tools to do this ... Hmmmm ... will "test crash" replicate this perhaps?
LOL
08-29-2012 11:36 PM
For that one you need just to compare the address and start/end numbers :-)
Router#show region Region Manager: Start End Size(b) Class Media Name 0x00000000 0x007FFFFF 8388608 Local R/W main 0x00001000 0x0001922F 98864 IData R/W main:data 0x00019230 0x000666B3 316548 IBss R/W main:bss 0x000666B4 0x007FEFFF 7965004 Local R/W main:heap 0x007FF000 0x007FFFFF 4096 Local R/W main:flhlog 0x00800000 0x009FFFFF 2097152 Iomem R/W iomem 0x03000000 0x037FFFFF 8388608 Flash R/O flash 0x0304033C 0x037A7D3F 7764484 IText R/O flash:text
Btw, two "test crash" options for Bus Error speak about this HW kind of issues - parity in main or I/O memory:
Ciscozine#test crash
Type the number for the selected crash:
--------------------------------------
...
2 (crash router) Bus Error, due to parity error in Main memory
3 (crash router) Bus Error, due to parity error in I/O memory
...
Kind Regards,
Ivan Shirshin
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