<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][GLK] igt@gem_exec_suspend@basic-s3 hits WARN_ON(wait_for_engine(engine, 50))" href="https://bugs.freedesktop.org/show_bug.cgi?id=102456#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][GLK] igt@gem_exec_suspend@basic-s3 hits WARN_ON(wait_for_engine(engine, 50))" href="https://bugs.freedesktop.org/show_bug.cgi?id=102456">bug 102456</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 fix the suspend failure commit cad9946c2a4375386062131858881cfd30fc1b8f Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Sat Aug 26 12:09:33 2017 +0100 drm/i915: Always sanity check engine state upon idling When we do a locked idle we know that afterwards all requests have been completed and the engines have been cleared of tasks. For whatever reason, this doesn't always happen and we may go into a suspend with ELSP still full, and this causes an issue upon resume as we get very, very confused. If the engines refuse to idle, mark the device as wedged. In the process we get rid of the maybe unused open-coded version of wait_for_engines reported by Nick Desaulniers and Matthias Kaehlcke. v2: Suppress the -EIO before suspend, but keep it for seqno wrap. but leaves the underlying issue unresolved. FAIL -> WARN.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>