[Bug 105304] [BAT] [BSW only] igt at gem_sync@basic-each - GPU hung -> wedged -> WARN_ON(intel_gpu_reset(i915, (~0)))

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105304

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
Come back in 6 months to see if this is gone for good!

commit 5692251c254a3d561316c4e8e10c77e470b60658
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Sat Apr 28 12:15:32 2018 +0100

    drm/i915/lrc: Scrub the GPU state of the guilty hanging request

    Previously, we just reset the ring register in the context image such
    that we could skip over the broken batch and emit the closing
    breadcrumb. However, on resume the context image and GPU state would be
    reloaded, which may have been left in an inconsistent state by the
    reset. The presumption was that at worst it would just cause another
    reset and skip again until it recovered, however it seems just as likely
    to cause an unrecoverable hang. Instead of risking loading an incomplete
    context image, restore it back to the default state.

    v2: Fix up off-by-one from including the ppHSWP in with the register
    state.
    v3: Use a ring local to compact a few lines.
    v4: Beware setting the ring local before checking for a NULL request.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180430/e31e8473/attachment.html>