Skip to content
Snippets Groups Projects

Flickering coloured glitchyness on 780M Phoenix iGPU with 6.7.0 kernel on Xorg/plasma

    • Closed Issue created by George M. @sgmihai

    Before submitting your bug report:

    Brief summary of the problem:

    After upgrading to 6.7.0-lto on cachyOS, I get instant glitchy graphics (flickering raw texture type) when plasma desktop starts. Happens all the time. Switching to wayland session fixes this. Previously I had the problem of full white screen flickering, which was reported to happen with >=64GB RAM systems, and supposedly fixed, but I still needed to use kernel param amdgpu.sg_display=0 to fix this, even though the laptop only has 32GB. Now using this kernel param in 6.7.0 does not fix the new kind of glitchyness. Later EDIT: Starting a game (league of legends via wine) causes the corruption to happen even on wayland, where it flickers at a constant rate, not semi-random like in the desktop. Starting a native game (urtok: the desolation) doesn't cause any problems on wayland.

    Hardware description:

    • CPU: AMD Ryzen 7 7840U w/ Radeon 780M Graphics (16) @ 4,35 GHz

    • GPU: c2:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c9) product: Phoenix1 [1002:15BF] vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002] physical id: 0 bus info: pci@0000:c2:00.0 logical name: /dev/fb0 version: c9 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list fb configuration: depth=32 driver=amdgpu latency=0 resolution=3200,2000 resources: iomemory:800-7ff irq:48 memory:8000000000-800fffffff memory:90000000-901fffff ioport:1000(size=256) memory:90500000-9057ffff

    • System Memory: 32GiB

    • Display(s): (SDC418D): 3200x2000 @ 120Hz [Built-in]

    System information:

    • Distro name and Version: cachyOS
    • Kernel version: Linux cachyos-x8664 6.7.0-2-cachyos-lto
    • Custom kernel: N/A
    • AMD official driver version: N/A

    How to reproduce the issue:

    Just start plasma desktop

    Log files (for system lockups / game freezes / crashes)

    signal-2024-01-09-233312_002

    signal-2024-01-09-233312_004

    signal-2024-01-09-233312_005

    Edited

    Designs

      Child items 0

      2. No child items are currently assigned. Use child items to break down this issue into smaller parts.

      Activity

      • George M. changed the description

        changed the description

      • Alex Deucher added Phoenix label

        added Phoenix label

      • Alex Deucher
        Alex Deucher @agd5f ·
        Owner

        Please attach your logs to the report rather than providing links to external sites. Also, can you attach a picture or a video of the corruption?

      • George M. changed the description

        changed the description

      • George M.
        George M. @sgmihai ·
        Author

        I attached some pictures of the corruption, but won't edit much more, as I have to solve captchas every time.

      • George M. changed the description

        changed the description

      • Chris Sutcliff
        Chris Sutcliff @csutcliff ·

        Same issue here with an Acer SFE16-43 (7840u based but only 16GB RAM). 6.6 works well with the amdgpu.sg_display=0 setting, 6.7 has this behaviour.

        For me a few minutes after the launch/corruption happens the screen goes completely black and unresponsive, audio continues and it responds over the network. I will try and update with some logs etc when I get home this evening.

      • Alex Deucher
        Alex Deucher @agd5f ·
        Owner

        Does setting amdgpu.agp=1 help?

      • Chris Sutcliff
        Chris Sutcliff @csutcliff ·

        with amdgpu.agp=1 I get a brief flash of the corruption and then straight to a black screen so the same end result but it happens in <1sec instead of a minute.

      • George M.
        George M. @sgmihai ·
        Author

        Did some more testing with the kernel params, all tests done at native 3200 x 2000 @ 120hz. game = league of legends via wine

        agp=1, sg=1: xorg - corruption as usual, mixed with some full white screen during the flickers wayland - desktop good, game works fine in windowed mode, but in full screen there's just a solid white image with game cursor visible dmesg log in wayland after starting game: https://pastebin.com/raw/jTpKcVeg

        agp=0, sg=0: xorg - corruption as usual wayland - desktop good, but black screen when i start the game dmesg log in wayland after starting the game (via ssh): https://pastebin.com/raw/FJXHywpJ xorg log (in xorg): https://pastebin.com/raw/cRKdeRUL

        agp=1, sg=0: xorg - screen turns black immediately after some corruption is visible wayland - desktop good, game runs fine in window, but corruption when in full screen dmesg in wayland has just this as last relevant line : [ 152.791595] amdgpu 0000:c2:00.0: Using 44-bit DMA addresses xorg log: https://pastebin.com/raw/QtVD62qs dmesg log (when running xorg): https://pastebin.com/raw/rL0FkFzp

        Could it be that it's something acer specific (maybe bios?) related to this model ? As I haven't seen any reports of the white screen bug after it was previously fixed (for >=64GB RAM devices)

      • Chris Sutcliff
        Chris Sutcliff @csutcliff ·

        I was going to bisect this but in starting to do so I discovered that it is not an issue with a vanilla v6.7.0 kernel.

        It's actually an issue with the amd-hdr patchset that is being used by the cachyos kernel, when combined with 6.7.

        I think the issue can be closed.

        Edit: Spoke too soon, it happens less quickly without that patch but it still occurs. I've bisected it to 27442758e9b4e083bef3f164a1739475c01f3202. Currently working out how I narrow it down from that big squashed commit.

        Edited by Chris Sutcliff
        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          @agd5f I tried unsucessfully to bisect this on your repo that was the source of the big pull in the main linux repo, unfortunately nothing I built from there would boot to a graphical state. Do you have any tips for narrowing this down? Is there a proper procedure for bisecting these big pulls?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          One suggestion is to take the tags between pull requests from https://gitlab.freedesktop.org/agd5f/linux/-/commits/amd-staging-drm-next and bisect between those two. I think you would want to try between amd-drm-fixes-6.6-2023-10-11 and -drm-next-6.7-2023-10-13 potentially.

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          Yeah that's what I thought, Unfortunately I can't get a kernel built from either of those tags to boot, let alone bisect between.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          That's weird you can't boot those tags. Those are pretty much what QA teams test on. What's happening when you try?

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          Sorry "doesn't boot" is not really correct. I get the usual systemd boot stuff but then the display freezes at "Reached target Graphical Interface". Everything works over SSH but no login manager appears and I can't even change TTY on the screen to get to a console.

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          I started fresh to see if I had introduced some error in the process. Got a bit further but now stuck on a new issue.

          I've built from agd5f/linux amd-drm-fixes-6.6-2023-10-11 tag which works correctly now.

          When I start bisecting with amd-drm-next-6.7-2023-10-13 weirdly the kernel version that gets built is actually lower. 6.5.0-rc7 and so far all 3 commits I've tried (skipping on failure) have been unable to load the amdgpu module.

          On boot the following is in dmesg:

          dmesg 
          [    2.458181] ------------[ cut here ]------------
[    2.458185] WARNING: CPU: 15 PID: 325 at mm/page_alloc.c:4453 __alloc_pages+0x341/0x350
[    2.458191] Modules linked in: i2c_algo_bit iwlmvm(+) videobuf2_vmalloc snd_hda_codec drm_ttm_helper snd_pci_ps videobuf2_memops ttm snd_hwdep snd_rpl_pci_acp6x uvc drm_exec videobuf2_v4l2 intel_rapl_msr snd_acp_pci drm_suballoc_helper snd_hda_core intel_rapl_common snd_pci_acp6x mac80211 amdxcp videodev snd_pcm drm_buddy snd_pci_acp5x kvm_amd videobuf2_common gpu_sched snd_rn_pci_acp3x snd_timer snd_acp_config libarc4 usbhid mc drm_display_helper snd snd_soc_acpi ccp kvm cec soundcore snd_pci_acp3x acer_wmi iwlwifi btusb sparse_keymap irqbypass btrtl btbcm wmi_bmof ucsi_acpi video rapl btintel cfg80211 typec_ucsi pcspkr thunderbolt(+) btmtk roles k10temp i2c_piix4 acer_wireless typec wmi joydev amd_pmc mousedev bluetooth mac_hid crc16 lz4 ecdh_generic lz4_compress rfkill winesync(OE) ryzen_smu(OE) pkcs8_key_parser i2c_dev corefreqk(OE) sg crypto_user loop fuse dm_mod nfnetlink zram ip_tables x_tables btrfs libcrc32c raid6_pq crc32c_generic sha256_ssse3 xor aesni_intel atkbd vivaldi_fmap serio_raw libps2
[    2.458251]  polyval_clmulni i8042 crypto_simd xhci_pci ghash_clmulni_intel hid_multitouch nvme polyval_generic sha512_ssse3 cryptd crc32_pclmul crc32c_intel gf128mul crct10dif_pclmul xhci_pci_renesas nvme_core serio i2c_hid_acpi i2c_hid
[    2.458264] CPU: 15 PID: 325 Comm: (udev-worker) Tainted: G           OE      6.5.0-rc7-1-git-g35588314e963 #1 167039ad6ee29d549dd65a77dc58880fad141fc7
[    2.458266] Hardware name: Acer Swift SFE16-43/Ray_PEU, BIOS V1.54 09/07/2023
[    2.458268] RIP: 0010:__alloc_pages+0x341/0x350
[    2.458270] Code: 89 ee 89 df c6 44 24 20 00 4c 89 64 24 08 41 89 de e8 33 ef ff ff 49 89 c5 e9 7a fe ff ff 80 e3 3f eb c0 c6 05 c4 95 c5 01 01 <0f> 0b eb 98 e8 c6 66 9d 00 66 0f 1f 44 00 00 90 90 90 90 90 90 90
[    2.458271] RSP: 0018:ffffb5928557fc08 EFLAGS: 00010246
[    2.458273] RAX: 0000000000000000 RBX: 0000000000040cc0 RCX: 0000000000000000
[    2.458274] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000040cc0
[    2.458275] RBP: 000000000000000c R08: 0000000000000006 R09: 0000000000000006
[    2.458276] R10: ffffef2c44a01a08 R11: 0000000000000000 R12: 0000000000000000
[    2.458277] R13: ffffffff8817ba27 R14: ffff8b5544645a00 R15: ffff8b554db83790
[    2.458278] FS:  00007fc044022e00(0000) GS:ffff8b58ae9c0000(0000) knlGS:0000000000000000
[    2.458279] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.458280] CR2: 0000556535936168 CR3: 0000000114f42000 CR4: 0000000000750ee0
[    2.458281] PKRU: 55555554
[    2.458282] Call Trace:
[    2.458284]  <TASK>
[    2.458285]  ? __alloc_pages+0x341/0x350
[    2.458287]  ? __warn+0x81/0x130
[    2.458291]  ? __alloc_pages+0x341/0x350
[    2.458293]  ? report_bug+0x171/0x1a0
[    2.458297]  ? handle_bug+0x3c/0x80
[    2.458300]  ? exc_invalid_op+0x17/0x70
[    2.458302]  ? asm_exc_invalid_op+0x1a/0x20
[    2.458305]  ? module_decompress+0x107/0x310
[    2.458309]  ? __alloc_pages+0x341/0x350
[    2.458311]  ? mod_lruvec_page_state.constprop.0+0x1c/0x30
[    2.458315]  ? module_decompress+0x107/0x310
[    2.458316]  __kmalloc_large_node+0x73/0x130
[    2.458319]  __kmalloc+0xc3/0x150
[    2.458321]  module_decompress+0x107/0x310
[    2.458324]  init_module_from_file+0xb4/0xe0
[    2.458330]  idempotent_init_module+0x120/0x2b0
[    2.458334]  __x64_sys_finit_module+0x5e/0xb0
[    2.458336]  do_syscall_64+0x5d/0x90
[    2.458339]  ? srso_alias_return_thunk+0x5/0x7f
[    2.458342]  ? syscall_exit_to_user_mode+0x2b/0x40
[    2.458344]  ? srso_alias_return_thunk+0x5/0x7f
[    2.458345]  ? do_syscall_64+0x6c/0x90
[    2.458347]  ? syscall_exit_to_user_mode+0x2b/0x40
[    2.458348]  ? srso_alias_return_thunk+0x5/0x7f
[    2.458349]  ? do_syscall_64+0x6c/0x90
[    2.458351]  ? srso_alias_return_thunk+0x5/0x7f
[    2.458352]  ? do_syscall_64+0x6c/0x90
[    2.458354]  ? srso_alias_return_thunk+0x5/0x7f
[    2.458355]  ? do_syscall_64+0x6c/0x90
[    2.458356]  ? do_syscall_64+0x6c/0x90
[    2.458358]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[    2.458361] RIP: 0033:0x7fc043931d5d
[    2.458383] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 9b 3f 0d 00 f7 d8 64 89 01 48
[    2.458384] RSP: 002b:00007ffd6a31aef8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    2.458386] RAX: ffffffffffffffda RBX: 00005581f663ca90 RCX: 00007fc043931d5d
[    2.458387] RDX: 0000000000000004 RSI: 00005581f663b180 RDI: 000000000000001b
[    2.458388] RBP: 00005581f663b180 R08: fffffffffffffec0 R09: 00005581f652f40f
[    2.458389] R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000020000
[    2.458389] R13: 00005581f6636c60 R14: 00005581f663ccd0 R15: 00005581f663cc30
[    2.458393]  </TASK>
[    2.458393] ---[ end trace 0000000000000000 ]---

          and attempting to modprobe amdgpu results in modprobe: ERROR: could not insert 'amdgpu': Cannot allocate memory

          Edit: amd-drm-next-6.7-2023-10-13 tag has the same issue for me, can't load the amdgpu module and mm error in dmesg

          Edited by Chris Sutcliff
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I start bisecting with amd-drm-next-6.7-2023-10-13 weirdly the kernel version that gets built is actually lower. 6.5.0-rc7

          Ah... they don't take a common base I guess because 6.6 was based off drm-fixes for 6.6 at that time.

          and attempting to modprobe amdgpu results in modprobe: ERROR: could not insert 'amdgpu': Cannot allocate memory

          As another idea - can you reproduce the issue directly on the branch amd-staging-drm-next? If so, maybe a direct bisect from a commit around September as a starting point and HEAD as an ending point?

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          amd-staging-drm-next (still 6.5.0-rc7) has the same issue, mm error and can't load amdgpu.

          I can build the drm-fixes-6.8 (based off of a 6.7.0-rc version) branch which does boot and have the amdgpu module loaded and working but the screen freezes shortly after, needing magic sysrq key to restart so I haven't been able to test this issue on it.

          It appears to me that every build that is based on 6.5.0-rc7 has the same issue with mm and loading the module.

          Edited by Chris Sutcliff
        • Please register or sign in to reply
      • Rohit Sukumaran
        Rohit Sukumaran @roku8 ·

        I have this issue on KDE Wayland on Arch Linux as well. Everything works for a while but eventually the display is overrun with noise. Initially there is some very brief noise when making applications fullscreen as well. I had a look at the dmesg logs via journalctl --boot after using the lts kernel but there are no drm/amdgpu logs or stacktraces when this happens.

        I have amdgpu.dcdebugmask=0x10 amdgpu.sg_display=0 in kernel cmdline. The issue is present even when I remove these flags in any permutation.

        Edited by Rohit Sukumaran
      • George M.
        George M. @sgmihai ·
        Author

        Can you share the hardware you hae @roku8 ?

      • Rohit Sukumaran
        Rohit Sukumaran @roku8 ·
        • Device: HP Pavilion Plus 14
        • CPU: AMD Ryzen 7840U @ 5.132 GHz
        • GPU: Radeon 780M
        • Memory: 16GB LPDDR5x @ 6400MHz
        • Display: 2880x1800 @ 120Hz
        • OS: Arch Linux
        • DE: KDE Wayland (5.27.10)
        Edited by Rohit Sukumaran
        • Mark Herbert
          Mark Herbert @mark.herbert42 ·

          Try export variable AMD_DEBUG='nodisplaydcc useaco'

          For me that helped with some artifacts on Xorg based session (not KDE).

        • George M.
          George M. @sgmihai ·
          Author

          I put that in /etc/environment, and the corruption is reduced, most of screen is clear, only two bars on top and bottom that flicker, but text in plasma is not visible in some places (menus, notifications). With Xorg. So it's not a fix.

          Edited by George M.
        • Please register or sign in to reply
      • George M. changed title from Flickering coloured glitchyness on 780M Phonix igpu with 6.7.0 kernel on xorg/plasma to Flickering coloured glitchyness on 780M Phoenix igpu with 6.7.0 kernel on xorg/plasma

        changed title from Flickering coloured glitchyness on 780M Phonix igpu with 6.7.0 kernel on xorg/plasma to Flickering coloured glitchyness on 780M Phoenix igpu with 6.7.0 kernel on xorg/plasma

      • George M. changed title from Flickering coloured glitchyness on 780M Phoenix igpu with 6.7.0 kernel on xorg/plasma to Flickering coloured glitchyness on 780M Phoenix iGPU with 6.7.0 kernel on Xorg/plasma

        changed title from Flickering coloured glitchyness on 780M Phoenix igpu with 6.7.0 kernel on xorg/plasma to Flickering coloured glitchyness on 780M Phoenix iGPU with 6.7.0 kernel on Xorg/plasma

      • Mario Limonciello mentioned in issue #2812 (closed)

        mentioned in issue #2812 (closed)

        • Marcus A
          Marcus A @oxar ·

          I've same issue, but it seems related to the firmware and not the kernel version. I got way more glitches and distortions recently, I also thought that the 6.7.0 update was the reason, but booting with previous 6.6 kernel the issue persisted. I downgraded linux-firmware package (Arch) and the problem is now gone. I have this issue on GNOME Wayland. Not as bad as KDE Plasma but on animations it shows distortions.

          Could someone from AMD acknowledge that could be a firmware issue? Or could tell me how to debug this?

          Edited by Marcus A
        • Rohit Sukumaran
          Rohit Sukumaran @roku8 ·

          I have no problem running 6.6.13-lts kernel with latest firmware on Arch. This only occurs on the 6.7.x kernel. Updated to 6.7.1 recently and still have the same problem (although it seems to take longer for the glitching noise to start).

          For reference the firmware version I am on is linux-firmware 20240115.9b6d0b08-1.

          Will try out your suggestion and downgrade the firmware package to see if it makes a difference. But why does latest firmware work with lts kernel and not mainline?

        • Rohit Sukumaran
          Rohit Sukumaran @roku8 ·

          @oxar You are right. Downgrading the firmware to linux-firmware 20231211.f2e52a1c-1 worked.

          Edited by Rohit Sukumaran
        • Cicada17
          Cicada17 @CicadaSeventeen ·

          debian firmware 20230625-2, problem still exists.

        • Please register or sign in to reply
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Could someone from AMD acknowledge that could be a firmware issue?

          Sure it sounds plausible. That might explain why internal AMD team has not been able to reproduce this on the reference hardware (I asked them to). Please capture the specifics of the firmware in use right now:

          # cat /sys/kernel/debug/dri/*/amdgpu_firmware_info

          Then everyone else affected, please compare.

          Or could tell me how to debug this?

          There's a bunch of new firmware for various devices that was just upstreamed in the past few days. Can you pull the update to that and see if it goes away? If it does; please post those versions as well.

        • Marcus A
          Marcus A @oxar ·

          Working firmware (dec 2023) firmware-dec-2023-working.txt Problematic firmware (jan 2024)firmware-jan-2024-glitches.txt

          diff

          27c27
< DMCUB feature version: 0, firmware version: 0x08002a81
---
> DMCUB feature version: 0, firmware version: 0x08003000
59c59
< DMCUB feature version: 0, firmware version: 0x08002a81
---
> DMCUB feature version: 0, firmware version: 0x08003000
91c91
< DMCUB feature version: 0, firmware version: 0x08002a81
---
> DMCUB feature version: 0, firmware version: 0x08003000
        • Marcus A
          Marcus A @oxar ·

          There's a bunch of new firmware for various devices that was just upstreamed in the past few days. Can you pull the update to that and see if it goes away? If it does; please post those versions as well.

          Did update from upstream (only amdgpu) but didn't fix it (for me). Here are the firmware versions loaded from upstream upstream.txt

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          OK that's really helpful. Here's the decoder to it.

          January (broken) is this commit: firmware@4d8afe32 This maps to AMD internal commit 8e9a9e065ee5ccb0b03d6c31d94058a94674faac.

          December (working is this commit: firmware@87be457c This maps to AMD internal commit de8f5fc265f36ea91c2dd7c277d814dab7cfb437

          So if you revert just the DMCUB binary (dcn_3_1_4_dmcub.bin) and keep everything else the same everything is OK?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          CC @charliewang

        • Marcus A
          Marcus A @oxar ·

          So if you revert just the DMCUB binary (dcn_3_1_4_dmcub.bin) and keep everything else the same everything is OK?

          It's working now, I downgraded the firmware package (arch version 20231211.f2e52a1c-1), took out dcn_3_1_4_dmcub.bin.zst, upgraded firmware package (arch version 20240115.9b6d0b08-1) and copied dcn_3_1_4_dmcub.bin.zst back. And no artifacts for me. Here is the versions listdowngrade-dmcub.txt Running on 6.7.1-arch1-1

          Edited by Marcus A
        • Please register or sign in to reply
      • Mario Limonciello added DC label

        added DC label

      • y61759h y61759h mentioned in issue #3133 (closed)

        mentioned in issue #3133 (closed)

      • Chris Bainbridge mentioned in issue #3058

        mentioned in issue #3058

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I am afraid we have multiple issues conflated here in this bug. I think the issue @oxar sees and the @sgmihai originally reported are not the same root cause, although it sounds they look similar.

          @CicadaSeventeen Does your issue go away in LTS 6.6.y kernel? If so; can you please bisect the issue from 6.6 to 6.7?

        • Cicada17
          Cicada17 @CicadaSeventeen ·

          I do not find any similar problem in 6.6 kernel. However, even under 6.7 this problem is a rare bug, so it needs to take me lots of time to find out the situation.

        • Please register or sign in to reply
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I've reproduced what I believe is the same issue as the one reported here. There's a few comments that made it seem to be caused by the DMUB update, but actually it's kernel commits that tripped it. DMUB update is just coincidental.

          You can try reverting these 3 commits:

          9ae587f850a6 ("drm/amdgpu: Fix the vram base start address")
2eb412aa25ed ("drm/amdgpu: Move the size computations to drm buddy")
0a1844bf0b53 ("drm/buddy: Improve contiguous memory allocation")

          If that helps, it's the same as I saw. @arunpravin24 is currently working on a solution for it.

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          Reverting those three commits on top of drm-fixes-6.7 doesn't build for me.

          They are also all newer than the amd-drm-next-6.7-2023-10-13 tag that I was able to bisect this to so no chance of reverting them there as they didn't exist at that point.

          Edited by Chris Sutcliff
        • Trolli Schmittlauch
          Trolli Schmittlauch @schmittlauch ·

          Yes, unfortunately applying these 3 patch reverts on top of kernel 6.7.2 results in a linkin failure for amdgpu.o:

          […]
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes.o
  CC [M]  drivers/iio/adc/ti-adc108s102.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxi-6030e.o
  CC [M]  drivers/iio/temperature/tmp006.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6070e.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6220.o
  CC [M]  drivers/iio/light/si1133.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6221.o
  CC [M]  drivers/iio/adc/ti-adc128s052.o
  CC [M]  drivers/iio/light/si1145.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxi-6224.o
  CC [M]  drivers/iio/light/stk3310.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxi-6225.o
  CC [M]  drivers/iio/pressure/ms5611_spi.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6229.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6251.o
  CC [M]  drivers/iio/temperature/tmp007.o
  CC [M]  drivers/iio/pressure/ms5637.o
  CC [M]  drivers/iio/adc/ti-adc161s626.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxi-6251.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/hwss/link_hwss_dpia.o
  CC [M]  drivers/iio/temperature/tmp117.o
  CC [M]  drivers/iio/adc/ti-ads1015.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxie-6251.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6254.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6259.o
  CC [M]  drivers/iio/temperature/tsys01.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/hwss/link_hwss_hpo_dp.o
  CC [M]  drivers/iio/adc/ti-ads1100.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6534.o
  CC [M]  drivers/iio/light/st_uvis25_core.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxie-6535.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6602.o
  CC [M]  drivers/iio/light/st_uvis25_i2c.o
  CC [M]  drivers/iio/pressure/st_pressure_core.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/hwss/link_hwss_dio_fixed_vs_pe_retimer.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6713.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6723.o
  CC [M]  drivers/iio/temperature/tsys02d.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pci-6733.o
  CC [M]  drivers/iio/adc/ti-ads7924.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxi-6733.o
  CC [M]  drivers/iio/pressure/st_pressure_buffer.o
  CC [M]  drivers/comedi/drivers/ni_routing/ni_device_routes/pxie-6738.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/hwss/link_hwss_hpo_fixed_vs_pe_retimer_dp.o
  CC [M]  drivers/comedi/drivers/ni_labpc_common.o
  CC [M]  drivers/iio/light/st_uvis25_spi.o
  CC [M]  drivers/iio/adc/ti-ads7950.o
  CC [M]  drivers/comedi/drivers/comedi_8255.o
  CC [M]  drivers/iio/light/tcs3414.o
  CC [M]  drivers/iio/pressure/t5403.o
  CC [M]  drivers/iio/pressure/hp206c.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_hpd.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_ddc.o
  CC [M]  drivers/comedi/drivers/8255.o
  CC [M]  drivers/iio/adc/ti-ads8344.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dpcd.o
  CC [M]  drivers/comedi/drivers/amplc_dio200_common.o
  CC [M]  drivers/iio/pressure/zpa2326.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_dpia.o
  CC [M]  drivers/iio/light/tcs3472.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training_8b_10b.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training_128b_132b.o
  CC [M]  drivers/iio/pressure/zpa2326_i2c.o
  CC [M]  drivers/iio/adc/ti-ads8688.o
  CC [M]  drivers/comedi/drivers/amplc_pc236_common.o
  CC [M]  drivers/iio/light/tsl2563.o
  CC [M]  drivers/iio/adc/ti-ads124s08.o
  CC [M]  drivers/comedi/drivers/das08.o
  CC [M]  drivers/iio/light/tsl2583.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training_dpia.o
  CC [M]  drivers/iio/pressure/zpa2326_spi.o
  CC [M]  drivers/iio/adc/ti-ads131e08.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training_auxless.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_training_fixed_vs_pe_retimer.o
  CC [M]  drivers/iio/light/tsl2591.o
  CC [M]  drivers/iio/light/tsl2772.o
  CC [M]  drivers/iio/adc/ti_am335x_adc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_phy.o
  CC [M]  drivers/iio/light/tsl4531.o
  CC [M]  drivers/iio/pressure/st_pressure_i2c.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_capability.o
  CC [M]  drivers/iio/pressure/st_pressure_spi.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_edp_panel_control.o
  CC [M]  drivers/iio/light/us5182d.o
  CC [M]  drivers/iio/adc/ti-lmp92064.o
  CC [M]  drivers/comedi/drivers/tests/comedi_example_test.o
  LD [M]  drivers/comedi/drivers/ni_routing.o
  CC [M]  drivers/iio/light/vcnl4000.o
  CC [M]  drivers/comedi/drivers/tests/ni_routes_test.o
  CC [M]  drivers/iio/light/vcnl4035.o
  CC [M]  drivers/iio/adc/ti-tlc4541.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_irq_handler.o
  CC [M]  drivers/iio/light/veml6030.o
  CC [M]  drivers/iio/light/veml6070.o
  CC [M]  drivers/iio/adc/ti-tsc2046.o
  CC [M]  drivers/iio/light/vl6180.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/link/protocols/link_dp_dpia_bw.o
  CC [M]  drivers/iio/adc/vf610_adc.o
  LD [M]  drivers/iio/pressure/bmp280.o
  LD [M]  drivers/iio/pressure/st_pressure.o
  CC [M]  drivers/iio/light/zopt2201.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/virtual/virtual_link_encoder.o
  CC [M]  drivers/iio/adc/viperboard_adc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/virtual/virtual_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/virtual/virtual_link_hwss.o
  CC [M]  drivers/iio/adc/xilinx-xadc-core.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.o
  CC [M]  drivers/iio/adc/xilinx-xadc-events.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/rc_calc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/rc_calc_dpi.o
  CC [M]  drivers/iio/adc/sd_adc_modulator.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_ipp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer_debug.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_opp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_mpc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_dpp_dscl.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_dpp_cm.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dpp_cm.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hubp.o
  LD [M]  drivers/iio/adc/xilinx-xadc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_mpc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_opp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_mmhubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_vmid.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dwb.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dwb_scl.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dsc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_mpc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_opp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn201/dcn201_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_mpc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_vpg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_afmt.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dio_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dwb.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dpp_cm.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dwb_cm.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_mmhubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_panel_cntl.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn301/dcn301_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn302/dcn302_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn302/dcn302_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn303/dcn303_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn303/dcn303_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_panel_cntl.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_apg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_hpo_dp_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_hpo_dp_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_afmt.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_vpg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn314/dcn314_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn314/dcn314_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn314/dcn314_dio_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn314/dcn314_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn314/dcn314_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn315/dcn315_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn316/dcn316_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_mmhubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_dio_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_hpo_dp_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_resource_helpers.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn32/dcn32_mpc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn321/dcn321_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn321/dcn321_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_init.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dio_stream_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dio_link_encoder.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dccg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_optc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dsc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_hubp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_hubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_mmhubbub.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_opp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dpp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_pg_cntl.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn35/dcn35_dwb.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_core.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/display_mode_util.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_wrapper.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_utils.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_policy.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_translation_helper.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_dc_resource_mgmt.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml2_mall_phantom.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dml2/dml_display_rq_dlg_calc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_compressor.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_compressor.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_regamma_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_csc_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_mem_input_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_opp_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_transform_v.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce100/dce100_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce80/dce80_timing_generator.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce80/dce80_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_timing_generator.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_hw_sequencer.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/hdcp/hdcp_msg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stat.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_hw_sequencer.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_sink.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_surface.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_debug.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_enc_cfg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_exports.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_vm_helper.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dc_dmub_srv.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dc/dc_edid_parser.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/freesync/freesync.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_gamma.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/color/color_table.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/info_packet/info_packet.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/power/power_helpers.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv_stat.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_reg.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn20.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn21.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn30.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn301.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn302.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn303.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn31.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn314.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn315.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn316.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn32.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn35.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp_ddc.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp_log.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp_psp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp1_execution.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp1_transition.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp2_execution.o
  CC [M]  drivers/gpu/drm/amd/amdgpu/../display/modules/hdcp/hdcp2_transition.o
  LD [M]  drivers/gpu/drm/amd/amdgpu/amdgpu.o
make[4]: *** [../scripts/Makefile.build:480: drivers/gpu/drm] Error 2
make[3]: *** [../scripts/Makefile.build:480: drivers/gpu] Error 2
make[2]: *** [../scripts/Makefile.build:480: drivers] Error 2
make[1]: *** [/build/linux-6.7.2/Makefile:1911: .] Error 2
make: *** [../Makefile:234: __sub-make] Error 2
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I did them on 6.8-rc2. I found a problem compiling i915 so I disabled it in my config for now.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          They are also all newer than the amd-drm-next-6.7-2023-10-13 tag that I was able to bisect this to so no chance of reverting them there as they didn't exist at that point.

          I think they came in through drm-misc.

        • arunpravin24
          arunpravin24 @arunpravin24 ·
          Developer

          @csutcliff @superm1 I couldn't reproduce this issue in the latest drm-misc-next on the PHX system. Could you please let me know which branch has this problem?

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I reproduced on 6.8-rc2

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          My reproduce was specifically turning on / off abm a number of times, doing a modeset and then shortly after moving the mouse would sometimes trip it.

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          For me it affects anything since 27442758e9b4e083bef3f164a1739475c01f3202. Tested up to 6.8-rc2.

          I reproduce by launching any game. native, wine, proton doesn't seem to matter.

        • Trolli Schmittlauch
          Trolli Schmittlauch @schmittlauch ·

          I yet again tried the 3 reverts on top of 6.8-rc2, unfortunately linking still fails the same way as before.

          edit: building the patched kernel now works, I updated my config snippet below.

          Just for documentation, this is my NixOS config for that attempt:

            boot.kernelPackages = pkgs.linuxPackagesFor (pkgs.linux_latest.override {
    argsOverride = rec {
      src = pkgs.fetchurl {
        url = "https://git.kernel.org/torvalds/t/linux-${version}.tar.gz";
        hash = "sha256-LiNkYsgTJby9MctxxLWKUhsH1hNnGRJNDjyv+FwsXXU=";
      };
      version = "6.8-rc2";
      modDirVersion = "6.8.0-rc2";
    };
  });
  boot.kernelPatches = [
    {name = "revert 9ae587f850a6702428273fcf4a2a9b392349b2a3";
     patch = (pkgs.fetchpatch {
        url = "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=9ae587f850a6702428273fcf4a2a9b392349b2a3";
        hash = "sha256-5Uu8zxRSQuqE8oymjwPMt/ylsItpkQVDhbrOSMj8g3I=";
        revert = true;
    });}
    {name = "revert 2eb412aa25ed2bf59f5ad5f7a09787d182d67934";
     patch = (pkgs.fetchpatch {
        url = "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=2eb412aa25ed2bf59f5ad5f7a09787d182d67934";
        hash = "sha256-VtsH6bmwaLxPZ+uXvVE6qVWD2/aIKf9GLuMTNKq6d8M=";
        revert = true;
    });}
    {name = "revert 0a1844bf0b532d84324453374ad6845f64066c28";
     patch = (pkgs.fetchpatch {
        url = "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=0a1844bf0b532d84324453374ad6845f64066c28";
        hash = "sha256-Zd2pcYiOmuuzcc7THNtJW/YTjPyzO7HmQYKJNzy9YPw=";
        revert = true;
      });
     # alternatively, 8569c3154538 can be reverted as well
     extraStructuredConfig = with lib.kernel; {
       DRM_I915 = no;
       DRM_I915_GVT = lib.mkForce unset;
       DRM_I915_GVT_KVMGT = lib.mkForce unset;
     };
     }
    ];
          Edited by Trolli Schmittlauch
        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          I have the same amdgpu linking failure with those three commits reverted on 6.7.3 and 6.8-rc2

          Edited by Chris Sutcliff
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          I'm not sure why you guys are having a hard time with the linking. The only thing I had to do differently was turn off i915 from my kernel config and the reverts worked just fine on 6.8-rc2.

        • Kenny Levinsen
          Kenny Levinsen @kennylevinsen ·

          I don't think they're running into linker errors, but a compiler error beyond their scrollback.

          If you revert 0a1844bf0b53, you also need to revert:

          8569c3154538 ("drm/i915: Move the size computations to drm buddy")

          Otherwise i915 fails to compile as it references the reverted DRM_BUDDY_CONTIGUOUS_ALLOCATION.

          Edited by Kenny Levinsen
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Yup; like I said; I just turned off i915. This isn't an upstream ready solution; it's just to prove it's the right root cause.

        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          @kennylevinsen @superm1 You are both correct. I usually compile with localmodconfig so I was expecting that it was already disabled but localmodconfig wasn't enabled in the pkgbuild I put together for testing these git builds.

          Now that I've got it compiled it does appear that reverting these commits fixes the issue. Is the fix you mentioned that was in the works expected for 6.8?

          Edited by Chris Sutcliff
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Now that I've got it compiled it does appear that reverting these commits fixes the issue.

          @csutcliff OK good we're all on the same page.

          Is the fix you mentioned that was in the works expected for 6.8?

          Can you try drm-misc-next and confirm if you can see it there since @arunpravin24 couldn't?

          Edited by Mario Limonciello
        • Chris Sutcliff
          Chris Sutcliff @csutcliff ·

          I cannot reproduce this on drm-misc-next either so it looks like it is fixed there.

          Unrelated to this issue but I'll mention it anyway for anyone reading this as it was another issue affecting these laptops:

          amdgpu.sg_display=0 doesn't appear to be necessary on either 6.8 (tested rc3) or the drm-misc-next branch. on older kernels the screen would go white in full screen 3D applications unless S/G was disabled.

          Edited by Chris Sutcliff
        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          @arunpravin24 any idea what commit could have fixed in drm-misc-next? Maybe we need something else queued up for fixes instead.

        • arunpravin24
          arunpravin24 @arunpravin24 ·
          Developer

          Hi Mario, @superm1 I don't see any difference between drm-misc-next and 6.8-rc2. The commits are the same. I tried the following methods to reproduce the problem.

          1. Boot to Xorg/Plasma
          2. Played games on Steam. I couldn't observe the display corruption problem.

          As I am not able to reproduce the problem I am just guessing the below patch would have triggered the problem. 9ae587f850a6 ("drm/amdgpu: Fix the vram base start address") For our experiment, we can revert the above patch only and please apply the patch that optimizes the trim function in DRM buddy. I will upload the patch in a few minutes.

        • arunpravin24
          arunpravin24 @arunpravin24 ·
          Developer

          Please apply the attached patch on top of 6.8-rc2 and test the issue. 0001-drm-buddy-Improve-alloc_range-error-handling-routine.patch

          Note: Pls don't revert any patches. Just apply the above attached patch on top of 6.8

          Edited by arunpravin24
        • Jürg Billeter
          Jürg Billeter @juergbi ·

          I see this issue as well sometimes after resume from s2idle on a Rembrandt laptop (6850U PRO) with Linux 6.7.3, DMCUB firmware version 0x04000043, and Mesa 23.3.3. Reverting only 9ae587f850a6 ("drm/amdgpu: Fix the vram base start address") did not fix the issue for me but, after reverting all 3 commits, I haven't been able to reproduce the display corruption.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          @juergbi can you try with no reverts but using the patch Arun linked above?

        • Jürg Billeter
          Jürg Billeter @juergbi ·

          So far it's looking good with Linux 6.8-rc2 and Arun's patch (and the suspend fix). I've only been running it for a short while (with 3 suspend/resume cycles), though. Will keep this kernel running for now.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          @arunpravin24 works for me too in the case I could reproduce it. Here's a tag for when you submit it: Tested-by: Mario Limonciello <mario.limonciello@amd.com>

        • arunpravin24
          arunpravin24 @arunpravin24 ·
          Developer

          @superm1 Thank you. I will post the patch for the review.

        • Stefan Hoelzl
          Stefan Hoelzl @stefanhoelzl ·

          I also had flickering when changing the panel_power_savings value.

          This patch solved the issue for me.

          Tested on Fedora Silverblue 39 on a Framework 13 AMD 7840U with Kernel 6.7.4 (amdgpu.sg_display=0)

          Thanks for the patch!

          Edited by Stefan Hoelzl
        • Trolli Schmittlauch
          Trolli Schmittlauch @schmittlauch ·

          In contrast to what @csutcliff said, amdgpu.sg_display=0 is still necessary for me. Otherwise, the white flickering described in #2954 happens again after a while. I am on 6.8-rc2 with the patch by @arunpravin24.

          In the following log, the #2954-style flickering started after resuming the laptop and unfortunately was not resolved by suspending and resuming again:

          Feb 08 12:54:36 framenix kernel: Freezing user space processes
Feb 08 12:54:36 framenix kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Feb 08 12:54:36 framenix kernel: OOM killer disabled.
Feb 08 12:54:36 framenix kernel: Freezing remaining freezable tasks
Feb 08 12:54:36 framenix kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Feb 08 12:54:36 framenix kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 08 12:54:36 framenix kernel: queueing ieee80211 work while going to suspend
Feb 08 12:54:36 framenix kernel: ACPI: EC: interrupt blocked
Feb 08 12:54:36 framenix kernel: ACPI: EC: interrupt unblocked
Feb 08 12:54:36 framenix kernel: nvme nvme0: 16/0/0 default/read/poll queues
Feb 08 12:54:36 framenix kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Feb 08 12:54:36 framenix kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Feb 08 12:54:36 framenix kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Feb 08 12:54:36 framenix kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Feb 08 12:54:36 framenix kernel: [drm] ring gfx_32803.1.1 was added
Feb 08 12:54:36 framenix kernel: [drm] ring compute_32803.2.2 was added
Feb 08 12:54:36 framenix kernel: [drm] ring sdma_32803.3.3 was added
Feb 08 12:54:36 framenix kernel: [drm] ring gfx_32803.1.1 ib test pass
Feb 08 12:54:36 framenix kernel: [drm] ring compute_32803.2.2 ib test pass
Feb 08 12:54:36 framenix kernel: [drm] ring sdma_32803.3.3 ib test pass
Feb 08 12:54:36 framenix kernel: OOM killer enabled.
Feb 08 12:54:36 framenix kernel: Restarting tasks ... done.
Feb 08 12:54:36 framenix kernel: random: crng reseeded on system resumption
Feb 08 12:54:36 framenix systemd-logind[2106]: Lid opened.
Feb 08 12:54:36 framenix systemd-sleep[21096]: System returned from sleep state.
Feb 08 12:54:36 framenix kernel: PM: suspend exit
Feb 08 12:54:36 framenix bluetoothd[2052]: Controller resume with wake event 0x0
Feb 08 12:54:36 framenix systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 08 12:54:36 framenix systemd[1]: Finished System Suspend.
Feb 08 12:54:36 framenix systemd[1]: Stopped target Sleep.
Feb 08 12:54:36 framenix systemd[1]: Reached target Suspend.
Feb 08 12:54:36 framenix systemd-logind[2106]: Operation 'sleep' finished.
Feb 08 12:54:36 framenix kdeconnectd[3514]: Error sending UDP packet: QAbstractSocket::NetworkError
Feb 08 12:54:36 framenix systemd[1]: Starting Post-Resume Actions...
Feb 08 12:54:36 framenix systemd[1]: Stopped target Suspend.
Feb 08 12:54:36 framenix xserver-wrapper[2362]: (II) modeset(0): EDID vendor "BOE", prod id 3018
Feb 08 12:54:36 framenix xserver-wrapper[2362]: (II) modeset(0): Printing DDC gathered Modelines:
Feb 08 12:54:36 framenix xserver-wrapper[2362]: (II) modeset(0): Modeline "2256x1504"x0.0  235.69  2256 2304 2336 2536  1504 1507 1513 1549 +hsync -vsync (92.9 kHz eP)
Feb 08 12:54:36 framenix xserver-wrapper[2362]: (II) modeset(0): Modeline "2256x1504"x0.0  188.55  2256 2304 2336 2536  1504 1507 1513 1549 +hsync -vsync (74.3 kHz e)
Feb 08 12:54:36 framenix kernel: amd_iommu_report_page_fault: 7387 callbacks suppressed
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab270000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab271000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab272000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab273000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab274000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab275000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab276000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab277000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab278000 flags=0x0000]
Feb 08 12:54:36 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabc25000 flags=0x0000]
Feb 08 12:54:36 framenix plasmashell[3317]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Feb 08 12:54:36 framenix systemd[1]: post-resume.service: Deactivated successfully.
Feb 08 12:54:36 framenix systemd[1]: Finished Post-Resume Actions.
Feb 08 12:54:36 framenix systemd[1]: Reached target Post-Resume Actions.
Feb 08 12:54:36 framenix systemd[1]: Stopped target Post-Resume Actions.
Feb 08 12:54:36 framenix plasmashell[3317]: qt.qpa.clipboard: QXcbClipboard::setMimeData: Cannot set X11 selection owner
Feb 08 12:54:36 framenix wpa_supplicant[2759]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 08 12:54:37 framenix wpa_supplicant[2759]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 08 12:54:38 framenix kded5[3271]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
Feb 08 12:54:38 framenix ksystemstats[3364]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
Feb 08 12:54:38 framenix plasmashell[3317]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
Feb 08 12:54:38 framenix wpa_supplicant[2759]: wlp1s0: WPS-PBC-ACTIVE
Feb 08 12:54:38 framenix wpa_supplicant[2759]: wlp1s0: WPS-CANCEL
Feb 08 12:54:38 framenix kded5[3271]: "Das Objekt existiert nicht am Pfad »/org/freedesktop/NetworkManager/ActiveConnection/2«"
Feb 08 12:54:38 framenix kdeconnectd[3514]: "Das Objekt existiert nicht am Pfad »/org/freedesktop/NetworkManager/ActiveConnection/2«"
Feb 08 12:54:39 framenix systemd[1]: Stopped target Host and Network Name Lookups.
Feb 08 12:54:39 framenix systemd[1]: Stopping Host and Network Name Lookups...
Feb 08 12:54:39 framenix systemd[1]: Stopped target User and Group Name Lookups.
Feb 08 12:54:39 framenix systemd[1]: Stopping User and Group Name Lookups...
Feb 08 12:54:39 framenix systemd[1]: Stopping Name Service Cache Daemon (nsncd)...
Feb 08 12:54:39 framenix systemd[1]: nscd.service: Deactivated successfully.
Feb 08 12:54:39 framenix systemd[1]: Stopped Name Service Cache Daemon (nsncd).
Feb 08 12:54:39 framenix systemd[1]: nscd.service: Consumed 52ms CPU time, received 0B IP traffic, sent 8.5K IP traffic.
Feb 08 12:54:39 framenix systemd[1]: Starting Name Service Cache Daemon (nsncd)...
Feb 08 12:54:39 framenix nsncd[21212]: Feb 08 11:54:39.675 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 3s }, path: "/var/run/nscd/socket"
Feb 08 12:54:39 framenix systemd[1]: Started Name Service Cache Daemon (nsncd).
Feb 08 12:54:39 framenix systemd[1]: Reached target Host and Network Name Lookups.
Feb 08 12:54:39 framenix systemd[1]: Reached target User and Group Name Lookups.
Feb 08 12:54:40 framenix kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
Feb 08 12:54:40 framenix systemd[1]: Stopped target Host and Network Name Lookups.
Feb 08 12:54:40 framenix systemd[1]: Stopping Host and Network Name Lookups...
Feb 08 12:54:40 framenix systemd[1]: Stopped target User and Group Name Lookups.
Feb 08 12:54:40 framenix systemd[1]: Stopping User and Group Name Lookups...
Feb 08 12:54:40 framenix systemd[1]: Stopping Name Service Cache Daemon (nsncd)...
Feb 08 12:54:40 framenix systemd[1]: nscd.service: Deactivated successfully.
Feb 08 12:54:40 framenix systemd[1]: Stopped Name Service Cache Daemon (nsncd).
Feb 08 12:54:40 framenix systemd[1]: nscd.service: Consumed 26ms CPU time, received 9.9K IP traffic, sent 5.3K IP traffic.
Feb 08 12:54:40 framenix nsncd[21289]: Feb 08 11:54:40.946 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 3s }, path: "/var/run/nscd/socket"
Feb 08 12:54:40 framenix systemd[1]: Started Name Service Cache Daemon (nsncd).
Feb 08 12:54:40 framenix systemd[1]: Reached target Host and Network Name Lookups.
Feb 08 12:54:40 framenix systemd[1]: Reached target User and Group Name Lookups.
Feb 08 12:54:41 framenix kernel: amd_iommu_report_page_fault: 63555 callbacks suppressed
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf80000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf81000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf82000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf83000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf84000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf85000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf86000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf87000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf88000 flags=0x0000]
Feb 08 12:54:41 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf94000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amd_iommu_report_page_fault: 52293 callbacks suppressed
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab270000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab271000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab272000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab273000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab274000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab275000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab276000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab277000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffab278000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabc05000 flags=0x0000]
Feb 08 12:54:46 framenix kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
Feb 08 12:54:48 framenix systemd-logind[2106]: Lid closed.
Feb 08 12:54:49 framenix systemd-logind[2106]: The system will suspend now!
Feb 08 12:54:49 framenix ModemManager[3585]: <info>  [sleep-monitor-systemd] system is about to suspend
Feb 08 12:54:49 framenix kded5[3271]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Feb 08 12:54:49 framenix kernel: wlp1s0: deauthenticating from f0:b0:14:cb:89:ab by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 08 12:54:49 framenix systemd[1]: Stopped target Host and Network Name Lookups.
Feb 08 12:54:49 framenix systemd[1]: Stopping Host and Network Name Lookups...
Feb 08 12:54:49 framenix systemd[1]: Stopped target User and Group Name Lookups.
Feb 08 12:54:49 framenix systemd[1]: Stopping User and Group Name Lookups...
Feb 08 12:54:49 framenix systemd[1]: Stopping Name Service Cache Daemon (nsncd)...
Feb 08 12:54:49 framenix systemd[1]: nscd.service: Deactivated successfully.
Feb 08 12:54:49 framenix systemd[1]: Stopped Name Service Cache Daemon (nsncd).
Feb 08 12:54:49 framenix systemd[1]: nscd.service: Consumed 33ms CPU time, received 11.5K IP traffic, sent 6.3K IP traffic.
Feb 08 12:54:49 framenix systemd[1]: Starting Name Service Cache Daemon (nsncd)...
Feb 08 12:54:49 framenix nsncd[21456]: Feb 08 11:54:49.562 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 3s }, path: "/var/run/nscd/socket"
Feb 08 12:54:49 framenix systemd[1]: Started Name Service Cache Daemon (nsncd).
Feb 08 12:54:49 framenix systemd[1]: Reached target Host and Network Name Lookups.
Feb 08 12:54:49 framenix systemd[1]: Reached target User and Group Name Lookups.
Feb 08 12:54:49 framenix wpa_supplicant[2759]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 08 12:54:49 framenix systemd[1]: Starting Pre-Sleep Actions...
Feb 08 12:54:49 framenix systemd[1]: pre-sleep.service: Deactivated successfully.
Feb 08 12:54:49 framenix systemd[1]: Finished Pre-Sleep Actions.
Feb 08 12:54:49 framenix systemd[1]: Reached target Sleep.
Feb 08 12:54:49 framenix systemd[1]: Starting System Suspend...
Feb 08 12:54:49 framenix systemd-sleep[21474]: Entering sleep state 'suspend'...
Feb 08 12:54:49 framenix kernel: PM: suspend entry (s2idle)
Feb 08 12:54:49 framenix wpa_supplicant[2759]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 08 12:54:49 framenix wpa_supplicant[2759]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
Feb 08 12:54:49 framenix kernel: Filesystems sync: 0.058 seconds
Feb 08 12:54:54 framenix kernel: Freezing user space processes
Feb 08 12:54:54 framenix kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Feb 08 12:54:54 framenix kernel: OOM killer disabled.
Feb 08 12:54:54 framenix kernel: Freezing remaining freezable tasks
Feb 08 12:54:54 framenix kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Feb 08 12:54:54 framenix kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 08 12:54:54 framenix kernel: queueing ieee80211 work while going to suspend
Feb 08 12:54:54 framenix kernel: ACPI: EC: interrupt blocked
Feb 08 12:54:54 framenix kernel: ACPI: EC: interrupt unblocked
Feb 08 12:54:54 framenix kernel: nvme nvme0: 16/0/0 default/read/poll queues
Feb 08 12:54:54 framenix kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Feb 08 12:54:54 framenix kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Feb 08 12:54:54 framenix kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Feb 08 12:54:54 framenix kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Feb 08 12:54:54 framenix kernel: [drm] ring gfx_32803.1.1 was added
Feb 08 12:54:54 framenix kernel: [drm] ring compute_32803.2.2 was added
Feb 08 12:54:54 framenix kernel: [drm] ring sdma_32803.3.3 was added
Feb 08 12:54:54 framenix kernel: [drm] ring gfx_32803.1.1 ib test pass
Feb 08 12:54:54 framenix kernel: [drm] ring compute_32803.2.2 ib test pass
Feb 08 12:54:54 framenix kernel: [drm] ring sdma_32803.3.3 ib test pass
Feb 08 12:54:54 framenix kernel: amd_iommu_report_page_fault: 35693 callbacks suppressed
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac0000 flags=0x0000]
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac1000 flags=0x0000]
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac2000 flags=0x0000]
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac3000 flags=0x0000]
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac4000 flags=0x0000]
Feb 08 12:54:54 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac5000 flags=0x0000]
Feb 08 12:54:55 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac6000 flags=0x0000]
Feb 08 12:54:55 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac7000 flags=0x0000]
Feb 08 12:54:55 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabac8000 flags=0x0000]
Feb 08 12:54:55 framenix kernel: amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabad4000 flags=0x0000]
Feb 08 12:54:55 framenix kernel: OOM killer enabled.
Feb 08 12:54:55 framenix kernel: Restarting tasks ... done.
Feb 08 12:54:55 framenix kernel: random: crng reseeded on system resumption
Feb 08 12:54:54 framenix systemd-logind[2106]: Lid opened.
Feb 08 12:54:55 framenix xserver-wrapper[2362]: (EE) event11 - Power Button: client bug: event processing lagging behind by 677ms, your system is too slow
Feb 08 12:54:55 framenix kernel: PM: suspend exit
Feb 08 12:54:55 framenix systemd-sleep[21474]: System returned from sleep state.
F

          With s/g disabled though, the patch reliably resolves this coloured glitchyness.

        • Mario Limonciello
          Mario Limonciello @superm1 ·
          Developer

          Colored glitchiness and a white screen with the IOMMU errors like those shown above (AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfffabf80000 flags=0x0000] ) should be different root causes.

        • Trolli Schmittlauch
          Trolli Schmittlauch @schmittlauch ·

          Yeah, seems so. Just wanted to counter the statement of csutcliff:

          amdgpu.sg_display=0 doesn't appear to be necessary on either 6.8 (tested rc3) or the drm-misc-next branch. on older kernels the screen would go white in full screen 3D applications unless S/G was disabled.

          Note that I'm on 6.8-rc2, but I'll test with rc3 as well. The rest of the conversation will continue over in the appropriate issue.

        • Please register or sign in to reply
      • Mario Limonciello mentioned in issue #3136 (closed)

        mentioned in issue #3136 (closed)

      • Mario Limonciello marked this issue as related to #2859 (closed)

        marked this issue as related to #2859 (closed)

      • Trolli Schmittlauch mentioned in issue #2954

        mentioned in issue #2954

        • Alex Deucher
          Alex Deucher @agd5f ·
          Owner

          Possibly related to #2859 (closed)

        • Bert Karwatzki
          Bert Karwatzki @spasswolf ·

          That issue was fixed by (at least for me)

          commit 9ae587f850a6702428273fcf4a2a9b392349b2a3
Author: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Date:   Mon Oct 30 09:25:37 2023 -0700

    drm/amdgpu: Fix the vram base start address
    
    If the size returned by drm buddy allocator is higher than
    the required size, we take the higher size to calculate
    the buffer start address. This is required if we couldn't
    trim the buffer to the requested size. This will fix the
    display corruption issue on APU's which has limited VRAM
    size.
    
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2859
    Fixes: 0a1844bf0b53 ("drm/buddy: Improve contiguous memory allocation")
    Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
        • Please register or sign in to reply
      • Ivan Stanković
        Ivan Stanković @istankovic ·

        Have the same issue (colors, flickering) on kernel 6.7.3, mesa 23.3.5, Ryzen 7 6850u.

      • Mario Limonciello mentioned in issue #3132 (closed)

        mentioned in issue #3132 (closed)

      • arunpravin24 mentioned in commit mwa/kernel@8746c6c9

        mentioned in commit mwa/kernel@8746c6c9

      • arunpravin24
        arunpravin24 @arunpravin24 ·
        Developer

        @spasswolf Good catch. The order should be changed. Thanks!

      • arunpravin24 closed

        closed

      • Thomas Duffin mentioned in issue #3227 (closed)

        mentioned in issue #3227 (closed)

      Please register or sign in to reply