[Bug 106523] [CI][IGT] DRM-Tip 4.17-rc5 pull made igt at gem_eio@ tests unstable

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 17 04:43:12 UTC 2018


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

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

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

--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 3f6e9822308127104a7bb007ca569f2c57d03b67
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed May 16 19:33:55 2018 +0100

    drm/i915: Stop parking the signaler around reset

    We cannot call kthread_park() from softirq context, so let's avoid it
    entirely during the reset. We wanted to suspend the signaler so that it
    would not mark a request as complete at the same time as we marked it as
    being in error. Instead of parking the signaling, stop the engine from
    advancing so that the GPU doesn't emit the breadcrumb for our chosen
    "guilty" request.

    v2: Refactor setting STOP_RING so that we don't have the same code thrice

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Michałt Winiarski <michal.winiarski at intel.com>
    CC: Michel Thierry <michel.thierry at intel.com>
    Cc: Jeff McGee <jeff.mcgee at intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180516183355.10553-8-chris@chris-wilson.co.uk

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


More information about the intel-gfx-bugs mailing list