This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn Wed, Jun 14, 2017 at 05:41:33PM +0200, Neels Hofmeyr wrote: > It seems that these failures have become less frequent again, which could > indeed be related to NTP activity. I'll switch off NTP and see if these go away > completely. No, despite NTP being switched off, I still see frequent failures due to osmo-bts-trx stopping in mid-air. A recent one was: 20170614170931479 DL1C <0006> scheduler_trx.c:1451 PC clock skew: elapsed uS 328104 20170614170931479 DOML <0001> bts.c:208 Shutting down BTS 0, Reason No clock from osmo-trx i.e. only a third of a second, much less than the four seconds of last time, but still. Any other ideas? Are these necessarily actual clock skews of the host computer? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170614/41d595e4/attachment.bin>