On 30/05/2016 21:34, Holger Freyther wrote: > argh. Could you go to f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0 and > revert it and then try again? Does it work better? > > holger >
This specific problem is gone (I can see data flows and even some packets) but data service is still practically unusable, I get a lot of "Scheduling Ack/Nack, because MS is stalled." messages. On 02/06/2016 10:47, Max wrote: > Hi. > > Could you please make a ticket in http://projects.osmocom.org/ to make > sure this won't get lost in ML archives? Yes, I just wanted to make sure that I wasn't the only one experiencing this problem. I am now bisecting d87e1d6ab747423d3668c74d16201a5d967accf0..f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0 commits to identify which commit introduced these reliability problems
