Andy, OK, the ball is in your court. Karol can't reproduce it, thus it will require you sending debug information back so we can get this solved.
-- Steve On Fri, 19 Aug 2016 12:35:24 +0200 karol herbst <[email protected]> wrote: > Hi everybody, > > is there any update on that issue I missed somehow? I really don't > want to leave the mmiotracer in a state, where it breaks something > while fixing other issues. > > But for now, without being able to even reproduce the issue, I can't > really do much, because the code in the current state looks sane to > me. Maybe this case includes the mmiotracer cleaning things up and > arms new region for mmiotracing and that's why it fails? Besides that, > I have no idea and no way to reproduce this, so I can't help this way. > > Greetings > > 2016-08-02 18:13 GMT+02:00 Steven Rostedt <[email protected]>: > > On Tue, 2 Aug 2016 19:08:24 +0300 > > Andy Shevchenko <[email protected]> wrote: > > > >> I don't think so, since linux-next doesn't work until I revert this commit. > >> > >> I can try exactly v4.6 (yep, I tried stable versions, including > >> v4.4.16 that's why all of them failed to me) if you still would like > >> me to do so. > > > > If linux-next doesn't work, then don't bother. > > > > That commit obviously broke something and you'll probably need help > > from Karol to fix it. > > > > Thanks, > > > > -- Steve
