<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB, IVB] Page flips hang indefinitely, apparently waiting for mmio writes that never happen" href="https://bugs.freedesktop.org/show_bug.cgi?id=75502#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [SNB, IVB] Page flips hang indefinitely, apparently waiting for mmio writes that never happen" href="https://bugs.freedesktop.org/show_bug.cgi?id=75502">bug 75502</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=75502#c11">comment #11</a>) > It takes two to three hours to fail each time, and has sometimes lasted as > long as 3 days before failing. > > git bisect suggests that I've got 16 steps to try to get there on the kernel > alone, at worst case time of 3 days per step. > > Do you have any further clues I could push on before I dive into bisection? If the fail/success is so imbalanced you can try to skew the bisect by picking commits which are more likely to be bad than the perfect middle one (since you can detect those faster). Unfortunately there's no cmdline option for this, so you need to do this by hand. There was a write-up somewhere, but I can't find it any more. Probably not worth the bother though ...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>