OpenBSC March 2017

openbsc@lists.osmocom.org

22 participants
48 discussions

by Neels Hofmeyr

It seems that we won't be merging vlr_2G or vlr_3G into openbsc.git's master, at least not soon. Instead we're likely to move to a new git repository altogether to mark the changed setup. We could switch 'Osmocom' over to vlr_3G and assume that it includes the others, but that's not accurate at all. The VLR stuff cuts away half the code from openbsc.git's master and 3G the other half. well, almost :) So I thought we could repurpose two of the unused coverity scan projects we have for the vlr_2G and vlr_3G branches. Or maybe one for vlr_3G would be enough. It seems we can't change the name of a coverity project. Maybe we can just use the OpenBSC one for vlr_3G without changing the name? We could possibly also include a separate build within the tar sent to the Osmocom job, I can also check that out. Or I can try and register a brand new one. Any preferences? ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte

8 years, 3 months

OsmoTRX runtime CPU optimization detection

by Harald Welte

FYI, Philipp has been working on some patches to do the OsmoTRX cpu instruction set extension detection at runtime rather than compile-time. See "Bug #1869: osmo-trx binary cannot be moved to similar CPU" https://osmocom.org/issues/1869#change-3394 As not everyone is following each redmine ticket or gerrit patch: I would like the OsmoTRX folks (Tom, Alexander, ...) to have a look at this. For convenience, the latest update to the ticket and the associated links to the gerrit patches below: --- The matching implementation is now selected dynamically during runtime. In order to be sure that the convolution part did not break, I wrote a small test program to compute some testvectors. I compared the results before and after my changes. They match up. I made only minimal changes to the conversion code, so I skipped testing that as well. The SSE relevant sources are compiled with $(SIMD_FLAGS) now. The sources only contain the SSE implementation and the decision logic to defer to the correct implementation during runtime. That should run fine on non SSE3 / SSE4.1 CPUs, since the decision logic is not vectorize-able. However, we can divide this up further as discussed. https://gerrit.osmocom.org/2098 buildenv: Turn off native architecture builds https://gerrit.osmocom.org/2099 cosmetic: Make parameter lists uniform https://gerrit.osmocom.org/2100 ssedetect: Add runtime CPU detection https://gerrit.osmocom.org/2101 cosmetic: Add info about SSE support https://gerrit.osmocom.org/2102 buildenv: Make build CPU invariant https://gerrit.osmocom.org/2103 cosmetic: remove code duplication https://gerrit.osmocom.org/2104 Add test program to verify convolution implementation --- -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

8 years, 3 months

Re: [MERGED] openbsc[master]: gprs_sgsn.c: initialize ptmsi with 0xdeadbeef

by Neels Hofmeyr

> - uint32_t ptmsi; > + uint32_t ptmsi = 0xdeadbeef; GSM_RESERVED_TMSI would make more sense here I guess (the "invalid TMSI" value). ~N

8 years, 3 months

Re: Build failure of network:osmocom:nightly/libosmocore in xUbuntu_16.10/i586

by Neels Hofmeyr

should be fixed by https://gerrit.osmocom.org/2089 On Wed, Mar 15, 2017 at 07:52:33PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… > > Package network:osmocom:nightly/libosmocore failed to build in xUbuntu_16.10/i586 > > Check out the package for editing: > osc checkout network:osmocom:nightly libosmocore > > Last lines of build log: > [ 143s] RAND: 6a61050765caa32c90371370e5d6dc2d > [ 143s] -AUTN: afb993e4f4b8000069cdeebb4a4b5b58 > [ 144s] +AUTN: 504693e4f4b80000e3963072c50f0b91 > [ 144s] IK: c348c2fe2f3e1fb37a7ae1638163bd98 > [ 144s] CK: e740c156278705a14e1a99ba6d31334f > [ 144s] RES: 7c04e86a67967fcd > [ 144s] SRES: 1b9297a7 > [ 144s] Kc: 10687b71e4eb94c5 > [ 144s] -SQN: 281474976710655 > [ 144s] +SQN: 4294967295 > [ 144s] > [ 144s] > [ 144s] > osmo-auc-gen -3 -a milenage -r 39fa2f4e3d523d8619a73b4f65c3e14d -k EB215756028D60E3275E613320AEC880 -o FB2A3D1B360F599ABAB99DB8669F8308 -A 979498b1f72d3e28c59fa2e72f9c > [ 144s] 40. testsuite.at:253: 40. osmo-auc-gen (testsuite.at:253): FAILED (testsuite.at:257) > [ 144s] debian/rules:26: recipe for target 'override_dh_auto_test' failed > [ 144s] make[1]: *** [override_dh_auto_test] Error 1 > [ 144s] make[1]: Leaving directory '/usr/src/packages/BUILD' > [ 144s] debian/rules:15: recipe for target 'build' failed > [ 144s] make: *** [build] Error 2 > [ 144s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 > [ 144s] > [ 144s] build85 failed "build libosmocore_0.9.6.20170315.dsc" at Wed Mar 15 19:52:15 UTC 2017. > [ 144s] > [ 144s] ### VM INTERACTION START ### > [ 146s] [ 136.282415] reboot: Power down > [ 147s] ### VM INTERACTION END ### > [ 147s] > [ 147s] build85 failed "build libosmocore_0.9.6.20170315.dsc" at Wed Mar 15 19:52:19 UTC 2017. > [ 147s] > > -- > Configure notifications at https://build.opensuse.org/user/notifications > openSUSE Build Service (https://build.opensuse.org/)

8 years, 3 months

NITB: high cpu usage and "crossed" messages when SMS table grows

by Keith

Hi all, I temporarily disabled a cron job we run at rhizomatica that purges the hlr SMS table of sent messages every day. After a few days I noticed slightly sluggish behaviour in the VTY, and sure enough, the nitb was consuming 100% cpu, not always, but presumably whenever it does a queue run. I also just heard that in the last few days, we got a number of reports from users, some confirmed by photos of the phones, about messages being delivered to the wrong destination. Apologies if this has been touched on before. I am not finding where I can directly search this list archives. Anyway, it might not be so bad to bring it up, as the cron job purging via cron job calling sqlite3 is not ideal, and anyway.. this crossed messages shouldn't happen, right? I imagine we'd like to track this one down. Keith.

8 years, 3 months

osmo-bts-trx channel activation

by Max

Hi. This has been asked last year but to no avail, let's try again. How logical channels are (de)activated in osmo-bts-trx? For example in all the other models there's sapi_deactivate_cb() callback but osmo-bts-trx doesn't seem to be using sapi_cmd at all. To put this into perspective - while working on https://projects.osmocom.org/issues/1575 I got to activate/deactivate lchans when SI3 is received. This already works for sysmobts but I'd like to do the same for osmo-bts-trx as well. Is there any documentation somewhere describing how it works there? Or maybe someone more familiar with the code could help to shed the light on it? -- Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

8 years, 3 months

autoconf and .deb question

by Max

Hi. There's strange thing about the way autoconf and debian/rules interact for OpenBSC: - in openbsc/include/openbsc/Makefile.am gsm_data_shared.h and common_cs.h are in noinst_HEADERS - in debian/openbsc-dev.install they are marked for installation And this actually works! If you run "dpkg-buildpackage -uc -us -tc" you'll get openbsc-dev*.deb with those headers properly installed. It's nice but feels a bit too much like magic. Any ideas how dh_install (or smth else?) manages to work around it? Should we be worried that it might break some time in future? Should we move those headers away from noinst_* section? -- Max Suraev <msuraev(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

8 years, 3 months

IMSI: Inf ?

by Keith

This is a bit vague again... I have found across our sites several entries with a value of Inf for IMSI on a create-on-demand subscriber: For example: sqlite> select * from Subscriber where id=284054; 284054|2017-03-08 21:19:40|2017-03-08 21:19:40|Inf||20649|0||0| I also have some Inf values for IMEI in Equipment: sqlite> select id,created,imei from Equipment where id = 95108; 95108|2014-03-13 03:18:06|Inf Not a big deal for operations, just thought I'd mention it as I noticed while restoring backups, (sqlite3 doesn't like to reimport the Inf value it writes itself with .dump)

8 years, 3 months

BS-11 Serial Interface

by Alexander Huemer

Hi, I have a Siemens BS-11 with the factory cable for the LMT that has a DSUB-9 plug on the non-BTS end. When I connect a USB<-->RS232 adapter and run either $ cu -l /dev/ttyUSB or bs11_config -p /dev/ttyUSB0 I do not get any output when I switch on the BTS. I tried with nullmodem adapter and without just to be sure since I often mix up the pinouts. I was not able to measure any voltage on any of the DSUB-9 pins when the BTS is powered up, but believe that on either RX or TX there should be the voltage level of the serial line since RS232 is active low. Has somebody seen this behavior? -Alex

8 years, 3 months

FYI: Build failure of network:osmocom:nightly/osmo-pcu in xUbuntu_16.10/x86_64

by Neels Hofmeyr

fyi, we're still getting daily failures by the opensuse builds, which should be fixed once https://gerrit.osmocom.org/2007 is merged. ~N On Sat, Mar 11, 2017 at 07:57:26PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… > > Package network:osmocom:nightly/osmo-pcu failed to build in xUbuntu_16.10/x86_64 > > Check out the package for editing: > osc checkout network:osmocom:nightly osmo-pcu > > Last lines of build log: > [ 111s] from bts.cpp:21: > [ 111s] /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128) > [ 111s] abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; } > [ 111s] ^~~ > [ 111s] /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int std::abs(long long int) > [ 111s] abs(long long __x) { return __builtin_llabs (__x); } > [ 111s] ^~~ > [ 111s] /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int) > [ 111s] abs(long __i) { return __builtin_labs(__i); } > [ 111s] ^~~ > [ 111s] Makefile:778: recipe for target 'bts.lo' failed > [ 111s] make[2]: *** [bts.lo] Error 1 > [ 111s] make[2]: Leaving directory '/usr/src/packages/BUILD/src' > [ 111s] Makefile:403: recipe for target 'all-recursive' failed > [ 111s] make[1]: *** [all-recursive] Error 1 > [ 111s] make[1]: Leaving directory '/usr/src/packages/BUILD' > [ 111s] dh_auto_build: make -j1 returned exit code 2 > [ 111s] debian/rules:12: recipe for target 'build' failed > [ 111s] make: *** [build] Error 2 > [ 111s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 > [ 111s] > [ 111s] lamb16 failed "build osmo-pcu_0.3.20170311.dsc" at Sat Mar 11 19:57:22 UTC 2017. > [ 111s] > [ 111s] ### VM INTERACTION START ### > [ 115s] [ 102.127065] reboot: Power down > [ 115s] ### VM INTERACTION END ### > [ 115s] > [ 115s] lamb16 failed "build osmo-pcu_0.3.20170311.dsc" at Sat Mar 11 19:57:26 UTC 2017. > [ 115s] > > -- > Configure notifications at https://build.opensuse.org/user/notifications > openSUSE Build Service (https://build.opensuse.org/)

8 years, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2017