Bug #6179
closedASSERT in st_wait_release
0%
Description
osmo-pcu from the recent release:
Here's a backtrace (from sysmobts with osmo-pcu-dbg and libosmocore-dbg symbols installed)
Assert failed 0 ../../git/src/tbf_dl_fsm.c:309
backtrace() returned 0 addresses
Program received signal SIGABRT, Aborted.
0x432dcf74 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x432dcf74 in raise () from /lib/libc.so.6
#1 0x432de358 in abort () from /lib/libc.so.6
#2 0xb6eb38d4 in osmo_panic_default (args=..., fmt=0x0)
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:45
#3 osmo_panic (fmt=0x66fd4 "Assert failed %s %s:%d\n")
at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/panic.c:80
#4 0x00040f5c in st_wait_release (fi=<optimized out>, event=<optimized out>, data=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf_dl_fsm.c:309
#5 0xb6ea7824 in _osmo_fsm_inst_dispatch (fi=0x15e420, event=0, event@entry=3, data=data@entry=0x0, file=0x70098 "../../git/src/tbf.cpp",
line=line@entry=540) at /usr/src/debug/libosmocore/1.9.0+gitrAUTOINC+aca2c724ae-r2.18.0/git/src/core/fsm.c:875
#6 0x000356cc in gprs_rlcmac_tbf::poll_timeout (this=0x162920, pdch=0x154e64, poll_fn=223816, reason=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf.cpp:540
#7 0x0003585c in tbf_poll_timeout (tbf=<optimized out>, pdch=<optimized out>, poll_fn=<optimized out>, reason=<optimized out>)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/tbf.cpp:828
#8 0x0004cdf8 in pdch_ulc_expire_fn (ulc=0x1549d0, fn=223816, fn@entry=1395928)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/pdch_ul_controller.c:331
#9 0x00026a70 in pcu_rx_data_ind_pdtch (bts=bts@entry=0x154cd8, pdch=0x154e64, data=0x0, len=<optimized out>, fn=223816, meas=0xbefffb80,
meas@entry=0xbefffb78) at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/pcu_l1_if.cpp:396
#10 0x00015d70 in handle_ph_data_ind (fl1h=0x15de28, fl1h=0x15de28, l1p_msg=0x202ef8, data_ind=0x202fc0)
at /usr/src/debug/osmo-pcu/1.3.0+gitAUTOINC+3ef173b980-r0.18/git/src/osmo-bts-sysmo/sysmo_l1_if.c:220
It's always happening at line 540 in tbf.cpp:
osmo_fsm_inst_dispatch(this->state_fi, TBF_EV_MAX_N3105, NULL);
Logs are messy, there's a lot going on.
Maybe attached log (at INFO) helps.
Files
Updated by pespin 8 months ago
- Status changed from New to In Progress
I submitted this patch to gerrit which should fix it:
https://gerrit.osmocom.org/c/osmo-pcu/+/34425 tbf_dl_fsm: Fix assert hit due to EV_MAX_N3105 received in ST_RELEASING
Updated by keith 8 months ago
pespin wrote in #note-1:
I submitted this patch to gerrit which should fix it:
Indeed, although being able to run it now without the ASSERT shows me that no phones are getting any data service. Lot's of possibilities there.. but that's another story/ticket..
For now I went back to the previous tagged version (and same with osmo-bts due to the PCU_IF bump)
Updated by pespin 8 months ago
- Assignee changed from pespin to keith
keith wrote in #note-2:
pespin wrote in #note-1:
I submitted this patch to gerrit which should fix it:
Indeed, although being able to run it now without the ASSERT shows me that no phones are getting any data service. Lot's of possibilities there.. but that's another story/ticket..
Hi keith , I just tested my sysmobts with 201705-nightly which contains merged https://gerrit.osmocom.org/c/osmo-pcu/+/34425 (osmo-pcu 09dc6b21e2332e65d1fec2c9ceeb085703d2928a) and GPRS is working just fine.
Feel free to provide more feedback on what is not working for you.
