Attention is currently required from: osmith, pespin.
fixeria has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email )
Change subject: bts: set osmo-bts sched priority to 30
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Patchset:
PS1:
In the case of sysmoBTS, it helped to increase priority:
https://gerrit.osmocom.org/c/osmo-bts/+/34581
> I recall I set those values after doing some testing myself a few days/weeks ago?
This was for fake_trx.py, but here we're targeting osmo-bts-trx.
> I'd also need to confirm prio 30 is actually higher prio than prio 10...
```
07:17:29 PM - osmith(a)im.sysmocom.de: Processes scheduled under one of the real-time policies (SCHED_FIFO, SCHED_RR) have a sched_priority value in the range 1 (low) to 99 (high)
07:18:05 PM - osmith(a)im.sysmocom.de: (from https://www.man7.org/linux/man-pages/man7/sched.7.html)
```
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I828422e2363a58ca8c19d0f1b8a1b7d4e4bc031e
Gerrit-Change-Number: 40153
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 25 Apr 2025 13:39:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Attention is currently required from: fixeria, osmith.
pespin has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email )
Change subject: bts: set osmo-bts sched priority to 30
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
I fail to see why changing the rt prio from one value to another helps here.
Is there another process with higher prio actually generating trouble?
I recall I set those values after doing some testing myself a few days/weeks ago?
I'd also need to confirm prio 30 is actually higher prio than prio 10...
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I828422e2363a58ca8c19d0f1b8a1b7d4e4bc031e
Gerrit-Change-Number: 40153
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 25 Apr 2025 12:50:05 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email )
Change subject: bts: set osmo-bts sched priority to 30
......................................................................
bts: set osmo-bts sched priority to 30
Change the scheduling priority from 10 to 30, as we are currently see
osmo-bts suffering from scheduling latency in jenkins even though we
don't run other jobs at that time:
20250425034138405 DL1C ERROR PC clock skew: elapsed_us=387574, error_us=382959 (scheduler_trx.c:449)
This testsuite currently gets executed through docker-playground and it
fetches this config from osmo-ttcn3-hacks (see
If15461240f3037c142c176fc7da745a1701ae3f8).
Related: osmo-ci I0162f7299c8e37f893ffa10ddc4c8edece29ed7f
Change-Id: I828422e2363a58ca8c19d0f1b8a1b7d4e4bc031e
---
M bts/osmo-bts.cfg
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/53/40153/1
diff --git a/bts/osmo-bts.cfg b/bts/osmo-bts.cfg
index a683a03..e0fadb1 100644
--- a/bts/osmo-bts.cfg
+++ b/bts/osmo-bts.cfg
@@ -33,7 +33,7 @@
bind 127.0.0.1
!
cpu-sched
- policy rr 10
+ policy rr 30
!
e1_input
e1_line 0 driver ipa
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40153?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I828422e2363a58ca8c19d0f1b8a1b7d4e4bc031e
Gerrit-Change-Number: 40153
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/40152?usp=email )
Change subject: rua: Change log err level ERROR->NOTICE regarding received unexpected RUA context
......................................................................
rua: Change log err level ERROR->NOTICE regarding received unexpected RUA context
This is not really an internal error but can actually happen if the HNB
or the HNBGW crashed and state is no longer the same in both.
Change-Id: Ib588bb71ccbe716a495afec27d38f48881e7e1bc
---
M src/osmo-hnbgw/hnbgw_rua.c
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-hnbgw refs/changes/52/40152/1
diff --git a/src/osmo-hnbgw/hnbgw_rua.c b/src/osmo-hnbgw/hnbgw_rua.c
index 7cc1b27..7a51c8d 100644
--- a/src/osmo-hnbgw/hnbgw_rua.c
+++ b/src/osmo-hnbgw/hnbgw_rua.c
@@ -271,7 +271,7 @@
/* A Connect message can only be the first message for an unused RUA context */
if (map) {
/* Already established this RUA context. But then how can it be a Connect message. */
- LOGHNB(hnb, DRUA, LOGL_ERROR, "rx RUA %s for already active RUA context %u\n",
+ LOGHNB(hnb, DRUA, LOGL_NOTICE, "rx RUA %s for already active RUA context %u\n",
rua_procedure_code_name(rua_procedure), context_id);
return -EINVAL;
}
@@ -300,7 +300,7 @@
default:
/* Any message other than Connect must have a valid RUA context */
if (!map) {
- LOGHNB(hnb, DRUA, LOGL_ERROR, "rx RUA %s for unknown RUA context %u\n",
+ LOGHNB(hnb, DRUA, LOGL_NOTICE, "rx RUA %s for unknown RUA context %u\n",
rua_procedure_code_name(rua_procedure), context_id);
rua_tx_disc_conn_fail(hnb, is_ps, context_id);
return -EINVAL;
--
To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/40152?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: osmo-hnbgw
Gerrit-Branch: master
Gerrit-Change-Id: Ib588bb71ccbe716a495afec27d38f48881e7e1bc
Gerrit-Change-Number: 40152
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>