It seems that whenever a graphical component of the OS is adjusted in scale, the is issue occurs. In my experience, Gnome’s experimental fractional scaling will trigger it the most. Here is more information on that: How to Enable Fractional Scaling on Fedora Linux - OMG! Linux
For me, i have my AMD FW 13 (Ryzen 5 CPU with 32 GB of RAM) set to 125%, with amdgpu.sg value set to 0, and the flashing squares have not appear for about a couple of days now. Not sure if this is exactly because of the Kernel setting, or if an update possibly resolved the issue altogether. I have dnf-automatic enabled, so it could have been that.
Alternatively, you can try adjusting the Scaling Factor in Gnome tweaks to see if that floats our boat. For me, I’m not a fan of using it too much, it at all since small UI with big text looks odd.
This has definitely been one of the bigger hurdles to getting acquainted with my new Framework. Unfortunately I think it is a matter of tuning until it works better for you.
I’ve got my first instance of this bug on fedora rawhide (6.7 kernel, with xxmitsu/mesa-git) - It looks like for me it’s preceded by steam runtime coredumping/iommu issues coredumping. My guess is it is corrupting/not freeing some memory region accessed by amdgpu during a power state change.
Steps to reproduce:
a) Launch steam - run something intensive for a while (I used civ6 with proton-ge23)
b) observe steam runtime coredumps and/or iommu errrors in journal
c) change power state from being AC powered to Battery
d) watch as machine goes into sleep/idle
e) Quickly resume from sleep.
f) Get graphical corruption on resume (in my case a whited out screen where sddm/plasma unlock should be) - my cursor was still responsive/active but vtty switching was broken.
g) Hold power to hard reset
h) Look at previous 10m journal
Appreciate this @jwp, if you feel this differs at all from the other mentions of odd AMD blocky/graphical corruption, please file a bug report with them. If you feel this is in line, did enabling the kernel parameter or UMA_Game_Optimized in BIOS helped at all.
I’ve run into this issue and would like to try and add in that amdgpu.sg_display=0 parameter that was alluded to above. However, I’m not too familiar in amending the kernel to make the change (how to edit/where to put in the line). I’m using pop OS (yes, I know that it isn’t officially supported so I wanted to put in the question here as I couldn’t reach out to support).
If someone could provide guidance on this, that’d be much appreciated. I only started using the new laptop about a day ago and am a little concerned about screwing something up.
@Matt_Hartley ; The UMA 4GB VRAM flag should be the default as shipped i’m not sure why it isn’t. 512MB reserved is far too small for the Display Size IMNSHO.
But yes the UMA bios flag not being set out of the box was causing other issues with slow performance in a few things hitting the GPU - so I had it turned on quite early in testing.
Those of you that have hit issues that amdgpu.sg_display=0 or changing VRAM flags helped, can I ask you to revert to the default BIOS settings and see if amdgpu.dcdebugmask=0x10 can also help your issues? This will disable PSR, which I’m wondering if maybe be playing into the underlying issue.
I have done: gsettings reset org.gnome.shell disable-extension-version-validation
and uninstalled gnome-theme-extra, this seemed firstly to work, but now I get the flickering back. I may try the amdgpu.sg_display=0
I got actually a few bug reports in the program for that (“sorry crashed thing”), I sended one, but may finished with errors and others I can’t even report (get errors then).
But no errors accour when flickering happens (like right now while typing).
Have done now sudo systemctl restart gdm and have now the following via journalctl --since 20 minutes:
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac60000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac61000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac62000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac63000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac64000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac65000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac66000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac67000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac68000 flags=0x0000]
21:38:40 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac34000 flags=0x0000]
21:38:40 my-laptop rtkit-daemon[1716]: Successfully made thread 11533 of process 11498 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
21:38:40 my-laptop goa-daemon[11878]: goa_http_client_check() failed: 0 — (null)
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab5e5150 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab5e5150 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aad663d0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aad663d0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aad668b0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aad668b0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab93d070 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab93d070 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab93d550 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab93d550 Gjs_window-list_gnome-shell-extensions_gcampax_github_com
---
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab60bc30 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab60bc30 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab60c110 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab60c110 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab8697f0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab8697f0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab869cd0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab869cd0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab81d3d0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab81d3d0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab6d45b0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:45 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578ab6d45b0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
---
21:38:45 my-laptop chronyd[1808]: Forward time jump detected!
---
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:45 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
---
21:38:45 my-laptop kernel: amd_iommu_report_page_fault: 6272 callbacks suppressed
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac20000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac21000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac22000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac23000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac24000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac25000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac26000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac27000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac28000 flags=0x0000]
21:38:45 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac34000 flags=0x0000]
---
21:38:50 my-laptop kernel: amd_iommu_report_page_fault: 29488 callbacks suppressed
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac20000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac21000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac22000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac23000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac24000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac25000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac26000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac27000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac28000 flags=0x0000]
21:38:50 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac34000 flags=0x0000]
21:38:55 my-laptop kernel: amd_iommu_report_page_fault: 18991 callbacks suppressed
---
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac20000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac21000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac22000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac23000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac24000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac25000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac26000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac27000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac70000 flags=0x0000]
21:38:55 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac7c000 flags=0x0000]
---
21:38:59 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aba88a50 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:59 my-laptop gnome-shell[11498]: st_widget_get_theme_node called on the widget [0x5578aba88a50 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndica>
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
21:38:59 my-laptop gnome-shell[11498]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
21:39:00 my-laptop kernel: amd_iommu_report_page_fault: 23489 callbacks suppressed
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac00000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac01000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac02000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac03000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac04000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac05000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac06000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac07000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac08000 flags=0x0000]
21:39:00 my-laptop kernel: amdgpu 0000:c0:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffffac14000 flags=0x0000]
21:39:05 my-laptop kernel: amd_iommu_report_page_fault: 25428 callbacks suppressed
---
and so on. The amd_iommu_report_page_fault and then the [IO_PAGE_FAULT] multiple times --- means lines removed, e.g. NetworkManager lines.
Flickering happend after the laptop was multiple hours closed.
If the @Framework Team wants to see the report logs (e.g. the one I sent), write me via DM.
IOMMU is kinda important and shouldn’t be disabled ideally. Disabling the amdgpu Scatter gather alone was enough to fix the bug for me.
I might try and see if disabling IOMMU whilst forcing scatter gather on changes behaviour. But IOMMU is kinda important for a heap of other things like SRIOV/Virt and I would imagine it likely has a relatively important place in combination with the amdgpu APU for shuffling memory around consistently.
Seems like it does not fix the graphical corruption, at least for me. I just had the issue arise for me again after I plugged my system into my USBC TB dock, with the lid open. I set Kernel parameter back to the adjusted variable (0).
I have the same issue and unfortunately neither amdgpu.sg_display=0 nor adding amdgpu.dcdebugmask=0x10 to it made any difference. Fedora 39 with BIOS 3.03. Other threads mention reseating the left display connector on the motherboard, which I did. The cable looks healthy and undamaged.
Charging and running heavy loads at the same time makes the laptop unusable due to extreme flickering. So I either have to run only on battery, or stick to light tasks like e-mail and web browsing.
I had my first failure to resume yesterday even with the SG toggle. Like use after heavy load both plugged and unplugged. I am wondering if it’s thermal related
I can trigger this issue much more often if I leave an electron application open during suspend.
I suspect the Javascript VM garbage collection puts more memory pressure on the suspended system triggering the artifacting.
It seems anything with significant memory usage variances can trigger this to happen as even a Rust Gtk application that I set to sync in the background can trigger this issue also.
None of the acpi kernel params for amdgpu alter this behavior, it will always come up if there is memory usage variances in suspend and you wait long enough.
Personally, I don’t believe this is on Framework and am holding out for kernel 6.6 (and it’s bundled firmware) to drop hopefully resolving this as is has a lot of AMD improvements in it.