<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Intel driver 2.21.13 hangs on shutdown process" href="https://bugs.freedesktop.org/show_bug.cgi?id=67490#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Intel driver 2.21.13 hangs on shutdown process" href="https://bugs.freedesktop.org/show_bug.cgi?id=67490">bug 67490</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>You are not using SNA, which is why this is quite strange. You have two choices, either do a normal bisect looking for the commit that introduced the hang, or a "reversed" bisect that looks for the commit that fixes the hang. In a reversed bisect, you would treat as any hang as good, and any working commit as bad: $ git bisect start good 2.21.13 # broken $ git bisect bad master # works $ make && sudo make install # test $ git bisect bad # if it works (shuts down without a hang) $ git bisect good # if it hangs and repeat make / git bisect (bad|good). I suspect that both bisects will be useful to understanding this mystery.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>