osmo-bts-trx uses non-monotonic system clock for frame number timer
osmo-bts-trx is using regular gettimeofday() calls, i.e. a non-monotonic local system clock for its frame number timers.
This is wrong, as this clock is impacted by changes such as NTP or GPS clock synchronization.
The only relevant clock for osmo-bts-trx frame timer is the clock provided by OsmoTRX, which in turn is based on the hardware sample rate clock of the SDR board.
#3 Updated by laforge about 2 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 70
I've submitted a new CLOCK_MONOTONIC based implementation at https://gerrit.osmocom.org/#/c/3037/
This implementation also contains logging of all related important events, such as missed timer executions, drift between TRX and local clock, etc.