From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199101] AMDGPU Fury X random screen flicker on Linux kernel 4.16rc5
Date: Fri, 06 Apr 2018 10:58:30 +0000 [thread overview]
Message-ID: <bug-199101-2300-keH8UIJeMR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199101-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199101
Paweł (pawel.pc44@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pawel.pc44@gmail.com
--- Comment #14 from Paweł (pawel.pc44@gmail.com) ---
Since nobody cared I bisected the issue:
>commit 36cc549d59864b7161f0e23d710c1c4d1b9cf022
>Author: Shirish S <shirish.s@amd.com>
>Date: Wed Feb 28 12:14:58 2018 +0530
>
> drm/amd/display: disable CRTCs with NULL FB on their primary plane (V2)
>
> The below commit
>
> "drm/atomic: Try to preserve the crtc enabled state in
> >drm_atomic_remove_fb, v2"
>
> introduces a slight behavioral change to rmfb. Instead of disabling a crtc
> when the primary plane is disabled, it now preserves it.
>
> This change leads to BUG hit while performing atomic commit on amd driver.
>
> As a fix this patch ensures that we disable the CRTC's with NULL FB by
> >returning
> -EINVAL and hence triggering fall back to the old behavior and turning off
> >the
> crtc in atomic_remove_fb().
>
> V2: Added error check for plane_state and removed sanity check for crtc.
>
> Signed-off-by: Shirish S <shirish.s@amd.com>
> Signed-off-by: Pratik Vishwakarma <Pratik.Vishwakarma@amd.com>
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>
>:040000 040000 9b8fd67908699d2651daa93fab59b21e7a76b1c6
>>21bbcb69561e67e5acf63d56344c7ba7ac4146a6 M drivers
It makes my AMD Radeon RX 480 flicker a lot.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-06 10:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 4:30 [Bug 199101] New: AMDGPU Fury X random screen flicker on Linux kernel 4.16rc5 bugzilla-daemon
2018-03-13 4:30 ` [Bug 199101] " bugzilla-daemon
2018-03-13 9:51 ` bugzilla-daemon
2018-03-20 16:49 ` bugzilla-daemon
2018-03-20 16:49 ` bugzilla-daemon
2018-03-25 2:03 ` bugzilla-daemon
2018-03-25 2:04 ` bugzilla-daemon
2018-03-26 8:58 ` bugzilla-daemon
2018-03-26 18:09 ` bugzilla-daemon
2018-03-30 12:12 ` bugzilla-daemon
2018-03-30 13:15 ` bugzilla-daemon
2018-03-30 13:20 ` bugzilla-daemon
2018-03-30 18:30 ` bugzilla-daemon
2018-04-03 20:29 ` bugzilla-daemon
2018-04-04 7:05 ` bugzilla-daemon
2018-04-06 10:58 ` bugzilla-daemon [this message]
2018-04-06 14:15 ` bugzilla-daemon
2018-04-09 12:43 ` bugzilla-daemon
2018-04-12 15:16 ` bugzilla-daemon
2018-04-13 18:00 ` bugzilla-daemon
2018-04-20 13:14 ` bugzilla-daemon
2018-04-20 17:08 ` bugzilla-daemon
2018-04-21 11:58 ` bugzilla-daemon
2018-04-23 17:19 ` bugzilla-daemon
2018-04-24 16:57 ` bugzilla-daemon
2018-04-24 19:02 ` bugzilla-daemon
2018-04-24 19:24 ` bugzilla-daemon
2018-04-24 19:29 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-199101-2300-keH8UIJeMR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).