7 Jul
2017
7 Jul
'17
3:23 a.m.
On Thu, Jul 6, 2017 at 5:59 PM, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
Kudos to pespin for finding that issue. Hopefully we can also get rid of the remaining odd failure.
Absolutely.
Interesting that it doesn't happen every time, nor on everyone else's equipment. Maybe CPU speed or faster I/O makes it less likely to happen.
That is likely. The bts-trx socket interface has been fairly static and I know that L2 scheduling issues have existed in OpenBTS. I doubt that there has been any recent regression; the use of faster CPU's has probably been covering up the issue for a very long time.
-TT