I compiled and installed 4.16rc on Arch Linux via the linux-git AUR package today. After rebooting I noticed some random flickering. Every 20-30 seconds or so a single white flash would take up the entire screen. This occurs on the desktop and in full screen OpenGL Dota 2.
Here's some more system info
OpenGL version string: 3.0 Mesa 17.3.6
AMD Ryzen 7 1800X Eight-Core Processor
Max Speed: 4100 MHz
Current Speed: 3600 MHz
Speed: 3200 MT/s
OpenGL renderer string: AMD Radeon (TM) R9 Fury Series (FIJI / DRM 3.23.0 / 4.15.8-1-ARCH, LLVM 5.0.1)
0b:00.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] [1002:7300] (rev c8)
ASUSTeK COMPUTER INC.
CROSSHAIR VI HERO
BIOS Version: 3008
Please attach the corresponding dmesg output.
Created attachment 274825 [details]
Output from journalctl -k on 4.16.0-rc6
Still happening with rc6
I'm also getting this with a fresh compile as of today (3-24). It's a screen flicker that occurs every few seconds.
OpenGL version string: 3.1 Mesa 18.1.0-devel (git-d60eaf7b1f)
AMD Ryzen 7 1700X Eight-Core Processor
Current Speed: 3800 MHz
Speed: 3200 MT/s
OpenGL renderer string: Radeon RX Vega (VEGA10 / DRM 3.23.0 / 4.16.0-rc6-gd8a5b80568a9, LLVM 6.0.0)
0d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1)
ASUSTeK COMPUTER INC.
ROG STRIX X370-F GAMING
BIOS Version: 3803
Created attachment 274921 [details]
Output from journalctl -k on 4.16.0-rc6-VEGA
(In reply to Kevin McCormack from comment #3)
> Still happening with rc6
Kevin: Is this still happening? And is this working with 4.15 (that's unclear from the initial report)? Just wondering, because I have this issue on the regression reports for 4.16
Created attachment 274949 [details]
It's not a problem on 4.15. It was still a problem on the last rc I tried.
On March 26, 2018 4:58:42 AM EDT, email@example.com wrote:
>Thorsten Leemhuis (firstname.lastname@example.org) changed:
> What |Removed |Added
> CC| |email@example.com
>--- Comment #6 from Thorsten Leemhuis (firstname.lastname@example.org) ---
>(In reply to Kevin McCormack from comment #3)
>> Still happening with rc6
>Kevin: Is this still happening? And is this working with 4.15 (that's
>from the initial report)? Just wondering, because I have this issue on
>regression reports for 4.16
>You are receiving this mail because:
>You reported the bug.
@Michel Dänzer: Any progress with this? It's on the list of regressions for 4.16
Can you bisect?
just fyi I do not get the flicker on 4.16 rc3, this may help to shorten the time it takes to bisect
I get the same issue on arch kernels: linux (4.15), linux-mainline, and from linux-git(4.16rc6) on my Vega 64 when using both latest mesa-git (18) and stable mesa (17) from arch repos.
It seemed not to appear when using fullscreen Vulkan rendering, pointing at GL issues (right?), can examine further later.
Crosshair VI x370 mobo
STRIX Vega 64
I confirm that i have this issue too with final kernel 4.16, Rx560 and mesa-git.
The issue does not appears with the Kernel 4.15.15
I can confirm this issue also exists for the latest (from 2.4.2018) amd-staging-drm-next kernel and for the R9 380 with amdgpu dc.
The issue is also reported and commented on my repo:
Since nobody cared I bisected the issue:
>Author: Shirish S <email@example.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
> -EINVAL and hence triggering fall back to the old behavior and turning off
> crtc in atomic_remove_fb().
> V2: Added error check for plane_state and removed sanity check for crtc.
> Signed-off-by: Shirish S <firstname.lastname@example.org>
> Signed-off-by: Pratik Vishwakarma <Pratik.Vishwakarma@amd.com>
> Reviewed-by: Harry Wentland <email@example.com>
> Signed-off-by: Alex Deucher <firstname.lastname@example.org>
>:040000 040000 9b8fd67908699d2651daa93fab59b21e7a76b1c6
>>21bbcb69561e67e5acf63d56344c7ba7ac4146a6 M drivers
It makes my AMD Radeon RX 480 flicker a lot.
We reproduced the issue and have someone looking into it.
(In reply to Harry Wentland from comment #15)
> We reproduced the issue and have someone looking into it.
Too bad a fix doesn't seem to be included in 4.16.1. I myself got this on RX 580 (but on old FX-6100 / PCI-e v.2 system), wasn't able to revert commit above and just resorted to disabling DC with amdgpu.dc=0 boot option.
Still exist for me on kernel 4.16.2 but I have less randome flickering than kernel 4.16/4.16.1 ...
Rx560 - 4Go
Okay the AMD devs reverted the corresponding commit in amd-staging-drm-next (https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-next&id=fc0644eddd2d5f77aac44ad2ab5a3edae08d11c2). I rebuild and tested them (https://github.com/M-Bab/linux-kernel-amdgpu-binaries) and can confirm the issue is fixed for now.
Thanks for testing, Martin. This doesn't appear to be included in 4.16.3 looking at https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.3 and Arch just bumped the kernel from 4.15 to 4.16.3 so I'm holding back updating.
Are we likely to see this included in 4.16.4?
The revert is cc'ed to stable so it will show up in the 4.16 stable tree as well.
Thank you, Alex!
Flickering seems to be gone on 4.17rc2!
However, there's a new issue :/
I experienced the flicker on 4.16.3 & I had to use amdgpu.dc=0 to suppress the flicker (but it also disabled audio over HDMI) on my RX 560.
The flicker seems to be gone on 4.16.4 for me (amdgpu.dc=0 was also removed), and audio over HDMI is working too.
Kevin, can you mark this as resolved?
I can also confirm the flicker is gone with 4.17rc2
It looks like this commit has made it into 4.16.4