<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=53926#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=53926">bug 53926</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>Ok, this bug here does not seem to be bisectable - the parent of c10e408a00bb74c39f4f9b should be good since an earlier bisect point contained it and was good. But actually it's a bad commit, too. Hence the really strange bisect result. One thing you can try is to restart bisect with bad commit c10e408a00bb74c39f4f and good commit v3.4. git bisect will then first go back in time to test the common merge base, and if that works, too, will restart a bisect from that point. Sorry if this is such a mess, usually it's much simpler to bisect a regression :(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>