osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-bts.git branch master updated. 0.7.0-49-ge95ad79

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via e95ad79d6c236489069f769c6b9c3cfc1aca595a (commit) via 8c1d15764377eb6a11aa432661d5afe60c2e8a9c (commit) via 1f80e9815f3bb98ddfabe5aaa9e69c0a47b84269 (commit) via 9a57c7bed4c096ccff4f9fc78b7ef789eeb18360 (commit) from 63948b033d41982b5e986a9c8a15fcfcd364eb25 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=e95ad79d6c236489069f769c6b9c3cf… commit e95ad79d6c236489069f769c6b9c3cfc1aca595a Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Wed Jan 17 13:45:40 2018 +0100 bts-trx: Detect duplicated responses for retransmitted commands It was detected that under some conditions, osmo-trx (with limesdr) may take a long time to answer to CMDs, which means trx_ctrl_timer will trigger re-transmitting the last sent but yet unacked CMD. Due to the high latency in osmo-trx, the original AND the rentrasnmited CMD are handled after a while and RSP messages are sent for both. When osmo-bts-trx receives the first RSP, it was marking the CMD as acked and carried on with next one. Then, when the RSP from the retransmited CMD arrives, it already lost state and doesn't know where does that come from. As a result, osmo-bts-trx shutdowns. The issue can be seen in the following truncated log from osmo-bts-trx with TRX category enabled: 20180117135228175 Enqueuing TRX control command 'CMD RXTUNE 1782000' 20180117135228175 Enqueuing TRX control command 'CMD TXTUNE 1877000' 20180117135228175 Enqueuing TRX control command 'CMD SETTSC 7' 20180117135228175 Enqueuing TRX control command 'CMD POWERON' 20180117135228175 Enqueuing TRX control command 'CMD SETRXGAIN 1' 20180117135228175 Enqueuing TRX control command 'CMD SETPOWER 20' 20180117135228175 Enqueuing TRX control command 'CMD SETSLOT 0 5' ... 20180117135249829 Response message: 'RSP POWEROFF 0' 20180117135249855 Response message: 'RSP RXTUNE 0 1782000' 20180117135249876 Response message: 'RSP TXTUNE 0 1877000' 20180117135249876 Response message: 'RSP SETTSC 0 7' 20180117135250648 Response message: 'RSP POWERON 0' 20180117135251150 Response message: 'RSP SETRXGAIN 0 0' 20180117135253151 No response from transceiver for phy0.0 (CMD SETPOWER 20) 20180117135253777 Response message: 'RSP SETPOWER 0 20' 20180117135254535 Clock indication: fn=2018878 20180117135255777 No response from transceiver for phy0.0 (CMD SETSLOT 0 5) ... 20180117135256858 Response message: 'RSP SETPOWER 0 20' 20180117135256858 Discarding duplicated RSP from old CMD 'RSP SETPOWER 0 20' 20180117135256858 Response message: 'RSP SETSLOT 0 0 5' 20180117135256858 Response message: 'RSP SETSLOT 0 0 5' 20180117135256858 Discarding duplicated RSP from old CMD 'RSP SETSLOT 0 0 5' Change-Id: I3633cba212edde878f83ed36aef922aaca6f503a http://cgit.osmocom.org/osmo-bts/commit/?id=8c1d15764377eb6a11aa432661d5afe… commit 8c1d15764377eb6a11aa432661d5afe60c2e8a9c Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Jan 16 18:42:03 2018 +0100 bts-trx: trx_if.c: Improve parsing of received RSP messages from TRX First the cached CMD sent (struct trx_ctrl_msg) is reworked to have the cmdname and the params in different buffers for easier comparison with RSP later. For the receive path (trx_ctrl_read_cb), new function helpers are added to parse the buffer into cmdname+params+code (parse_rsp) and to compare if a given RSP matches the current CMD we sent (cmd_matches_rsp). The reasoning behind this patch is that a way to check for parameters when receiving a RSP will be needed in future work, as before this patch checking of parameters is ignored. This commit is a preparation for commit to check for duplicated responses. Change-Id: I2474cbc3e4457cf04f78e1c168768295e1132034 http://cgit.osmocom.org/osmo-bts/commit/?id=1f80e9815f3bb98ddfabe5aaa9e69c0… commit 1f80e9815f3bb98ddfabe5aaa9e69c0a47b84269 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Jan 16 18:45:46 2018 +0100 bts-trx: trx_if.c: trx_ctrl_read_cb: Move error handling to end of func The move includes a small logic change: If there's a mismatch between the rsp and the cmd, now we bts_shutdown instead of blindly skipping expected RSP and continuing with sending the next CMD in the queue. The change is specially not a problem since next patches are improving the logic furthermore to account for duplicates, different parameters, etc. Change-Id: I7018ded23fe51f364f248ade111aaa80ef46187e http://cgit.osmocom.org/osmo-bts/commit/?id=9a57c7bed4c096ccff4f9fc78b7ef78… commit 9a57c7bed4c096ccff4f9fc78b7ef789eeb18360 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Tue Jan 16 19:16:53 2018 +0100 bts-trx: trx_if.c: Log timedout+retransmitted CMD Change-Id: Ib573c86a1640640c2a61e80fe1f1412b30342b1a ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-trx/l1_if.h | 3 + src/osmo-bts-trx/trx_if.c | 222 +++++++++++++++++++++++++++++++--------------- src/osmo-bts-trx/trx_if.h | 4 +- 3 files changed, 156 insertions(+), 73 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

7 years, 5 months

osmo-bts.git branch master updated. 0.7.0-45-g63948b0

by gitosis＠osmocom.org

7 years, 5 months

osmo-ggsn.git branch master updated. 1.1.0-50-g36b940d

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The OpenGGSN project". The branch, master has been updated via 36b940d1fed8d5780bb69ec7de0d170939d4745e (commit) from e661277b48e3f13c5f630bd31c4759e766c33a40 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-ggsn/commit/?id=36b940d1fed8d5780bb69ec7de0d17… commit 36b940d1fed8d5780bb69ec7de0d170939d4745e Author: Harald Welte <laforge(a)gnumonks.org> Date: Fri Jan 19 15:08:08 2018 +0100 README.md: Remove misleading sentence on sgsnemu As reported by Viktor Tsymbalyuk, "Use the same LAN switch as the one your SGSN is connected to." is of course completely bogus. As long as you have IP routing in place, it doesn't matter at all which switch you are using. Change-Id: I748752337b863b317d2899017b1dc255ced2515d ----------------------------------------------------------------------- Summary of changes: README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) hooks/post-receive -- The OpenGGSN project

7 years, 5 months

osmo-bts.git branch master updated. 0.7.0-44-gf37fcc9

by gitosis＠osmocom.org

7 years, 5 months

osmo-bts.git branch master updated. 0.7.0-42-ge81347f

by gitosis＠osmocom.org

7 years, 5 months

osmo-ci.git branch master updated. 8bd700d33d7a27d42dfb2f5d5c5542d3d76d8657

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CI scripts". The branch, master has been updated via 8bd700d33d7a27d42dfb2f5d5c5542d3d76d8657 (commit) from 5dbe9a4617b136337fb1c5473ea4af8e7798ea0a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-ci/commit/?id=8bd700d33d7a27d42dfb2f5d5c5542d3… commit 8bd700d33d7a27d42dfb2f5d5c5542d3d76d8657 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Fri Jan 19 05:23:37 2018 +0100 jobs: master: also trigger once per day Recently we had changes to osmo-ci, and I noticed that although some master builds were broken by that, the builds were still showing success -- of twenty days ago. Run each master build at least once a day to indicate odd side effect failure sooner. Change-Id: I126de2bab3db22cb693b0fa665f6579de9238fdf ----------------------------------------------------------------------- Summary of changes: jobs/master-builds.yml | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- CI scripts

7 years, 5 months

osmo-bts.git branch master updated. 0.7.0-41-gd1f0a7e

by gitosis＠osmocom.org

7 years, 5 months

libosmocore.git branch master updated. 0.10.2-119-gc4759885

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "An utility library for Open Source Mobile Communications". The branch, master has been updated via c4759885d7c2aedf310739d9a2420ae1d67a0338 (commit) from 23d3161d4bbe80da13bf3e7afb64242dc8b7236c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/libosmocore/commit/?id=c4759885d7c2aedf310739d9a242… commit c4759885d7c2aedf310739d9a2420ae1d67a0338 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Jan 16 02:10:48 2018 +0100 cosmetic: logging: if color is disabled, don't print "" If color output is disabled, skip the empty snprintf() to (not) clear the ANSI color. Also, no need to use a format string of "%s", just pass the string constant directly. That is a micro optimisation as well as clarification of the code. Change-Id: Ie7cb06de160830d2f8ee5718246c0fe311f68d49 ----------------------------------------------------------------------- Summary of changes: src/logging.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 5 months

osmo-ci.git branch master updated. 5dbe9a4617b136337fb1c5473ea4af8e7798ea0a

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CI scripts". The branch, master has been updated via 5dbe9a4617b136337fb1c5473ea4af8e7798ea0a (commit) from a28b789022032b4aece18136abbfe36a5d209e7f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-ci/commit/?id=5dbe9a4617b136337fb1c5473ea4af8e… commit 5dbe9a4617b136337fb1c5473ea4af8e7798ea0a Author: Max <msuraev(a)sysmocom.de> Date: Wed Jan 17 16:22:17 2018 +0100 Don't run OsmoPCU tests in parallel The vty and ctrl tests are enabled by default and are run on hard-coded ports. This causes some builds to fail when run in parallel. Change-Id: I23d5b75825a667e4f043d16a12b841cd8f01af5e ----------------------------------------------------------------------- Summary of changes: jobs/gerrit-verifications.yml | 1 + jobs/master-builds.yml | 1 + 2 files changed, 2 insertions(+) hooks/post-receive -- CI scripts

7 years, 5 months

osmo-ci.git branch master updated. a28b789022032b4aece18136abbfe36a5d209e7f

by gitosis＠osmocom.org

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CI scripts". The branch, master has been updated via a28b789022032b4aece18136abbfe36a5d209e7f (commit) from 595ea2df169b252fb44e2322bf307aa08002c041 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-ci/commit/?id=a28b789022032b4aece18136abbfe36a… commit a28b789022032b4aece18136abbfe36a5d209e7f Author: Max <msuraev(a)sysmocom.de> Date: Wed Jan 17 14:56:36 2018 +0100 Install pip tool into containers The pip(2|3) tool is the officially recommended tool to deal with Python packages [1] with much greater flexibility compared to invoking setup.py directly. As a preparation step for using it to install osmo-python-tests let's add it to container images. [1] https://packaging.python.org/guides/tool-recommendations/ Change-Id: If2702c71cd268ca688e9ecc264f8cd1257c27899 ----------------------------------------------------------------------- Summary of changes: docker/Dockerfile.deb8_amd64 | 2 +- docker/Dockerfile.deb8_i386 | 2 +- docker/Dockerfile_osmocom_jenkins.amd64 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- CI scripts

7 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog