Possible crash/malfunction in the handover code

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Ciaby ciaby at autistici.org
Mon Nov 10 17:08:50 UTC 2014


We have been experiencing problems with osmo-nitb since we enabled handover.
Sometimes osmo-nitb crashes, and our users have reported the fact that sometimes they end up listening to someone's else conversation.
This started to happen since we enabled handover.
This is the backtrace i got from a core dump of osmo-nitb:

(gdb) bt
#0  subscr_name (subscr=0x0) at gsm_subscriber_base.c:47
#1  0x00000000004079e3 in ho_gsm48_ho_compl (new_lchan=0x7fb1a80dd0b0) at handover_logic.c:259
#2  ho_logic_sig_cb (signal_data=<optimized out>, signal=<optimized out>, subsys=<optimized out>, handler_data=<optimized out>) at handover_logic.c:353
#3  ho_logic_sig_cb (subsys=<optimized out>, signal=<optimized out>, handler_data=<optimized out>, signal_data=<optimized out>) at handover_logic.c:335
#4  0x00007fb1a76dccec in osmo_signal_dispatch (subsys=4, signal=3, signal_data=0x7ffffe668090) at signal.c:105
#5  0x0000000000408d25 in handle_rr_ho_compl (msg=<optimized out>) at bsc_api.c:524
#6  dispatch_dtap (msg=0x2436980, link_id=<optimized out>, conn=0xc8e070) at bsc_api.c:583
#7  gsm0408_rcvmsg (msg=0x2436980, link_id=<optimized out>) at bsc_api.c:657
#8  0x000000000041fde1 in abis_rsl_rx_rll (msg=0x2436980) at abis_rsl.c:1682
#9  abis_rsl_rcvmsg (msg=0x2436980) at abis_rsl.c:2093
#10 0x00007fb1a74cce5a in handle_ts1_read (bfd=0x90d6b8) at input/ipaccess.c:469
#11 ipaccess_fd_cb (bfd=0x90d6b8, what=1) at input/ipaccess.c:603
#12 0x00007fb1a76dca11 in osmo_select_main (polling=0) at select.c:158
#13 0x0000000000406e34 in main (argc=<optimized out>, argv=0x7ffffe6684f8) at bsc_hack.c:354

Any clue about why this is happening?
Cheers

Ciaby



More information about the OpenBSC mailing list