[Bug 105348] [CI] [KBL only] gt at drv_selftest@live_hangcheck - fail - Failed assertion: err == 0 / incomplete system hang?
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Apr 9 20:40:37 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105348
Chris Wilson <chris at chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
I claim to have fixed the incompletes and kbl failures, as of
commit 028666793a0291b63eb61bae7252345821326a1b
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Fri Mar 30 14:18:01 2018 +0100
drm/i915/selftests: Avoid repeatedly harming the same innocent context
We don't handle resetting the kernel context very well, or presumably any
context executing its breadcrumb commands in the ring as opposed to the
batchbuffer and flush. If we trigger a device reset twice in quick
succession while the kernel context is executing, we may end up skipping
the breadcrumb. This is really only a problem for the selftest as
normally there is a large interlude between resets (hangcheck), or we
focus on resetting just one engine and so avoid repeatedly resetting
innocents.
Something to try would be a preempt-to-idle to quiesce the engine before
reset, so that innocent contexts would be spared the reset.
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
Cc: MichaĆ Winiarski <michal.winiarski at intel.com>
CC: Michel Thierry <michel.thierry at intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20180330131801.18327-1-chris@chris-wilson.co.uk
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/20180409/f033b81d/attachment.html>
More information about the intel-gfx-bugs
mailing list