This sounds like a hardware issue as I am not seeing this here on two separate units. What is your update status (last time updated) and which kernel is in use again?
Edit: I’m doing a clean install now and retesting to see if a bug cropped up.
This AM opened lid and was unable to wake. Rebooted and updated (dnf update), later laptop suspended after inactivity, and when woken, display was flickering.
Linux devnull 6.5.7-300.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 11 04:19:02 UTC 2023 x86_64 GNU/Linux
Just did a clean install, running current kernel 6.5.9-300.fc39.x86_64 - suspended and resumed multiple times without issue. Logs reflect successful resuming as well.
Are you like Tim, attached to external displays as well? If so, how are the displays connected (expansion cards, HDMI or DP)?
It used to only happen when external displays were connected. Now it occurs even without them.
But when I had them connected, it was via USB-C expansion card for one monitor, with the other monitor daisy chained via DP.
Do you know what log files I should look at shouldwhen this happens again?
Now that I have everyone on the same thread.
-
Been trying to replicate this as to file a bug.
-
I can see the log noise, but not the artifacting itself on my own two systems.
-
Kernel 6.5.9 as well.
-
Wayland.
-
Single display (for testing).
Let’s compare.
-
Some users have indicated this has happened regardless of on power or on battery.
-
This is happening with internal display.
-
Is this happening on live USB or is this rare enough it’s difficult to make it happen there?
-
We want to test this on a single internal display only for now.
Can everyone affected match this criteria? For me to file this, I need to get it replicated.
If you all can replicate this, you can file this bug here: Log in to Red Hat Bugzilla
I’m seeing this same behavior on my system as well, and I have 3.03 installed. I’ve only had it occur on the lock screen and only after waking from suspend, not after a fresh boot.
However… I’m on the latest Elementary OS which is based on Ubuntu. I figured it was just a quirk from my distro choice I’d have to deal with. But not on Fedora like the rest of the thread.
edit:
Just saw Matt’s reply, so I’ll share my particulars
6.2.0-36-generic
Wayland
Internal display
Regardless of power/battery
Unable to replicate on live USB, but my occurrences have been rare
-
Yes this is the same in my experience. I believe it’s more closely related to suspend and resume or perhaps modesetting since people reported it from launching steam games above. It honestly reminds me of intel psr bugs. Or, more specifically this.
-
Yes
-
Perhaps? I believe I can reliably trigger it by suspending and resuming and using the laptop for about two days. It seems to always happen after two days, at least so far.
-
Using the orignal glossy display from a batch 4 or 5 (I forget) 11thgen Framework.
EDIT:
6.5.6-300.fc39.x86_64 also added the phoronix article above.
1 Like
Okay, awesome. If you can replicate this, can you file this as a bug on Bugzilla? I can be tagged as “mattwork” there and can comment on it. But without being able to replicate it on my end, my hands are tied as the Fedora team needs that data. 
1 Like
Caught it, thanks!
I’m currently on Fedora 39 Silverblue with kernel ver. 6.5.6-300.fc39.x86_64.
I’ll try to recreate this bug on a live usb of regular Fedora 39.
I have this problem on Fedora 39 Beta.
It’s worth noting that I only see this problem when I have left the laptop running for several days without a reboot. So if you regularly shut down your laptop you probably won’t experience this problem.
For me after a few days I’ll start getting it occasionally when waking the laptop from sleep, and it will be fixed by putting it back to sleep and waking it again. But after a few more days it will suddenly start having the problem on every wake from sleep, but it will be fixed by restarting the laptop.
I have not checked the display cable but I don’t believe the cable is the problem, since if I don’t move the lid at all and restart the computer the problem will be fixed. Also, the corruption will often have blocks localised around text elements in the UI, which doesn’t seem like a weak cable connection problem to me.
The delay in seeing this issue after a restart also means that with any possible fix that requires shutting down the laptop, you’ll have to wait at least 4-5 days for reliable results.
Just a potential data point to consider… is whether people are using fractional scaling?
When it occurs on my internal display, I see this when resuming from sleep. This is lock screen at 100% scaling changing to 150% scaling on Wayland.
With multiple displays, it is easy to trigger when adding or removing monitors, reconfiguring them, etc. I think I even managed to get it to happen once by switching which monitor was primary.
1 Like
I wonder the same on fractional scaling, my problem is I can’t replicate it consistently.
- Usually started while on power, but would continue after unplugging
- Affected both internal display and external display when connected via USB-C
- Sorry, didn’t try with live-USB
- Definitely happened with just a single internal display
For me, I could reproduce by changing my screen resolution or zoom level. FYI I’m running the Fedora 39 beta KDE spin but it also happened with the regular Gnome Fedora 39 beta.
Adding the amdgpu.sg_display=0 kernel param has 100% fixed this for me - I haven’t seen this happen since adding that param.
1 Like
AMD has confirmed that this is difficult to duplicate, however, that using amdgpu.sg_display=0 is the way forward. Will be updating docs today for those affected.
Also if you can provide logs and steps to duplicate, please create an issue here:
2 Likes
Hi All,
I’ve just got my nice new shiny FW13AMD, and I’m super impressed, great work FW Team.
I’m a Debian fan, and yeh I know, not “officially” supported etc and this is a Fedora thread, but…
I’ve just loaded a fresh Debian 12(Bookworm) build, ver 12.2 and upgraded to kernel(from stable-backports) 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux and can successfully replicate this “white screen” issue.
What I’ve been able to find is that when you suspend, then awake, if you have any application, like a browser etc, trying to access and use the 3D acceleration of the amdgpu driver, the screen corrupts the display output.
I simply close that browser(in my case Brave), and the corruption stops(in my case white solid screen or “techno” flickty flashes, glad I don’t have epilepsy conditions).
I hope that this might help/point us all in the right direction.
Let me know if there’s any other info you’d like.
Paul.
1 Like
Maybe a red herring, maybe not. I’ll throw this out here in case it helps. I have a 2015 15” MBP with a discrete AMD r9 GPU that I tried loading Debian 12 onto and got this exact same issue of white covering most of my screen, with blocks especially around text, making it unusable. The big difference is it happened 100% of the time. Only thing that machine has in common with FW 13 AMD is the AMD gpu I think, albeit a very different gpu. But perhaps this still points to the issue being with AMD’s gpu driver?
Instead of posting here it may be helpful to report this directly to AMD with logs. It seems like there is already an issue open: ubuntu 22.04, AMD 7840, SCREEN turn white/black/stripes (#2954) · Issues · drm / amd · GitLab. They probably need more information to be able to troubleshoot.
If it’s a different issue may be worth opening a new ticket so they know what is going on. No one from AMD is monitoring these forums from what I can tell.
There is an amd-gpu-firmware update in F39 updates-testing. Just upgraded and rebooted and no errors with full screen video after 5 min.
upgrading:
amd-gpu-firmware noarch 20231030-1.fc39 updates-testing
2 Likes