osmo-bts: Infinite loop in the MS power control
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.
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.
Did anyone observe this recently ?
This issue is from 3 years ago. In the mean time all the code related to this has had major changes and the original issue also didn't include a way to reproduce.
The PA code is also "scheduled" for some overhaul anyway in another issue.
So unless someone observes this currently on a current up-to-date setup and has the ability to provide more debug traces, I'd just close this as "can't reproduce".
- Status changed from New to Rejected
we just reject it for now, it can be re-opened if anyone ever observes it again. If it was happening for other people at all, I suppose we would have had other reports. It's not like an infinite loop is something you would ever miss to notice...