[Bug 104007] [BAT] igt at gem_ringfill@basic-default-hang - dmesg-warn - *ERROR* Failed to reset chip: -110 - and the aftermaths of a wedged CPU.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 1 16:33:38 UTC 2017


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

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

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

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit f7096d40eea84d32eb1e3b0f2b4407167aae9a83
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri Dec 1 12:20:11 2017 +0000

    drm/i915: Sleep and retry a GPU reset if at first we don't succeed

    As we declare the GPU wedged if the reset fails, such a failure is quite
    terminal. Before taking that drastic action, let's sleep first and try
    active, in the hope that the hardware has quietened down and is then
    able to reset. After a few such attempts, it is fair to say that the HW
    is truly wedged.

    v2: Always print the failure message now, we precheck whether resets are
    disabled.

    References: https://bugs.freedesktop.org/show_bug.cgi?id=104007
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20171201122011.16841-1-chris@chris-wilson.co.uk
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>

Now let's just wait a month to see if it reoccurs.

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


More information about the intel-gfx-bugs mailing list