The screen on my laptop freezes consistently. It started in the last few days after upgrading to F42. Most of my app usage is my browser so this happen mostly when I am using Firefox. Not sure if that matters. The keyboard still works - capslock works, and if I am listening to music on the browser I am able to pause play and mute it.
I have to force turn off and turn on the laptop from the power button as the freeze doesn’t stop.
I’m experiencing a similar issue, but it’s not actually a complete freeze. If you try to switch virtual consoles, it ‘unfreezes’ the system. I’ve reverted the power mode back to ‘balanced’ as @airdiz suggested, though, and I’ll try that as well.
There is another topic, that COULD be the same. I elaborated my experience there:
In my case, the freezes are specific to processes while other processes ain’t affected (so the freeze is only one process, such as Firefox, or the WiFi/wpa_supplicant - I could not yet verify what hangs when sleep is initiated), but the freezes stop from themselves after some time (its actually not a real freeze, just processes that don’t respond some time). I experienced that when WiFi is disabled/enabled after a sleep, it can take up to half a minute. In other cases, its about (maybe a little below) 10 seconds. Logs document the non-response, but so far I couldn’t see much more, but have not yet skimmed a whole log. I wanted to create a dedicated boot, provoke some incidents and then file a bug or so. But I lack time.
I guess this develops towards a bug report (I tend to kernel as initial assumption). The user in the other topic has Intel, but they did not yet elaborate their case, so it is not clear if we talk about the same thing. If they have a different issue, I see so far a correlation of AMD. A major question is obviously if there are different manifests of the same thing, or several different issues.
Here a consolidation of the topics I know so far that COULD be related:
I do not want to merge anything yet as elaborations ain’t 100% identical and I cannot invest the time to do much investigation myself, but people here and in the other topics might exchange and compare what they have in common and what not, and more deeply evaluate their “symptoms” and compare them. As mentioned, manifests of the same issue can differ, but sometimes slight differences can also mean that it is something different
I haven’t upgraded to 42 myself yet, but just from eyeballing these reports in the forum - am I right in thinking they are nearly all on laptops? So perhaps power management is implicated?
It could be also a thing related to the kernel, although only F42 has yet 6.14. So if people experience the same thing with F41 / 6.13, they either have something different, or something else is the cause.
That might be a possibility.
Yeah, but I think as of today, most people use a laptop as their daily driver. So I am not sure if I would derive much from that at this time.
Do I get it right that you experience the same but with F41? If so, could you give a uname -r output?
If I presume that the “performance issue” of one of the other topics is something else (they did not yet elaborate but just talk of “performance issues” in general - no freezes or so mentioned), I think all known cases (including bodhi) have AMD in common, at least so far
I am in a similar boat. I have a freeze occur every few hours. No clear cause, I’m normally just browsing the web. Started after upgrading to F42 a few days ago. I’m on a Lenovo Thinkpad Z16 Gen 1. Full screen freeze, but background audio or voice calls are still working. Here is my most recent error report - crash occurred at 19:08:
Apr 19 17:10:49 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GP17.XHC0.PSTA], AE_ALREADY_EXISTS (20240827/dswload2-326)
Apr 19 17:10:49 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Apr 19 17:10:50 fedora kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Apr 19 17:11:14 fedora gdm-password][2294]: gkr-pam: unable to locate daemon control file
Apr 19 17:11:24 fedora systemd[2316]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2485.scope - Application launched by gnome-session-binary.
Apr 19 17:11:24 fedora systemd[2316]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2488.scope - Application launched by gnome-session-binary.
Apr 19 17:11:24 fedora systemd[2316]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2491.scope - Application launched by gnome-session-binary.
Apr 19 17:11:26 fedora systemd[2316]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2728.scope - Application launched by gnome-session-binary.
Apr 19 17:13:13 fedora bluetoothd[1031]: src/service.c:btd_service_connect() a2dp-source profile connect failed for BC:87:FA:5B:A6:A4: Device or resource busy
Apr 19 17:32:34 fedora bluetoothd[1031]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not >
Apr 19 18:02:55 fedora kernel: rtsx_pci 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible
Apr 19 18:03:02 fedora bluetoothd[1031]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Apr 19 18:03:40 fedora NetworkManager[1222]: <error> [1745103820.6331] device (wlp1s0): Couldn't initialize supplicant interface: Timeout was reached
Apr 19 18:03:55 fedora NetworkManager[1222]: <error> [1745103835.9967] device (wlp1s0): Couldn't initialize supplicant interface: Timeout was reached
Apr 19 18:04:10 fedora NetworkManager[1222]: <error> [1745103850.9967] device (wlp1s0): Couldn't initialize supplicant interface: Timeout was reached
Apr 19 19:08:00 fedora kernel: amdgpu 0000:64:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 19:08:00 fedora kernel: amdgpu 0000:64:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 19:08:00 fedora kernel: amdgpu 0000:64:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Apr 19 19:08:10 fedora kernel: amdgpu 0000:64:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
I have a similar situation. My main work happens in the browser (I use Firefox), and my laptop is a Lenovo Legion 5 17IMH05.
I used to experience frequent system freezes, especially during active work.
Yesterday, I switched the power mode from “Performance” to “Balanced” — it’s been over 24 hours now, and I haven’t encountered a single freeze.
Previously, freezes happened quite regularly, so it seems the issue might indeed be related to the power mode.
In order to keep together all data that belongs together (which fosters solution of the issue for everyone affected), I suggested to consolidate experiences and what people have in common in this topic here → you might use this one IF its elaborations apply to you. Feel free to add more information to help identifying what all have in common in order to identify what cases are the same, and what might be the origin.
I leave all other topics open as the elaborations of the three topics (this one, No.2 plus No.3, and maybe more) do not yet make clear if that really are all the same issue. So if you think the one I mentioned does not apply to you but any of the other, you may of course keep posting there. But I suggest to mention your reasons in order to help delimiting the issues.
Everybody is free to open a bug report of course, but I suggest to invest the time to fill its fields carefully and produce and provide relevant data/logs that get attached, in order to get a real chance that a maintainer can pick it up (especially in times of a new release maintainers have to focus).
If you see more related topics that might resemble one of the existing ones, feel free to let them know about the others.
When I had a moment to spare, I could verify that the long freeze that occurs before the system goes sleep (as elaborated earlier, when sleep is started by closing lid, it takes 10-20 seconds until it actually goes sleep; frozen till then) is itself just the side effect of the non-responsive WiFi that hangs for the mentioned time: if WiFi is disabled, sleep works. All other symptoms remain as mentioned, at least in my case.
In my case, I haven’t noticed any issues related to closing the lid or WiFi behavior.
The freezes were happening randomly during active usage — usually while working in the browser (Firefox) or launching games. No specific trigger like going to sleep.
After switching from “Performance” to “Balanced” power mode, the issue seems to have disappeared — it’s been stable for over 24 hours now.
I’ll try to monitor it further and share more details if it happens again.
I’ve been observing and tracking back my steps. I think my issue started while using my laptop on the Performance power mode but it continued while I was using it on Balanced mode as well after that.
A day earlier I got a system update on Software. After doing that I have not experienced freezes on the Balanced mode at least. Things have been very stable. I will test later today if there is any such improvement while using the Performance power mode or not.
I am not sure how to list or show what update that was. If anyone could help me with a command that can do so, I’ll be happy to share.
Hey there,
I experienced another full system freeze — the entire desktop became unresponsive (keyboard and mouse stopped working), and I had to reboot using the power button.
I suggest to those who think they experience a permanent freeze (which enforces a hard reset/reboot) to wait for at least two minutes: there are reports that the freeze stops after a minute or so, especially if WiFi is involved/enabled. It would be good to know if what you have is really a full permanent freeze that needs a hard reset (which indicates that there are two different symptoms the different people experience) or if the freeze time just differs depending on the process that has frozen and can take up to 2 minutes. Feedback would be great here.
I presume no one could take the time for a detailed bug report yet, with related logs of an affected boot including the very times when the freezes have occurred and how they manifested?
Kernel 6.14.3 has been already build, and I presume it enters bodhi soon. I aim to do an immediate test once the automated tests have passed, in order to provide feedback early to the maintainer about this issue before the next kernel gets pushed to stable. That could be useful and something I can spare the time for.
supplement: people might also try if the issues also occur if WiFi is disabled. I still presume WiFi is only one of the symptoms, but I experienced a long period without issues yesterday, when WiFi was disabled at all (this means not only “not connected” to a wireless network, but disabled at all). Interested to hear other experiences. I will observe this more closely now and see if that proves a permanent correlation or if it was just a coincident.
Several kernel testers who experienced the issues I elaborated have reported that the new kernel 6.14.3 solves the issues for them. This includes me: the issues that I could reproduce always (sleep freeze, and wifi freeze after it) have disappeared. I hope this applies also to the other issues. We’ll see. But that the reproducible freeze has disappeared gives hope that the others did too
If you want, you can test the new kernel once it has entered testing (it is atm one step before the official testing stage), but since all automated tests have been passed and since some people already tested it in practice, I presume that the following page will soon enter testing stage, and thus show a dnf command (beginning with sudo dnf upgrade --refresh --advisory= and then an attribute to the advisory) that has a yellow background at the top of the page. Once that showed up, you can use that command to get the new kernel that hopefully solves the issue for everybody. Keep in mind that the kernel is then still in testing, and although a lot of testing has already been done when the “public testing” starts and that it is highly unlikely that major issues show up at this time, it is still testing until pushed to stable (which means to end up in your normal updates). So if you feel unsure, you might want to wait for it to be pushed to stable. Keep also in mind that this dnf command is a one-time-command: this means, it does NOT enable testing in general or so, it just installs that one update from testing, and then goes ahead as usual with stable only (including future kernels).
Feel free to let us know if that solves your issue too.
Supplement: the kernel is now in official testing. It can be installed already before it is pushed to the stable updates with sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0341e0131a → as mentioned above, keep in mind that it is testing! So far tests are promising, and it might be pushed to stable soon anyway.
I’m waiting for the kernel to appear in the updates. Meanwhile, I turn off the laptop every evening instead of going to sleep to go around the amdgpu freeze issue. I need to use the PC for over 10 hours for that problem to occur.
I updated to kernal 6.14.3 and am still getting freezes on my Thinkpad Z16 Gen 1. Here is the crash log from my most recent freeze. Happens every hour or so. Crash occurred at 18:36, but I let it sit for several minutes as instructed to ensure it was a real freeze.
running 6.14.2 right now.
when i was on fedora41, it took 10-11 hours for the amdgpu to die/screen off.
since i upgraded to fedora 42 and its current 6.14.2, now crashes are daily, and require much less time to happen : a few hours.
it got worse. so much i now have a laptop right next to my main laptop, connected with ssh and on the terminal the “reboot” command is just waiting for the return key.
I was facing this several times an hour on my AMD ThinkPad P16s but it seems like disabling the wifi and using wired ethernet might have resolved the problem?
Logs archive: