<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784">bug 107784</a> from <a class="email" href="mailto:sylvain.bertrand@gmail.com" title="Sylvain BERTRAND <sylvain.bertrand@gmail.com>"> Sylvain BERTRAND</a> <pre>On Thu, Sep 06, 2018 at 10:04:53AM +0000, <a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a> wrote: > <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="show_bug.cgi?id=107784">https://bugs.freedesktop.org/show_bug.cgi?id=107784</a> > > --- <a href="show_bug.cgi?id=107784#c14">Comment #14</a> from Michel Dänzer <<a href="mailto:michel@daenzer.net">michel@daenzer.net</a>> --- > 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).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>