[Bug 104513] freezes with dual monitors: bo is already pinned in ggtt with incorrect alignment

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 2 18:00:06 UTC 2018


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

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

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

--- Comment #18 from Chris Wilson <chris at chris-wilson.co.uk> ---
Should be fixed by commit 7e7367d3bc6cf27dd7e007e7897fcebfeff1ee8b (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:   Sat Jun 30 10:05:09 2018 +0100

    drm/i915: Try GGTT mmapping whole object as partial

    If the whole object is already pinned by HW for use as scanout, we will
    fail to move it to the mappable region and so must resort to using a
    partial VMA covering the whole object.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104513
    Fixes: aa136d9d72c2 ("drm/i915: Convert partial ggtt vma to full ggtt if it
spans the entire object")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
    Cc: Matthew Auld <matthew.william.auld at gmail.com>
    Reviewed-by: Matthew Auld <matthew.william.auld at gmail.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180630090509.469-1-chris@chris-wilson.co.uk

Please try testing with drm-tip and report if you can still trigger the issue.

-- 
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/20180702/42027656/attachment-0001.html>


More information about the intel-gfx-bugs mailing list