On Thu, Sep 06, 2018 at 10:04:53AM +0000, bugzilla-dae...@freedesktop.org wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=107784 > > --- Comment #14 from Michel Dänzer <mic...@daenzer.net> --- > That's not consistent with the merge commit you identified earlier. So I'm > afraid it's likely that you incorrectly classified some commits as good or > bad. > Maybe the problem doesn't occur 100% consistently even with bad commits, so > try > testing longer / more times before declaring a commit as good.
Not consistent? Could you be more specific? Some git magic I forgot again? This time I used git bisect to go through "merge" commits properly. I did test countless times those commits: that would mean this TSC code would "side-effect" an ultra-rare bad condition into an nearly-all-the-time bad condition. That amount of bad luck? Whatever, I'll update amd-staging-drm-next, and go through a full bisection again. I'll need probably days (lucky: I don't work). _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
