Flickering on dual screen setup, AMD GPU

Ask Fedora
, ,
1

Hi,

I’ve updated my F39 deployment yesterday and this issue started happening: https://youtu.be/05jNKrtGAyM

The flickering happens only on one screen. Does this ring a bell to anyone?
Meanwhile I rolled back to previous deployment.

2 Likes
2

Hi,

You don’t mention your amdgpu (or kernel) setup, but I have issues with kernel-6.8.4-100 in Fedora 38 with amdgpu on an Alienware m17 R5 AMD laptop (eDP 4K panel). Going back to kernel-6.7.11-100 seems to restore usability for me as well.

3

Yeah sorry about that. Tomorrow I’ll try again and gather the GPU/kernel informations.

4

This seems to be the culprit for me: kernel 6.7.10-200.fc39 → 6.8.4-200.fc39
Mesa version hasn’t changed (23.3.6-1.fc39) between both deployments.
My GPU is AMD Radeon RX 7700 XT (radeonsi, navi32)

2 Likes
5

Looks like a kernel regression then. Can you file a bug for the kernel in Fedora’s Bugzilla? Thanks

6

https://bugzilla.redhat.com/show_bug.cgi?id=2274331

2 Likes
7

I am seeing exactly the same thing under Fedora 40 with Gnome with a 7900 xt GPU. After switching to a 6.7 kernel the random flickering is gone.

I hope kernel 6.9 fixes this issue after it is released to the Fedora Repos.

8

Installed newest build of 6.9 from the koji buildsystem https://koji.fedoraproject.org/koji/buildinfo?buildID=2457165 and did not observe any flickering until now.

9

After last Updates of Mesa and libdrm stack i have seen flickering even on kernel 6.9.2.

No problems in games, it just happens in the transition in gnome when pressing the super key like in the video in the first post.

10

@philn The Problem still persists under Gnome and Kernel 6.9.9 for me. It seems to happen more often under a wayland session then under xorg. I first thought the problem ist gone after setting the performance level to high via lact gui, but it came back.

I now activated the experimental VRR under gnome and did not encounter the problem since then.

What is youre status on this bug?

11

Problem persists also with VRR enabled, seems totally random…

1 Like
12

This is also happening to me with two monitors, one 4k60 and one 1080p60. Notably, if I change the refresh rate of the 1080p60 monitor to 50hz the issue no longer occurs.

My system details report:

System Details Report

Report details

  • Date generated: 2024-08-08 19:19:04

Hardware Information:

  • Hardware Model: ASUS ROG STRIX B650E-F GAMING WIFI
  • Memory: 32.0 GiB
  • Processor: AMD Ryzen™ 9 7900X × 24
  • Graphics: AMD Radeon™ RX 7800 XT
  • Graphics 1: AMD Radeon™ Graphics
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: 3014
  • OS Name: Fedora Linux 40 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 46
  • Windowing System: Wayland
  • Kernel Version: Linux 6.9.12-200.fc40.x86_64
13

Changing the refresh rate on one monitor down to 60 hz nearly reduces the occurrence of artifacts nearly to 0, but it is not completely gone. I am just hoping that it will be fixed in the future …

14

Still happening,

External 2nd monitor, not in the primary monitor.
Fedora 40
Gnome 46
Kernel: 6.12.6-100.fc40.x86_64
AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
Lenovo ThinkPad P16v Gen 1

  • Attempted to decrease Refresh rater to 50Hz up to 74.99 (which matches the primary monitor), but didnt work.
  • Swap between Xorg/Wayland does not make any difference.
15

I ordinarily wouldn’t necro-bump, but I thought I’d note that I’ve been seeing the same behavior over the last couple of months, so the bug either still exists or has re-emerged. It’s always on the non-primary monitor, and usually appears after it wakes up from sleep. I’m running the kernel 6.16.12 amdgpu driver with KDE Plasma 6.5.2, KDE Frameworks 6.20.0, Qt 6.10.0, and Mesa 25.3.0, on a Radeon 6600XT GPU.

I’ve seen this at least four or five times, usually with the glitch in a horizontal band as shown in the video, and with repetitive patterns that make me think the driver has filled the framebuffer with unrelated data from somewhere else in memory. The flicker effect (with every other frame rendered apparently normally) suggests that only one of the buffers in a double-buffer scheme is affected. I also think KDE might have something to do with it, as I often get a kwin crash around the same time as or shortly after the screen corruption appears. I’ve only seen this happen on Wayland, because that’s what I’m in 98% of the time, but I have no reason not to believe it can happen on X11 too.

It happened most recently yesterday, starting with the typical horizontal corruption. A minute or so later kwin went bad, with my navigation/launcher bar and wallpaper disappearing and no right-click context menus on the desktop, although all applications kept running. Since I’m under Wayland, there’s no easy way to restart kwin to bring those back, but I didn’t want to close my apps yet so I kept using it and noticed a more interesting pattern: when I maximized an application on that secondary screen, the flickering went away. When I minimized it again, the flickering would return. When I reduced the window to smaller than full-screen size and dragged it around, the flickering would appear only in the “trail” behind the current window position. I noticed the same behavior with every application window: no corruption within the active drawing surface, but corruption could appear in a horizontal band behind them (i.e. plain desktop). Once again this was an every-other-frame flicker, suggesting only half of the double buffer was susceptible. I did not experience any graphical issues on the primary screen. Using the Display & Monitor control panel in the KDE System Settings to disable/reenable the secondary screen or to change its resolution or virtual desktop position did not resolve the corruption or flickering. I’m now 100% certain this is a software defect and not a hardware issue (otherwise why would drawing an application window clear the flicker effect on part of the screen?).