[Bug 110429] [CI][SHARDS] igt at i915_selftest@live_hangcheck - dmesg-fail - igt_atomic_reset_engine timed out, cancelling test.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Apr 26 11:32:04 UTC 2019


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|high                        |medium

--- Comment #5 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #4)
> (In reply to Arek Hiler from comment #3)
> > (In reply to Francesco Balestrieri from comment #2)
> > > From:
> > > 
> > > <3> [2204.524458] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset
> > > request timeout
> > > 
> > > It seems that the HW failed to respond and the test timed out. We should
> > > increase the timeout of the test to get the actual failure.
> > 
> > Was there anything done already? Did we increase the timeout? The issue was
> > seen only once in CI_DRM_5922.
> 
> The error has occurred quite rarely across the reset tests over the years,
> and over the years we have applied whatever w/a we could find to reduce the
> rate of incidence. We haven't increased the timeout applied to the selftest
> yet -- and it would not fix the bug, just make the cause more obvious.

So this failure has been twice, once on CFL and once on ICL.

I think your explanation makes sense, and we should try to reduce the
reproduction rate as much as possible, but this does not look like a new
regression, more like an architectural issue.

Dropping the priority to medium so as we can periodically check that this does
not become more apparent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact 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/20190426/bf277905/attachment.html>


More information about the intel-gfx-bugs mailing list