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 08:48:30PM +0700, Vadim Yanitskiy wrote: > Neels, > > > What would be possible reasons for this failure, > > and how can we go about fixing it? > > As I know, this happens when scheduler detects, that > system time is changed. For example, it might be caused > by NTP time correction. > > - Do you have NTP enabled? yes, indeed. But I wouldn't expect that frequent changes of as much as four seconds? We could switch off NTP ... though I enjoy having timestamps identical to my own box's time. > - Have you specified process realtime priority? Yep. Wait, have I? Looking up cmdlines from the log: osmo-trx -x osmo-bts-trx -r 1 -c [...] At least for osmo-bts-trx I have -r 1. Do I need to do the same for osmo-trx? No, it does so by default, right? 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. Hmm, doesn't NTP log its clock corrections somewhere? Can't find any... Thanks Vadim! ~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/ad5013dd/attachment.bin>