I don’t use Pop OS, but from a quick google and look at the documentation, it seems you should run
kernelstub -a "amdgpu.sg_display=0"
(if necessary with sudo).
However I haven’t test this, maybe look up kernelstub yourself and see if it seems right to you.
@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.
Yes, sorry I meant 22.04.3 with the 6.1.x OEM C kernel (I can’t seem to figure out how to edit the post).
In my case that has resolved the flicker/artifacts. I have other nits, mostly minor performance or UX related annoyances. But I’ll survive 
Thanks,
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.
I’ve had one hiccup since following your suggestion and here is what spat out on dmesg.
[64294.541861] amdgpu 0000:c1:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:24 vmid:2 pasid:32780, for process RDD Process pid 14453 thread firefox:cs0 pid 14471)
[64294.541871] amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000800100bda000 from client 18
[64294.541875] amdgpu 0000:c1:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00203A30
[64294.541878] amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x1d)
[64294.541880] amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
[64294.541883] amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
[64294.541885] amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[64294.541887] amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
[64294.541889] amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
Thanks, it confirms this is not a PSR sourced issue. The S/G or increased VRAM in BIOS are best workarounds for now.
Could you bring a bug report to AMD Gitlab? This needs to be in front of more people at AMD.
I should probably be clear what I did before we call this the problem. I have been working happily with the following:
sudo grubby --args="amdgpu.sg_display=0 amd_iommu=off" --update-kernel=ALL
When you had me try without amdgpu.sg_display=0,I went and removed amd_iommu=off as well…
I have added back amdgpu.sg_display=0 to the amdgpu.dcdebugmask=0x10 argument and so far (5 minutes trying to make things twitchy), no problems.
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 the amd-gpu-firmware update is out of testing and is now globally available.
Once this is installed, can we remove amdgpu.sg_display=0 from our kernel params?
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.
Just chiming in with my own experience of this. See it as per others on resume, almost vanilla fedora gnome 39 install / 3.03 etc / 64gb ram / Linux 6.5.11-300.fc39.x86_64 x86_64. I only got half way through the thread because I’ve got to get to work shortly, but will loop back with more detail this evening if I find it hasn’t been solved (there were some promising things in posts a few weeks ago).
In my case it was just on battery. Would have been resuming Firefox, Thunderbird, Alacritty, Terminal, Docker with Postgres and Redis and a Rust Web server app. Of those Alacritty is gpu accelerated (and I kind of love the idea that the gpu intense task that triggered the graphical issues was a terminal…).
Not sure if it was suspended or hibernating, probably the former as far as I understand the defaults? Most of the screen was artifacting (White with some visible regions of the login down the right) so I couldn’t get in and just had to hard-reboot. The only different thing I’ve done with the machine is that yesterday I did a full reinstall from KDE Spin to Gnome because of cascading instability with KDE (though I suspect that was all software and my fault as I had been playing with tiling plugins without cleaning them up).
Will return later on and read the rest of the thread / provide more context / logs as necessary.
Updated w/Additional Info: Running 150% scaled, I haven’t attached an external monitor at all to the laptop yet (though I do have the HDMI expansion card in there), have only heard the fans once for a 30 second period in the week I’ve had it. Also was running Slack which I just spotted reported that it had crashed.
I too don’t think this looks like a hardware fault at this stage, definitely feels different to hardware failures causing graphical corruptions I’ve seen in the past. Onward to Kernel 6.6 :).
@mikeymop ; hate to break it to you but I’m running all the various included amdgpu patches that were added both for the 6.6 and 6.7 (6.7 has a lot more of them). And I am still getting freezes.
6.7 with SG disabled it’s far less frequent tho.
Just chiming in with a datapoint: I’ve had my machine on Fedora 39 (XFCE/Xorg) for about two weeks now and have experienced no issues. I have not added any amgpu boot params. One thing I wonder is if this is related to the amount of memory in the system; I have 32G in mine and haven’t yet filled it up.
As far as I know, the issue arises only when there is a memory capacity of 64GB or more.
Setting amdgpu.sg_display=0 seemed to work for me.
Specs:
PopOS 22.04
2x 1440p monitors
32GB RAM
X11
6.5.6-76060506-generic
3.03 BIOS
White flickering was really bad before and I needed to pretty much restart my computer to buy me another couple hours before it happened again.