osmo-sgsn crash report

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/.

Holger Hans Peter Freyther holger at freyther.de
Mon Sep 15 16:19:44 UTC 2014


On Mon, Sep 15, 2014 at 04:13:28PM +0000, admin at manateeshome.com wrote:

Hi!



> osmo-sgsn:
> 
> <000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=52
> <000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=52
> <000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171
> <000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171
> <0010> gprs_ns.c:545 NSEI=101 Tns-alive expired more then 10 times, blocking NS-VC
> <000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171
> <0010> gprs_ns.c:624 All NS-VCs for NSEI 101 are either dead or blocked!
> 
> Program received signal SIGABRT, Aborted.
> 0x00007ffff69b3445 in raise () from /lib/x86_64-linux-gnu/libc.so.6


it is a known crash with a double free in the defragmentation code (not
freeing will most likely lead to a leak). Are you willing to sponsor
the necessary code-review to make that issue go away?



> Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=31357:WARN:BH_TRX_ROUTER_TR:rm_s_data_queue_entry.c#195:Pool 2 nearly full
> Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=31663:WARN:BH_TRX_ROUTER_TR:igki_sig.c#741:Pool 2 nearly full


GPRS with the nanoBTS is not very stable. They have known memory
leaks in all versions of their firmware.

holger




More information about the OpenBSC mailing list