Actions
Bug #78
closedosmo-bts: Infinite loop in the MS power control
Start date:
Due date:
% Done:
0%
Spec Reference:
Description
Report
All the phones were offline, so i logged in and basically osmo-nitb was not getting anything from the bts there was nothing in the log on osmo-nitb, then i checked the bts and i could see only:
2014-03-19_03:32:06.46033 <000b> loops.c:142 LOST SACCH frame of trx=0 chan_nr=0x0a, so we raise MS power 2014-03-19_03:32:06.47744 <000b> loops.c:142 LOST SACCH frame of trx=0 chan_nr=0x0a, so we raise MS power 2014-03-19_03:32:06.49496 <000b> loops.c:142 LOST SACCH frame of trx=0 chan_nr=0x0a, so we raise MS power
I've restarted osmo-bts and it started to work again. For some reason got in a loop because all i could see was just that message.
Conclusion
Needs further research. The environment where this happened has lots of phones at the very edge of coverage, which may trigger various bugs in the lost frames handling.
Actions
