[Bug 104158] [CFL][regression][bisected] Black screen since 4.14.4

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Feb 2 11:49:09 UTC 2018


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

--- Comment #39 from Abhijeet Kumar <abhijeet.kumar at intel.com> ---
Jrq, 

Can you still repro the issue on dinq kernel without additional cmdline
parameter which Jose suggested ? 

If yes can you try reverting the below patch and retry ?

commit 669c9215afea4e3684ef13e54e6908e9ae34f0ae
Author: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
Date:   Mon Sep 4 12:48:38 2017 +0200

    drm/atomic: Make async plane update checks work as intended, v2.

    By always keeping track of the last commit in plane_state, we know
    whether there is an active update on the plane or not. With that
    information we can reject the fast update, and force the slowpath
    to be used as was originally intended.

    We cannot use plane_state->crtc->state here, because this only mentions
    the most recent commit for the crtc, but not the planes that were part
    of it. We specifically care about what the last commit involving this
    plane is, which can only be tracked with a pointer in the plane state.

    Changes since v1:
    - Clean up the whole function here, instead of partially earlier.
    - Add mention in the commit message why we need commit in plane_state.
    - Swap plane->state in intel_legacy_cursor_update, instead of
      reassigning all variables. With this commit We know that the cursor
      is not part of any active commits so this hack can be removed.

    Cc: Gustavo Padovan <gustavo.padovan at collabora.com>
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
    Reviewed-by: Gustavo Padovan <gustavo.padovan at collabora.com>
    Reviewed-by: Daniel Vetter <daniel.vetter at ffwll.ch> #v1
    Link:
https://patchwork.freedesktop.org/patch/msgid/20170904104838.23822-7-maarten.lankhorst@linux.intel.com
    [mlankhorst: Amend commit for merge conflicts with drm-intel]

-- 
You are receiving this mail because:
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/20180202/8d18754a/attachment-0001.html>


More information about the intel-gfx-bugs mailing list