<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><div style="font-family: Tahoma; font-size: 16px;" class="crea-font-wrapper"><br><br><div></div>On Tue, Sep 16, 2014 at 01:20 AM, Holger Hans Peter Freyther <holger@freyther.de> wrote:<blockquote>On Mon, Sep 15, 2014 at 04:13:28PM +0000, <a target="_blank" href="mailto:admin@manateeshome.com">admin@manateeshome.com</a> wrote:<br><br>Hi!<br><br><blockquote>osmo-sgsn:<br><br><000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=52<br><000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=52<br><000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171<br><000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171<br><0010> gprs_ns.c:545 NSEI=101 Tns-alive expired more then 10 times, blocking NS-VC<br><000f> sgsn_libgtp.c:432 GTP DATA IND from GGSN, length=1171<br><0010> gprs_ns.c:624 All NS-VCs for NSEI 101 are either dead or blocked!<br><br>Program received signal SIGABRT, Aborted.<br>0x00007ffff69b3445 in raise () from /lib/x86_64-linux-gnu/libc.so.6</blockquote><br><br>it is a known crash with a double free in the defragmentation code (not<br>freeing will most likely lead to a leak). Are you willing to sponsor<br>the necessary code-review to make that issue go away?<br></blockquote><span><br>I wish I could, but I am not accustomed to debugging code in linux.<br>I looked over the surrounding code for a bit but it was difficult for me to get down to it without knowing how those are supposed to work...<br><br></span><blockquote><br><blockquote>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<br>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</blockquote><br><br>GPRS with the nanoBTS is not very stable. They have known memory<br>leaks in all versions of their firmware.<br><br></blockquote><span>If thats the case, how are commercial operators coping with those crashes?<br></span>Worst I've ever seen is the BTS crashing in 10 minutes of operation with a single iPhone connected.<br>I don't think thats even close to production level?<br><br><br>Regards,<br>Pierre<br><blockquote></blockquote></div></body></html>