Skip to content
Sign in
Success

#22208 (Jun 20, 2026, 7:07:11 AM)

Started 13 hr ago
Took 5 min 4 sec on build5-deb12build-ansible

Started by upstream project gerrit-osmo-bts build number 1257
originally caused by:

This run spent:

  • 5.9 sec waiting;
  • 5 min 4 sec build duration;
  • 5 min 10 sec total from scheduled to completion.
Revision: 0199c10855bc7dda1965b6ce991c1d69bc85e9ba
Repository: $GERRIT_REPO_URL
  • master
osmo-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().

Change-Id: If787ab7ed70aa2dcb0389ceb58620c2302c3431a
AI-Assisted: yes (Claude)
Related: OS#7020, OS#6794
Vadim Yanitskiy at