[Bug 108133] [CI][DRMTIP] igt at gem_eio@wait-wedge-1us - dmesg-warn - GEM_BUG_ON(!intel_engine_is_idle(engine))

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Oct 30 16:55:55 UTC 2018


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

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #2)
> I am not convinced, but
> 
> commit 88a83f3c2d7a87ce7c9c4171dec8e2fb48070288
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Thu Oct 4 09:21:19 2018 +0100
> 
>     drm/i915: Only reset seqno if actually idle
>     
>     Before we can reset the seqno, we have to be sure the engines are idle.
>     In debugfs/i915_drop_caches_set, we do wait_for_idle but allow ourselves
>     to be interrupted. We should only proceed to reset the seqno then if we
>     were not interrupted, and so also avoid overwriting the error status.
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=108133
>     Fixes: 6b048706f407 ("drm/i915: Forcibly flush unwanted requests in
> drop-caches")
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
>     Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
>     Reviewed-by: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20181004082119.24970-1-
> chris at chris-wilson.co.uk
> 
> may have an effect. Otherwise this bug is too weird for me.

It's been a month, and it is a drmtip run. Let's close this bug.

-- 
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/20181030/cd0b6689/attachment.html>


More information about the intel-gfx-bugs mailing list