Started by upstream project "gerrit-osmo-bts" build number 1,2541254gerrit-osmo-btsjob/gerrit-osmo-bts/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImaster00005547975547971.078647864056266177117711<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btshttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/lastBuild/artifacthttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/changeshttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/lastBuild/https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/lastBuild/testReportfalse#1253554797566551gerrit-osmo-bts-build #12531253falsefalse1253145499SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/1253/src/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyfixeriaCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000079512795121.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537951276630gerrit-osmo-bts-build » BTS_MODEL=lc15,FIRMWARE_VERSION=litecell15,0,default,osmocom-gerrit #12531253falsefalse1253145502SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=lc15,FIRMWARE_VERSION=litecell15,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00518945189472260722601.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537226068350gerrit-osmo-bts-build » BTS_MODEL=lc15,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145511SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=lc15,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/005046504674461744611.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537446173045gerrit-osmo-bts-build » BTS_MODEL=lc15,FIRMWARE_VERSION=v2017.01,0,default,osmocom-gerrit #12531253falsefalse1253145509SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=lc15,FIRMWARE_VERSION=v2017.01,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00613986139866070660701.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12536607065198gerrit-osmo-bts-build » BTS_MODEL=oc2g,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145512SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=oc2g,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00741957419564731647311.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12536473168225gerrit-osmo-bts-build » BTS_MODEL=oc2g,FIRMWARE_VERSION=oc2g,0,default,osmocom-gerrit #12531253falsefalse1253145514SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=oc2g,FIRMWARE_VERSION=oc2g,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000076352763521.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537635277533gerrit-osmo-bts-build » BTS_MODEL=oc2g,FIRMWARE_VERSION=oc2g-next,0,default,osmocom-gerrit #12531253falsefalse1253145504SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=oc2g,FIRMWARE_VERSION=oc2g-next,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000073159731591.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537315974825gerrit-osmo-bts-build » BTS_MODEL=oct,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145501SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=oct,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00737237372365187651871.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12536518764059gerrit-osmo-bts-build » BTS_MODEL=oct+trx,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145513SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=oct+trx,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00001009861009861.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#125310098698028gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=femtobts_v2.7,1,default,osmocom-gerrit #12531253falsefalse1253145508SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=femtobts_v2.7,WITH_MANUALS=1,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000073827738271.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537382771992gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145500SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00742557425564145641451.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12536414559413gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v2.4,0,default,osmocom-gerrit #12531253falsefalse1253145515SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v2.4,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/001177649776491.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537764973914gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v3.0.1pre,0,default,osmocom-gerrit #12531253falsefalse1253145506SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v3.0.1pre,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000077637776371.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537763773906gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v3.1,0,default,osmocom-gerrit #12531253falsefalse1253145503SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v3.1,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/000073846738461.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12537384675335gerrit-osmo-bts-build » BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v5.1,0,default,osmocom-gerrit #12531253falsefalse1253145507SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=sysmo,FIRMWARE_VERSION=superfemto_v5.1,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build5-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00201972019767017670171.0000<_2023q1 _class='hudson.plugins.git.util.Build'>374bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1bfdc23b1c676d017da2c1dff26d937be9c9926e2bfdc23b1c676d017da2c1dff26d937be9c9926e22023q1794f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.1f79a23bab0e43959d25363d2a4903127e0a1cb3af79a23bab0e43959d25363d2a4903127e0a1cb3aosmith/1.7.187475a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.275a087d16ba2539b8bcf05102b41d820e818724175a087d16ba2539b8bcf05102b41d820e8187241osmith/1.7.2125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#12536701765194gerrit-osmo-bts-build » BTS_MODEL=trx,FIRMWARE_VERSION=master,0,default,osmocom-gerrit #12531253falsefalse1253145510SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=trx,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=osmocom-gerrit/1253/build4-deb12build-ansiblesrc/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim YanitskiyCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42851GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION46f68007e89b9a6fc1a09fe85d413f1caa1e045dGERRIT_PATCHSET_UPLOADER_NAMEfixeriaGERRIT_PORT29418GERRIT_PROJECTosmo-btsGERRIT_REFSPECrefs/changes/51/42851/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/osmo-btsPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/1254/PROJECT_NAMEosmo-btsBRANCH_CImasterStarted by upstream project "gerrit-osmo-bts-build" build number 1,2531253gerrit-osmo-bts-buildjob/gerrit-osmo-bts-build/00005527865527861.0000125346f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmaster46f68007e89b9a6fc1a09fe85d413f1caa1e045d46f68007e89b9a6fc1a09fe85d413f1caa1e045dmasterssh://jenkins@gerrit.osmocom.org:29418/osmo-btsfalse#1253552786563712gerrit-osmo-bts-build » BTS_MODEL=trx,FIRMWARE_VERSION=master,0,default,raspbian #12531253falsefalse1253145505SUCCESS1781740219369https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts-build/BTS_MODEL=trx,FIRMWARE_VERSION=master,WITH_MANUALS=0,a4=default,label=raspbian/1253/rpi4-raspbian12build-ansible-2src/osmo-bts-trx/scheduler_trx.c46f68007e89b9a6fc1a09fe85d413f1caa1e045d1781740176000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.deosmo-bts-trx: shut down on stale clock indication from transceiver We expect the transceiver to be a reliable, monotonic clock source. If it reports an FN far behind our local timer (elapsed_fn < 0) while far more wall-clock time elapsed than its FN advance accounts for, its clock has likely stalled and the indication carries a stale frame number. Acting on it drags the scheduler backwards and re-transmits already-sent TDMA frames, corrupting lchan-internal state(s). Detect this and shut down the process, same rationale as the existing "PC clock skew too high" check in trx_fn_timer_cb(). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a Related: OS#7020, OS#6794 2026-06-18 06:49:36 +070046f68007e89b9a6fc1a09fe85d413f1caa1e045dosmo-bts-trx: shut down on stale clock indication from transceivereditsrc/osmo-bts-trx/scheduler_trx.cgithttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiy