[Bug 106702] [CI] igt at gem_eio@in-flight-suspend - incomplete - GEM_BUG_ON(buf[2 * head + 1] != port->context_id)

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #5 from Martin Peres <martin.peres at free.fr> ---
p(In reply to Chris Wilson from comment #4)
> I applied commit c3160da9a6af0e2d8f4fb3410df9d027a178ca3d
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Thu May 31 09:22:45 2018 +0100
> 
>     drm/i915: After reset on sanitization, reset the engine backends
>     
>     As we reset the GPU on suspend/resume, we also do need to reset the
>     engine state tracking so call into the engine backends. This is
>     especially important so that we can also sanitize the state tracking
>     across resume.
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=106702
>     Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
>     Reviewed-by: Mika Kuoppala <mika.kuoppala at intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20180531082246.9763-3-
> chris at chris-wilson.co.uk
> 
> which I claim to be sufficient to prevent this BUG().

Your claim did not hold up to reality as it is still happening at every single
run... try again?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact 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/20180614/a656024b/attachment-0001.html>