sporadic crash of osmo-bts-trx in osmo-gsm-tester runs
The osmo-bts-trx process sometimes dies prematurely during osmo-gsm-tester runs using the Ettus B210.
The cause is not clear yet, no core file seems to be created.
For example, see http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_run/591/
The sporadic "crashes" are actually intentional shutdown by osmo-bts-trx:
20170614021016906 DOML <0001> bts.c:208 Shutting down BTS 0, Reason No clock from osmo-trx
The end of the log shows "Shutdown timer expired", which has a three second expiry time.
About 30 logging lines above that, the shutdown reason is logged.
The "No clock" is logged about two seconds after the OML has successfully set up the BTS.
Immediately following that, the OML is torn down again, concluding in
Shutdown timer expired
I am not so sure about how to fix this, will have to ask osmo-trx guys.
- Status changed from New to In Progress
- Assignee set to neels
https://gerrit.osmocom.org/2909 <-- sets l1c logging level to notice
20170614032014399 DRSL <0000> rsl.c:2333 (bts=0,trx=0,ts=0,ss=2) Fwd RLL msg EST_IND from LAPDm to A-bis 20170614032018533 DL1C <0006> scheduler_trx.c:1451 PC clock skew: elapsed uS 4136730 20170614032018533 DOML <0001> bts.c:208 Shutting down BTS 0, Reason No clock from osmo-trx 20170614032018533 DL1C <0006> scheduler.c:240 Exit scheduler for trx=0 20170614032018533 DL1C <0006> scheduler.c:216 Init scheduler for trx=0 20170614032018533 DOML <0001> oml.c:280 OC=RADIO-CARRIER INST=(00,00,ff) AVAIL STATE OK -> Off line [...] Shutdown timer expired
I asked on openbsc@: http://lists.osmocom.org/pipermail/openbsc/2017-June/010802.html
- Category set to osmo-bts-trx
- osmo-bts uses gettimeofday() to determine how much system time has expired between two FN indications from OSmoTRX
- the maximum permitted value is 50*4.6ms, i.e. 50 TDMA frames, totalling to 230750, i.e. 230.75ms
- the actual skew as reported here is 4.13 seconds
I assume that the
--realtime argument is used when starting osmo-bts-trx, at least http://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_run/591/ indicates so.