<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@i915_selftest@live_hangcheck - dmesg-fail - igt_atomic_reset_engine timed out, cancelling test." href="https://bugs.freedesktop.org/show_bug.cgi?id=110429#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@i915_selftest@live_hangcheck - dmesg-fail - igt_atomic_reset_engine timed out, cancelling test." href="https://bugs.freedesktop.org/show_bug.cgi?id=110429">bug 110429</a> from <a class="email" href="mailto:arkadiusz.hiler@intel.com" title="Arek Hiler <arkadiusz.hiler@intel.com>"> Arek Hiler</a> <pre>(In reply to Francesco Balestrieri from <a href="show_bug.cgi?id=110429#c2">comment #2</a>) > 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. If it is a real issue, not a single time random fluke, it means we may fail to reset from atomic context from time to time, leading to a wedged GPU if it ever happens on a live system. But that's a stretch. TBH, I don't think that this particular issue has anything to do with atomic contexts. It is just one engine being randomly stuck or taking more time to reset than expected. So it is not that serious, especially with this failure rate. Let's keep an eye on this.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>