<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate" href="https://bugs.freedesktop.org/show_bug.cgi?id=93826#c37">Comment # 37</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 2560x1440 @144Hz graphic glitches and bad refresh rate" href="https://bugs.freedesktop.org/show_bug.cgi?id=93826">bug 93826</a> from <a class="email" href="mailto:jhasse@gmail.com" title="Jan Niklas Hasse <jhasse@gmail.com>"> Jan Niklas Hasse</a> <pre>> Sorry, but I don't know what you mean by "using bitsect". Changes to the source code of the driver are controlled via Git as commits. Assuming it once worked 144 Hz it's possible to use Git to find out which commit caused the flickering. This is done by identifying any commit which worked (good, in your case 4.4) and a commit which doesn't work (bad, 4.8). Bisecting will then help you find the first bad commit faster (by sectioning the pool of possible first bad commits in two sections repeatedly). I'm not sure though that this good commit exists though. Flickering also happens with 4.4 for me.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>