Hi, i have a problem on a Fedora Workstation.
I have been looking for the cause of freezing problems for several weeks now, however I am not an experienced Linux user, maybe someone has come across a similar one.
After I suspend my laptop and wake it up, the screen remains black and system not response.
I tried to use KDE, then the system freeze on the login screen and not response.
I found out that setting the parameter intel_iommu=igfx_off partially fixes the problem, but still there is a chance of hanging.
@paltis of course you can ignore the solutions with nvidia. These are related to drivers you don’t have. Assuming that you use the default driver of Fedora for your Intel gpu, I don’t think the driver is the origin (… unless we find explicit indication that tells the opposite).
Feel free to show us your logs: as soon as the problem happens again, you restart your computer and then go to a terminal and let us know the output of the following two commands:
journalctl --boot=-1 journalctl --boot=0
The first command shows us the system logs of the last boot (thus, the boot that ended up with the freeze), the latter command of the current boot. It would be also good if you note and tell us the time when you suspended and when you tried to wake it up.
Btw, what was the original value in this place? How does it work if intel_iommu=on and how if you remove the option at all? How is it with iommu=pt (without intel_ in the beginning)? The latter bypasses DMA translation (unlikely to be the origin, but worth a try).
@paltis additionally to the tests in Fedora freezes after suspend - #7 by py0xc3, can you provoke the freeze if you disable wpa_supplicant with sytemctl stop wpa_supplicant.service before suspending? stop will turn it off within this boot, but it will be automatically started again in the next boot. This will disable your wifi for the time it is stopped. Just to exclude this as potential origin…
if i set iommu=pt I can still get a freeze just like when i set intel_iommu=on.
If i set intel_iommu=off I cannot provoke a freeze, however, during operation with a long sleep, it can happen.
Another strange thing when i turn it on laptop in grub strange artifact is running from the top of the screen to the bottom, preventing me from interacting with the menu before it ends, this did not occur in ubuntu 20.04 lts distros from which I switched.
I accumulate, save logs, but for now I switched to kde spin, because it causes itself to be folded in planetary hibernation. and I basically use kde for work.
Sounds indeed like a bug so far. My guess is that it is related to ACPI (which is the “backbone” of suspending tasks): iommu (which is also acpi-related) seems to have an influence on the freeze occurrence, but even when turned off, it does not exclude the freeze to occur (so I assume the bug, or whatever, is not iommu itself). We would need the logs to find out more:
wpa_sytemctl stop wpa_sytemctl.service has no changes for me, I didn’t quite understand how to attach the file, so I’ll leave a link to the logs. boot log on hibernation is updated on suspend. https://github.com/Paltis96/boot_logs.git
@paltis With regards to my guess above, let’s check out the acpi related things.
Install the acpitool (you can remove it when we solved the issue): sudo dnf install acpitool
Then, check the output of sudo acpitool -w (with a lowercase -w) → this outputs information of the acpi devices with wakeup capability. Let us know the output.
I will compare it to the logs and then we will try to disable some devices’ acpi capabilities to identify the device that causes the error (assuming that this the problem is related to acpi). This will be also done with the acpitool.