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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 6 18:19:00 UTC 2019


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

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

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

--- Comment #12 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #11)
> (In reply to Martin Peres from comment #5)
> > Your claim did not hold up to reality as it is still happening at every
> > single run... try again?
> 
> I missed that this was about the drmtip runs, hence the confusion.
> 
> 
> commit 0eb6a3f7ef99e7de19efb1293be0571b1d4e83cd
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> Date:   Fri Feb 8 15:37:04 2019 +0000
> 
>     drm/i915: Force the GPU reset upon wedging
>     
>     When declaring the GPU wedged, we do need to hit the GPU with the reset
>     hammer so that its state matches our presumed state during cleanup. If
>     the reset fails, it fails, and we may be unhappy but wedged. However, if
>     we are testing our wedge/unwedged handling, the desync carries over into
>     the next test and promptly explodes.
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=106702
>     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 intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20190208153708.20023-3-
> chris at chris-wilson.co.uk

Thanks! This definitely fixed the issue!

-- 
You are receiving this mail because:
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/20190306/94865425/attachment-0001.html>


More information about the intel-gfx-bugs mailing list