Howto:Get the trap trace on unexpected restart (reboot) caused by a crash of the system

From innovaphone-wiki

Revision as of 12:24, 11 July 2018 by Slu (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Contents

Applies To

This information applies to:

  • All innovaphone gateways and phones with IP interface

Problem Description

In a very rare cases software errors could cause an unexpected reboot of an innovaphone device. We call this situation a trap and the crash dump information stored on the device in this case a trap trace.

The devices events log will show such restart:

Error  0x000b0001  Major CMD0 Unexpected Restart WATCHDOG (2) of 121022

To be able to investigate the problem our developer rely on the information provided in the trap trace. Therefore it is very important to deliver this trace to innovaphone support if such unexpected reboot happens.

The trap trace can be downloaded via the web interface of the innovaphone device under Maintenance -> Diagnostics -> Tracing -> trace(buffer) (do not use trace(continuous)!).

IMPORTANT: The trace buffer can be downloaded only one time after reboot.
           The download of the trap trace will cause clearance of the trace buffer and reinitializes the tracing activity.


The IPVA has a slightly different way to obtain the crash dump. Please refer to the related wiki article Reference12r1:Concept Innovaphone Virtual Appliance#Troubleshooting.

In case an unexpected restart happens, download the trap trace from the device, store it in a TXT file and deliver it to the innovaphone support.

Make sure the trace files contains the trap information. In contrast to a normal text trace, a trap trace contains stack and other dump information at the end of the trace:

 12r3 sr45 IP123[12.3456], Bootcode[12345], Hardware[123] 
 IP123-12-34-56
 Uptime 0d 0h 1m 23s                                                                                                                                                                                          
 
 ...
 
 0:0498:966:2 - AC-DSP0: headset_detach - already detached
 0:0498:966:2 - AC-DSP0: update_dsp 4->4 0->0 0->0 1->1 0
 0:0498:972:6 - PHONE_CALL.0 -> RING_CH.0 : CHANNEL_DISCONNECT
 0:0498:972:7 - PHONE_DSP.0 -> AC_CH.0 : CHANNEL_UNPAUSE
 0:0498:972:7 - phone_app: call_update 0001 SEND_CONNECT
 0:0498:972:7 - PHONE_CALL.0 -> VOIP_CALL.2 : SIG_CONN faststart=0 channel=-1 cmd=SELECT cn=
 0:0498:973:2 - VOIP_CALL.2 -> H323_CALL.0 : event type = 0
 0:0498:973:6 - PCAP NO-DATA
 0:0498:974:0 - PCAP NO-DATA
 0:0498:974:1 - PHONE_APP.0 -> PHONE_APP.0 : APP_DISP_FLUSH
 0:0498:974:5 - PCAP NO-DATA
 0:0498:975:2 - PCAP NO-DATA
 0:0498:975:3 - PCAP NO-DATA
 0:0498:981:3 - MEM-DELETE: obj at 0x87eb7388 inconsistent
 0:0498:981:3 - HEXDUMP
       87eb7288 - 88 73 eb 87  00 00 00 00  0d 00 00 00  c8 a3 79 80   .s............y.
       ...
       87eb7468 - c0 00 00 00  00 00 00 00  5b 00 00 00  64 00 00 00   ........[...d...
       87eb7478 - a8 00 00 00  b6 00 00 00  64 00 00 00  a8 00 00 00   ........d.......
 0:0498:981:3 - Assertion failed line 1205 in common/os/os.cpp, MEM-OBJ
 0:0498:981:3 - assert-ep 800047f4 called from 800af588
 0:0498:981:3 - BUILD 121147  Uptime 0d 0h 8m 18s  Local Time 01.06.17 14:57:20
 
 0:0498:981:3 -    0: -                       0 ticks=1146
 0:0498:981:3 -    1: -                       0 ticks=17300
 0:0498:981:3 -    2: -                       0 ticks=16828
 0:0498:981:3 -    3: -                       0 ticks=10994
 0:0498:981:4 -    4: ETHIF6                306 ticks=30252
 0:0498:981:4 -    5: -                       0 ticks=1335680
 0:0498:981:4 -    6: -                       0 ticks=0
 0:0498:981:4 -    7: -                       0 ticks=0
 0:0498:981:4 -    8: -                       0 ticks=104458
 0:0498:981:4 -    9: PHONE_APP            2100 ticks=605083
 0:0498:981:4 -   10: -                       0 ticks=0
 0:0498:981:4 -   11: -                       0 ticks=0
 0:0498:981:4 -   12: -                       0 ticks=0
 0:0498:981:4 -   13: -                       0 ticks=0
 
 0:0498:981:4 - stack(87eb72a8):
 0:0498:981:4 - HEXDUMP
       87eb72a0 - 00000000 8000487c 8047fec0 87eb7358   ....|H....G.Xs..
       87eb72b0 - 00000000 87eb7398 808c66a8 8079a23c   .....s...f..<.y.
       87eb72c0 - 87eb7388 800af588 00000000 00000001   .s..............
       87eb72d0 - 80f4b760 00000004 00000088 802a220c   `............"*.
 ...
       87eb8290 - 00000000 00000000 00000000 00000000   ................
 
 0:0498:982:6 - HALT
 end of trace
 
 reset-source=WATCHDOG(2) 
 
 BUILD: 121147
 
    0: -                0
    1: -                0
    2: -                0
    3: -                0
    4: ETHIF6           306
    5: -                0
    6: -                0
    7: -                0
    8: -                0
    9: PHONE_APP        2100
   10: -                0
   11: -                0
   12: -                0
   13: -                0
 
 XCPT: no exception context present
 
 ok

Reset-Sources

PWR-ON(0)
device was re-powered (no trap)
WATCHDOG(2)
device was restarted by the watchdog (trap)
COMMAND(3)
device was reset using the admin ui or update script (no trap)

Related Articles

Personal tools