[Bug 109661] [CI][SHARDS] igt at gem_eio@unwedge-stress - fail - Failed assertion: med < limit && max < 5 * limit

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 5 11:31:10 UTC 2019


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

--- Comment #17 from Chris Wilson <chris at chris-wilson.co.uk> ---
For reference,

commit f0e39642f6f8da5406627bfa79c6600df949e203 (upstream/master,
origin/master, origin/HEAD)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Jul 2 12:40:45 2019 +0100

    i915/gem_eio: Assert the hanging request is correctly identified

    When forcing a reset, it is crucial that the kernel correctly identifies
    the injected hang. Verify this is the case for reset-stress.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>

One hypothesis is that we are not resetting the guilty request and so hitting a
hangcheck instead.

-- 
You are receiving this mail because:
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/20190705/96d9f208/attachment.html>


More information about the intel-gfx-bugs mailing list