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/.
Sandi Suhendro djks74 at gmail.comHi Gullik, you might have same issued as here https://osmocom.org/issues/3339 On Sat, Jan 5, 2019 at 2:59 AM Gullik Webjorn <gullik.webjorn at corevalue.se> wrote: > This is the sequence of events that preceedes a failure in > osmo-trx-lime. Before this event everything looks > > normal, and sometimes I can see the messages relating to phones > selecting this bts. But, then I get many hundreds > > of fail messages, overfilling the terminal buffer. > > I managed to catch ONE event, it follows....at 17:53:26...... > > Fri Jan 4 17:53:22 2019 DMAIN <0000> Transceiver.cpp:1039 > [tid=3043908688] ClockInterface: sending IND CLOCK 2012824 > Fri Jan 4 17:53:23 2019 DMAIN <0000> Transceiver.cpp:1039 > [tid=3043908688] ClockInterface: sending IND CLOCK 2013041 > Fri Jan 4 17:53:24 2019 DMAIN <0000> Transceiver.cpp:1039 > [tid=3043908688] ClockInterface: sending IND CLOCK 2013257 > Fri Jan 4 17:53:25 2019 DMAIN <0000> Transceiver.cpp:1039 > [tid=3043908688] ClockInterface: sending IND CLOCK 2013474 > Fri Jan 4 17:53:26 2019 DDEV <0002> LMSDevice.cpp:600 [tid=3043908688] > chan 0 recv buffer of len 2500 expect 331871c got 3318b18 (3318b18) > diff=3fc > Fri Jan 4 17:53:26 2019 DDEV <0002> LMSDevice.cpp:600 [tid=3043908688] > chan 0 recv buffer of len 2500 expect 33190e0 got 3320c64 (3320c64) > diff=7b84 > Fri Jan 4 17:53:26 2019 DDEV <0002> LMSDevice.cpp:600 [tid=3043908688] > chan 0 recv buffer of len 2500 expect 3319aa4 got 3321628 (3321628) > diff=7b84 > Fri Jan 4 17:53:26 2019 DDEV <0002> LMSDevice.cpp:600 [tid=3043908688] > chan 0 recv buffer of len 2500 expect 331a468 got 3321fec (3321fec) > diff=7b84 > Fri Jan 4 17:53:26 2019 DDEV <0002> LMSDevice.cpp:600 [tid=3043908688] > chan 0 recv buffer of len 2500 expect 331ae2c got 33229b0 (33229b0) di > > after this, possibly 30 seconds later ?? the BTS restarts ?? and the trx > synchronizes up, config is done, and log starts logging IND CLOCK every > second... > > then this same event happens.....and we have a loop..... > > This is on an orange PI Zero, arm, so maybe not visible on your > platforms..... > > Gullik > > > -- Best Regards, Sandi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20190105/428005f8/attachment.htm>