[Bug 106560] [CI] igt at drv_selftest@live_hangcheck - igt_reset_engines failed with error

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Sep 5 10:38:54 UTC 2018


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

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

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

--- Comment #9 from Martin Peres <martin.peres at free.fr> ---
(In reply to Martin Peres from comment #8)
> (In reply to Chris Wilson from comment #7)
> > commit a99b32a6fff7e482a267c72e565c8c410ce793d7 (HEAD ->
> > drm-intel-next-queued, drm-intel/drm-intel-next-queued)
> > Author: Chris Wilson <chris at chris-wilson.co.uk>
> > Date:   Tue Aug 14 18:18:57 2018 +0100
> > 
> >     drm/i915: Clear stop-engine for a pardoned reset
> >     
> >     If we pardon a per-engine reset, we may leave the STOP_RING bit asserted
> >     in RING_MI_MODE resulting in the engine hanging. Unconditionally clear
> >     it on the per-engine exit path as we know that either we skipped the
> >     reset and so need the cancellation, or the reset was successful and the
> >     cancellation is a no-op, or there was an error and we will follow up
> >     with a full-reset or wedging (both of which will stop the engines again
> >     as required).
> >     
> >     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107188
> >     Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106560
> >     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/20180814171857.24673-1-
> > chris at chris-wilson.co.uk
> > 
> > 
> > Please note that the CI run for this patch indicated we have yet another
> > cause for hangs here. When that is detected please do file a fresh bug so we
> > don't have the debug logs confused.
> 
> That seems to have done the trick for this particular issue. Closing now :)

Actually, https://bugs.freedesktop.org/show_bug.cgi?id=106947 was saying that
the following failures are for this issue, and they still happen:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4512/fi-kbl-7500u/igt@drv_selftest@live_hangcheck.html

[...]

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4714/fi-kbl-7567u/igt@drv_selftest@live_hangcheck.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4611/shard-kbl7/igt@drv_selftest@live_hangcheck.html

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


More information about the intel-gfx-bugs mailing list