Bug #2794

msc crashing 34c3

Added by lynxis 23 days ago. Updated 14 days ago.

Target version:
Start date:
Due date:
% Done:




(gdb) bt
#0  0x00007f0293ce7c20 in _osmo_fsm_inst_dispatch (fi=0x5636065c63a0, event=event@entry=3, data=0x5636065c62a0, file=file@entry=0x563604b7ebcc "msc_mgcp.c", line=line@entry=1068) at fsm.c:433
#1  0x0000563604b63008 in msc_mgcp_call_release (trans=trans@entry=0x5636065c5de0) at msc_mgcp.c:1068
#2  0x0000563604b59491 in _gsm48_cc_trans_free (trans=0x5636065c5de0) at gsm_04_08.c:1338
#3  0x0000563604b65fc5 in trans_free (trans=0x5636065c5de0) at transaction.c:124
#4  0x0000563604b55cae in gsm48_cc_rx_release_compl (trans=0x5636065c5de0, msg=<optimized out>) at gsm_04_08.c:2223
#5  0x0000563604b5a514 in gsm0408_rcv_cc (msg=0x5636066bcad0, conn=0x5636065c3bf0) at gsm_04_08.c:3186
#6  gsm0408_dispatch (conn=conn@entry=0x5636065c3bf0, msg=msg@entry=0x5636066bcad0) at gsm_04_08.c:3296
#7  0x0000563604b6708d in msc_dtap (conn=0x5636065c3bf0, link_id=<optimized out>, msg=0x5636066bcad0) at osmo_msc.c:108
#8  0x0000563604b68490 in gsm0408_rcvmsg_iucs (network=0x56360558f200, msg=0x5636066bcad0, lac=0x0) at iucs.c:181
#9  0x00007f0292ae6811 in ranap_handle_co_dt (ies=0x7ffdcc137a88, ctx=0x5636065c3b50) at iu_client.c:408
#10 cn_ranap_handle_co (ctx=0x5636065c3b50, message=0x7ffdcc137a80) at iu_client.c:542
#11 0x00007f0292ae4043 in ranap_cn_rx_co (cb=cb@entry=0x7f0292ae6310 <cn_ranap_handle_co>, ctx=0x5636065c3b50, data=<optimized out>, len=<optimized out>) at ranap_common_cn.c:307
#12 0x00007f0292ae5b2c in sccp_sap_up (oph=0x5636066bc428, _scu=0x5636056343c0) at iu_client.c:795
#13 0x00007f0293ce7d8d in _osmo_fsm_inst_dispatch (fi=0x5636065bf0b0, event=11, data=data@entry=0x5636066bc000, file=file@entry=0x7f02931d635d "sccp_scoc.c", line=line@entry=1581) at fsm.c:450
#14 0x00007f02931c6a1c in sccp_scoc_rx_from_scrc (inst=inst@entry=0x563605638a00, xua=xua@entry=0x5636066bc000) at sccp_scoc.c:1581
#15 0x00007f02931c4670 in scrc_rx_mtp_xfer_ind_xua (inst=inst@entry=0x563605638a00, xua=0x5636066bc000) at sccp_scrc.c:449
#16 0x00007f02931c7545 in mtp_user_prim_cb (oph=0x5636066b5d98, ctx=0x563605638a00) at sccp_user.c:176
#17 0x00007f02931bf402 in m3ua_rx_xfer (xua=0x5636066a2190, asp=0x5636056380c0) at m3ua.c:586
#18 m3ua_rx_msg (asp=asp@entry=0x5636056380c0, msg=msg@entry=0x5636066a5f50) at m3ua.c:738
#19 0x00007f02931ca51b in xua_cli_read_cb (conn=<optimized out>) at osmo_ss7.c:1590
#20 0x00007f0291abd46b in osmo_stream_cli_read (cli=0x5636056384c0) at stream.c:192
#21 osmo_stream_cli_fd_cb (ofd=<optimized out>, what=1) at stream.c:276
#22 0x00007f0293ce495e in osmo_fd_disp_fds (_eset=0x7ffdcc138240, _wset=0x7ffdcc1381c0, _rset=0x7ffdcc138140) at select.c:216
#23 osmo_select_main (polling=<optimized out>) at select.c:256
#24 0x0000563604b4e1fc in main (argc=5, argv=<optimized out>) at msc_main.c:552


#1 Updated by laforge 18 days ago

  • Assignee set to lynxis
  • Priority changed from Normal to Urgent

#2 Updated by neels 14 days ago

This is obviously related to the new MGCP FSM

We observed crashes both with GERAN and UTRAN. Unfortunately I was not able to obtain detailed logging leading up to the crash.

The crash didn't happen continuously, so it appears to be related to a call release situation that's not too common. Maybe the user hanging up right away? Maybe some radio failure?

If I were spending time on this, I would probably add voice call tests to the msc_vlr_tests suite in osmo-msc, could also be a candidate for ttcn3 tests... With tests like these I uncovered various tear down / free problems in the subscriber connection and VLR FSMs. It's not trivial to do proper cleanup in all situations.

Also available in: Atom PDF