System returned to ROM by Bus error - VG224

campbellj1 · ‎10-20-2014

I'm currently running a VG224 on IOS 15.1(3).T3 using SIP which has 14 lines registered to an Asterisk server

It has just rebooted for no reason, when it came back up I get this:

System returned to ROM by bus error at PC 0x62806BE0, address 0x739C9220 at 16:34:32 BST Mon Oct 20 2014

Reading about I see that if the address is in the same range within show region then it's a hardware fault however I don't think it is

Region Manager:

      Start         End     Size(b) Class Media Name
0x07500000 0x07FFFFFF    11534336 Iomem R/W    iomem
0x60000000 0x674FFFFF   122683392 Local R/W    main
0x60016FD0 0x6292C5C7    43079160 IText R/O    main:text
0x6293C700 0x6394FC7F    16856448 IData R/W    main:data
0x6394FC80 0x63C76D5F     3305696 IBss   R/W    main:bss
0x63C76D60 0x674FFFFF    59282080 Local R/W    main:heap
0x80000000 0x874FFFFF   122683392 Local R/W    main:(main_k0)
0xA0000000 0xA74FFFFF   122683392 Local R/W    main:(main_k1)

Free Region Manager:

Start End Size(b) Class Media Name

Could it be a software bug? - Is there anything I can look for to pin point the cause?

Thanks

campbellj1 · ‎10-21-2014

I've grabbed the crashinfo file and see this at the time of the crash:

Oct 20 16:34:27.309 BST: flex_dsprm_vtsp_open - 2/6 ACTIVE CALL, CPU load 5sec = 8, 1 Min = 3

Oct 20 16:34:30.849 BST: ASSERTION FAILED : ../voip/ccvtsp/vtsp.c: vtsp_cdb_assert: 1562: unkn -Traceback= 0x620449F8z 0x62089D4Cz 0x62076490z 0x61655214z 0x61655B3Cz 0x62059968z 0x62059E80z 0x607CDA1Cz 0x607CDA00z

16:34:30 BST Mon Oct 20 2014: TLB (load or instruction fetch) exception, CPU signal 10, PC = 0x62806BE0

--------------------------------------------------------------------
Possible software fault. Upon reccurence, please collect
crashinfo, "show tech" and contact Cisco Technical Support.
--------------------------------------------------------------------

-Traceback= 0x627FBDC0z 0x61DD772Cz 0x620449F8z 0x62089D4Cz 0x62076490z 0x61655214z 0x61655B3Cz 0x62059968z 0x62059E80z 0x607CDA1Cz 0x607CDA00z
$0 : 00000000 00000000, AT : 00000000 63950000, v0 : FFFFFFFF 8E739244, v1 : 00000000 65294924
a0 : 00000000 739C9220, a1 : 00000000 739C9220, a2 : 00000000 00000000, a3 : 00000000 637B0000
t0 : 00000000 00000000, t1 : 00000000 00000003, t2 : 00000000 00000003, t3 : FFFFFFFF FFFF00FF
t4 : 00000000 608B79E0, t5 : 00000000 00000000, t6 : 00000000 00000000, t7 : 00000000 62AF0000
s0 : 00000000 6528F214, s1 : 00000000 00000003, s2 : 00000000 63C20000, s3 : 00000000 00000000
s4 : 00000000 5E60FD91, s5 : 00000000 0000012C, s6 : 00000000 00000001, s7 : 00000000 00000800
t8 : 00000000 00000000, t9 : 00000000 00000000, k0 : 00000000 3041E801, k1 : 00000000 00000008
gp : 00000000 63953AA0, sp : 00000000 65261808, s8 : 00000000 65BC97D4, ra : 00000000 61DE254C
EPC : 62806BE0, ErrorEPC : BFC00F2C, SREG : 3401FF03
MDLO : 00000000, MDHI : 00000006, BadVaddr : 739C9220
TEXT_START : 0x600136F0
DATA_START : 0x62938E20
Cause 00000008 (Code 0x2): TLB (load or instruction fetch) exception

16:34:30 BST Mon Oct 20 2014: TLB (load or instruction fetch) exception, CPU signal 10, PC = 0x62806BE0