[Bug 106684] [CI] igt at .* - dmesg-warn/dmesg-fail - *ERROR* rcs0: reset request timeout

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Aug 13 15:51:11 UTC 2018


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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Chris Wilson <chris at chris-wilson.co.uk> ---
The behaviour should have substantially changed with

commit f4e60c5cfbf217cc9faa3aeb63742860154fcfef (HEAD -> drm-intel-next-queued,
drm-intel/drm-intel-next-queued)
Author: Mika Kuoppala <mika.kuoppala at linux.intel.com>
Date:   Mon Aug 13 16:01:16 2018 +0300

    drm/i915: Force reset on unready engine

    If engine reports that it is not ready for reset, we
    give up. Evidence shows that forcing a per engine reset
    on an engine which is not reporting to be ready for reset,
    can bring it back into a working order. There is risk that
    we corrupt the context image currently executing on that
    engine. But that is a risk worth taking as if we unblock
    the engine, we prevent a whole device wedging in a case
    of full gpu reset.

    Reset individual engine even if it reports that it is not
    prepared for reset, but only if we aim for full gpu reset
    and not on first reset attempt.

    v2: force reset only on later attempts, readability (Chris)
    v3: simplify with adequate caffeine levels (Chris)
    v4: comment about risks and migitations (Chris)

    Cc: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180813130116.7250-1-mika.kuoppala@linux.intel.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
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/20180813/4fde176e/attachment.html>


More information about the intel-gfx-bugs mailing list