[Bug 111639] [CI][RESUME] igt at gem_vm_create@isolation - dmesg-warn - GEM_BUG_ON(!intel_context_is_pinned(ce))

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Oct 16 10:47:23 UTC 2019


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

--- Comment #6 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #5)
> commit ae911b23d2f06c5d0a3e32768bedea857cadd269
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Mon Sep 23 12:00:53 2019 +0100
> 
>     drm/i915/execlists: Relax assertion for a pinned context image on reset
>     
>     A gpu hang can occur at any time, given a sufficiently angry gpu. An
>     example is when it forgets to perform a context-switch at the end of a
>     request, leaving us with a hanging GPU on a completed request. Here, we
>     may retire the request, only leaving its context alive via the active
>     barrier. When we reset the GPU on a completed request, we do not modify
>     its context image (just updating the ring state) and can safely defer
>     the assertion that we have the image pinned and ready to modify.
>     
>     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111639
>     Fixes: dffa8feb3084 ("drm/i915/perf: Assert locking for
> i915_init_oa_perf_state()")
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
>     Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
>     Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20190923110056.15176-1-
> chris at chris-wilson.co.uk

Thanks, this issue was seen twice on fi-tgl-u, two runs apart. Now it has not
been seen in 23 runs. Looks good!

-- 
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/20191016/faafd102/attachment.html>


More information about the intel-gfx-bugs mailing list