Random screen flickering on dual monitors 1440p with Radeon 5700 at startup

Hi, everyone.
I saw the screen flickering at PC startup rarely random times. I have to restart PC, then the flicker is gone. But not always stable, sometimes the issue rarely occurs when starting the PC only. Not screen tearing!

The screen flickering looks like other photo:

My radeon RX 5700 with dual same monitors 1440p via Displayport, using Linux Kernel 5.10 and default amdgpu driver.

journalctl -b -p 3
Output:

Jul 25 20:25:42 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: failed send message: NumOfDisplays (64)         param: 0x00000002 response 0xffffffc2
Jul 25 20:25:44 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Jul 25 20:25:44 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Failed to power gate JPEG!
Jul 25 20:25:44 zesko kernel: [drm:jpeg_v2_0_set_powergating_state [amdgpu]] *ERROR* Dpm disable jpeg failed, ret = -62. 
Jul 25 20:25:46 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Jul 25 20:25:46 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Failed to power gate VCN!
Jul 25 20:25:46 zesko kernel: [drm:amdgpu_dpm_enable_uvd [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62. 
Jul 25 20:25:49 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Jul 25 20:25:51 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
...

After logout then login then journalctl -b -p 3:

Jul 26 20:26:53 zesko kernel: amdgpu 0000:0b:00.0: amdgpu: failed send message: SetHardMinByFreq (28)         param: 0x0002036b response 0xffffffc2

PC system: inxi -Fx

System:    Host: zesko Kernel: 5.10.52-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 Desktop: KDE Plasma 5.22.3 
           Distro: Manjaro Linux base: Arch Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x serial: <superuser required> 
           BIOS: American Megatrends v: 3202 date: 06/16/2021 
CPU:       Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86424 
           Speed: 2749 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2749 2: 2094 3: 2200 4: 2200 5: 2189 
           6: 2199 7: 2199 8: 2196 9: 2396 10: 2127 11: 2129 12: 2198 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Tul 
           driver: amdgpu v: kernel bus-ID: 0b:00.0 
           Device-2: Microdia Dual Mode Camera (8006 VGA) type: USB driver: hid-generic,usbhid bus-ID: 1-10:4 
           Device-3: Realtek WEB CAMERA M9 Pro type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2:2 
           Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: modesetting,radeon resolution: 
           1: 2560x1440~60Hz 2: 2560x1440 
           OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 5.10.52-1-MANJARO LLVM 12.0.1) v: 4.6 Mesa 21.1.5 
           direct render: Yes 
...

Sorry for my bad English.

Does anybody have the same issue?

Disable the display power management (DPM):
For GRUB:

  • Edit /etc/default/grub
  • Set kernel parameter amdgpu.dpm=0 in GRUB_CMDLINE_LINUX_DEFAULT
  • sudo update-grub
  • Restart PC, then no error in kernel log.

But no ideal solution.
I suspect this issue has to do with some DPM’s bug in kernel.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Two solutions:

  1. solution: Switch to GNOME, then no issue with amdgpu and dual monitors 1440p.
  2. solution: amdgpu in kernel and KDE SDDM must set the same screen resolution and refresh rate!
    How → Kernel mode setting - ArchWiki
    Change the config file /etc/default/grubGRUB_CMDLINE_LINUX_DEFAULT adds
    video=DP-1:2560x1440@60 video=DP-2_2560x1440@120
    It must match the display setting of KDE.

Edit:
—> The correct solution: <—
The RAM is faulty and has broken the whole system sometimes or accidentally at startup.
The faulty RAM must be removed from the system immediately! The issue is gone!
See below:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.