<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BDW]igt/kms_flip/flip-vs-modeset-vs-hang-interruptible randomly causes system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=72631#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [BDW]igt/kms_flip/flip-vs-modeset-vs-hang-interruptible randomly causes system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=72631">bug 72631</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>This should stop that particular assertion failure: commit 3db29744f74017a99d1b430b30623dce405ebb1a Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Fri Feb 21 09:38:43 2014 +0000 kms_flip: Try to make hang_gpu() robust against hanging the GPU On a bad day, hanging the GPU may be terminal. Yet even if the GPU is terminally wedged we expect modesetting (and pageflips) to continue. That deserves to be a dedicated test, but in the meantime we should strive to avoid falling over just because the code is not resilient. Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> but there are probably a couple of other spots that require help before we can run the testing against a terminally wedged GPU.</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>