[Bug 109677] [CI][DRMTIP] igt at gem_mmap_gtt@hang - fail - Timed out waiting for children

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #4 from Chris Wilson <chris at chris-wilson.co.uk> ---
I am ignoring the icl as that is not interesting (just another clock drift)...

commit 43a8f684b6d1e16c6ecf918332f9b35686bf7edd (HEAD -> drm-intel-next-queued,
drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Feb 21 10:29:19 2019 +0000

    drm/i915: Reorder struct_mutex-vs-reset_lock in i915_gem_fault()

    Annoyingly, struct_mutex was not entirely eliminated from the reset
    pathway; for reasons of its own, intel_display_resume() requires
    struct_mutex to prepare the planes it already captured. To avoid the
    immediate problem of a deadlock between the struct_mutex and the reset
    srcu, we have to acquire the reset_lock before struct_mutex in
    i915_gem_fault(). Now any wait underneath struct_mutex will result us in
    having to forcibly reset all inflight rendering, less than ideal, but
    better than a deadlock (and will do for the short term).

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190221102924.13442-1-chris@chris-wilson.co.uk

Was the bug that should have been reported!

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