[Bug 99733] [ILK] [BAT] gem_exec_fence at await-hang-default hangs on CI

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #4 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit fe3288b5da2c1286a7aac1fb1b2234caa752a81b
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Sun Feb 12 17:20:01 2017 +0000

    drm/i915: Park the breadcrumbs signaler across a GPU reset

    The signal threads may be running concurrently with the GPU reset. The
    completion from the GPU run asynchronous with the reset and two threads
    may see different snapshots of the state, and the signaler may mark a
    request as complete as we try to reset it. We don't tolerate 2 different
    views of the same state and complain if we try to mark a request as
    failed if it is already complete. Disable the signal threads during
    reset to prevent this conflict (even though the conflict implies that
    the state we resetting to is invalid, we have already made our
    decision!).

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99733
    References: https://bugs.freedesktop.org/show_bug.cgi?id=99671
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
http://patchwork.freedesktop.org/patch/msgid/20170212172002.23072-4-chris@chris-wilson.co.uk
    Reviewed-by: Mika Kuoppala <mika.kuoppala at intel.com>

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