[Bug 110771] [CI][DRMTIP] igt at gem_partial_pwrite_pread@reads-snoop - dmesg-warn - RPM wakelock ref not held during HW access

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 29 08:27:33 UTC 2019


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

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

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

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 2e2f08d02dd282751e8d329f373dd85d49ae7f90 (HEAD -> drm-intel-next-queued,
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue May 28 08:53:54 2019 +0100

    drm/i915: Take a runtime pm wakeref for atomic commits

    Before we start prepping the system for an atomic modeset, wake the
    device up. We then keep track of this wakeref until we complete the
    atomic commit, so we hold keep the device awake for all potential HW
    access, and do not allow the device to sleep with a pending modeset.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110771
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Ville Syrjälä <ville.syrjala at linux.intel.com>
    Cc: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
    Reviewed-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190528075354.22341-1-chris@chris-wilson.co.uk


Note to self: intel_rps_mark_interactive() is not let off the hook, as it's
check to see whether RPS is alive is racy.

-- 
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/20190529/9be76b75/attachment.html>


More information about the intel-gfx-bugs mailing list