You are not logged in.
So for about a month I've been having the same issue on my desktop, every time I suspend and subsequently turn my pc back on again, I get fans roaring, all the LEDs turning on, one of my three monitors briefly turns on only to say "no input" and nothing further happens. Doing any of CTRL+ALT keybinds achieves nothing and I'm forced to do a hard reset.
My Laptop is running a very similar setup and does not have this issue, so currently I got no better idea than it somehow being related to the discrete GPU.
inxi -Fxxxrz: https://pastebin.com/wsE2jBuV
journalctl -rb -1: https://pastebin.com/pqjNScZZ
Curiously there is no new entries after the suspend, despite me clearly turning the PC back on.
Here's a list of what I tried so far to no avail:
Gone through a few kernel updates passively
modprobe amdgpu
enabled IOMMU in UEFI
updated UEFI to the latest version
reinstalled mesa and amdgpu
This is my first post so I am sorry if it is badly formatted.
Update:
I looked at some other recent issues and saw that a lot of people seem to be having issues with their AMD GPUs and downgraded to linux-6.10.9, now the problem is no longer happening. So it seems the new kernel is a bit busted, but no clue how to report that issue anywhere.
Last edited by Fex (2024-10-06 09:40:45)
Offline
You can also check 6.10.10 kernel and linux-lts package.
Offline
Yeah, I too am having the same issue and have also downgraded to 6.10.10 for the time being.
I believe this is the place to report and/or track the issue:
https://bugzilla.kernel.org/show_bug.cgi?id=219290
Offline
I'm experiencing the same issue since linux 6.11. The journal stop at
(timestamp) (hostname) systemd-sleep[(PID)]: Successfully froze unit 'user.slice'.
(timestamp) (hostname) systemd-sleep[(PID)]: Performing sleep operation 'suspend'...
(timestamp) (hostname) kernel: PM: suspend entry (deep)
(timestamp) (hostname) kernel: Filesystems sync: 0.011 seconds
Occasionally it's the case that my display displays a screen that you would expect from a successful recovery from suspension, which however never updates, but usually it just stays black and says there be no signal.
On normal suspensions (say, on 6.10.10), it seems that whatever happens afterwards, including those reporting on what happens until the suspension is completed (CPU x is down &c.), only gets written to journal as the system resumes from suspension.
Given that the machine does enter and exit the suspended state (which is to be told from LEDs, fans &c. in my case. I think this part is handled by firmware and not the kernel.), what is to be concluded is, I think, that the kernel failed to resume.
EDIT: grammar and formatting
Last edited by soylens (2024-10-08 07:35:58)
Offline
Just a quick update, cause it's almost a month later: Still the same issue with 6.11.5 and everything else up to date too
Offline