[Bug 107799] [CI][SHARDS] igt at gem_eio@in-flight-*-(10ms|1us|immediate) - fail - Failed assertion: elapsed < 250e6
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Nov 30 13:09:46 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=107799
--- Comment #11 from Martin Peres <martin.peres at free.fr> ---
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4736/shard-glk9/igt@gem_eio@reset-stress.html
Starting subtest: reset-stress
(gem_eio:7946) CRITICAL: Test assertion failure function check_wait, file
../tests/i915/gem_eio.c:258:
(gem_eio:7946) CRITICAL: Failed assertion: elapsed < 250e6
(gem_eio:7946) CRITICAL: Wake up following reset+wedge took 445.988ms
Subtest reset-stress failed.
<6> [3804.883762] Console: switching to colour dummy device 80x25
<6> [3804.883866] [IGT] gem_eio: executing
<5> [3804.897459] Setting dangerous option reset - tainting kernel
<7> [3804.901938] [drm:i915_reset_device [i915]] resetting chip
<5> [3804.902142] i915 0000:00:02.0: Resetting chip for Manually set wedged
engine mask = ffffffffffffffff
<5> [3804.914782] Setting dangerous option reset - tainting kernel
<6> [3804.926600] [IGT] gem_eio: starting subtest reset-stress
<5> [3804.936303] Setting dangerous option reset - tainting kernel
<7> [3805.045373] [drm:i915_reset_device [i915]] resetting chip
<5> [3805.045512] i915 0000:00:02.0: Resetting chip for Manually set wedged
engine mask = ffffffffffffffff
<6> [3805.610883] [IGT] gem_eio: exiting, ret=99
<5> [3805.611436] Setting dangerous option reset - tainting kernel
<7> [3805.613946] [drm:i915_reset_device [i915]] resetting chip
<5> [3805.614067] i915 0000:00:02.0: Resetting chip for Manually set wedged
engine mask = ffffffffffffffff
<6> [3805.642387] Console: switching to colour frame buffer device 240x67
--
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/20181130/b5f78627/attachment.html>
More information about the intel-gfx-bugs
mailing list