| View previous topic :: View next topic |
| Author |
Message |
Delacemane
n00b
Joined: 28 Sep 2024
Posts: 2
|
 Posted: Sun Sep 29, 2024 6:24 am Post subject: Can't suspend |
 |
|
Hello Gentoo forum, after updating my system, it cant suspend anymore. s2idle hangs pc on, triggering wake doesn't really wake it up, however if I press power button it shutdowns(without anything on monitor). s2mem doesn't work at all, system wakes instantly. s2disk works fine.
Happens on kernels 6.11.0 (gentoo-sources) and 6.10.11 (gentoo-kernel) (I don't have other kernels on Gentoo)
Suspend is working fine on my second drive with endeavourOS and kernel 6.9.7
Some hardware info: motherplate: tuf gaming x670e plus wifi, cpu: ryzen 7 7700x, gpu: radeon rx7600.
I was trying to get some logs of s2idle by doing 'echo "freeze" > /sys/power/state && dmesg > /root/kernel-log' and it ends on "The system will suspend now!" |
|
| Back to top |
|
 |
Delacemane
n00b
Joined: 28 Sep 2024
Posts: 2
|
| Posted: Sun Sep 29, 2024 7:40 am Post subject: |
|
|
| I realised dmesg was running just after echo, so making it sleep gave me some logs, thats what happens after triggering s2idle: https://bpa.st/WKIZ5RI7VJQLAW3LPDGKWK6C6I |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3364
Location: de
|
| Posted: Sun Sep 29, 2024 11:36 am Post subject: |
|
|
After updating to 6.11 I guess I have the same problem.
I can suspend the system:
| Code: | Sep 29 11:34:58 nixe systemd-logind[849]: The system will suspend now!
Sep 29 11:34:58 nixe systemd[1]: Reached target Sleep.
Sep 29 11:34:58 nixe systemd[1]: Starting System Suspend...
Sep 29 11:34:58 nixe systemd-sleep[6653]: Performing sleep operation 'suspend' |
I can wake up the system. I see the desktop. But the systems remains in a freezed state, no mouse or keyboard input possible. Even can't switch to TTY.
Something strange:
At least SysRQ seems to work. With Alt+Print+b the computer reboots.
No problems at all with 6.10. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2263
|
| Posted: Sun Sep 29, 2024 12:44 pm Post subject: |
|
|
Try ALT+PrtScr+R to release the keyboard from raw mode, then try to switch to a TTY. You won't see anything but after some attempts you'll be able to log in blindly and issue a reboot.
They "fixed" something that broke S3 sleep and S2idle for amdgpu. I haven't been able to trace it back to the problematic commit but it has been a long time ago. Maybe at least a year. And they have been continuing to "fix" it.
I thought I had traced it back to 6.1.92 but prior to that it just intermittently breaks, that's why I got confused. There were a lot of compilations and reboots involved so I don't feel like doing it more to trace the problematic "fix".
Best Regards,
Georgi |
|
| Back to top |
|
|
musv
Advocate
Joined: 01 Dec 2002
Posts: 3364
Location: de
|
| Posted: Thu Oct 03, 2024 8:52 am Post subject: |
|
|
| logrusx wrote: | | Try ALT+PrtScr+R to release the keyboard from raw mode, then try to switch to a TTY. You won't see anything but after some attempts you'll be able to log in blindly and issue a reboot. |
I know the Shortcuts.
In that case I wasn't able to switch to a tty. If the other keys (release keyboard, sigterm, sigkill, sync) are working I couldn't notice. Only reboot worked.
| logrusx wrote: |
They "fixed" something that broke S3 sleep and S2idle for amdgpu. I haven't been able to trace it back to the problematic commit but it has been a long time ago. Maybe at least a year. And they have been continuing to "fix" it.
|
Up to including Kernel 6.10. suspend worked perfectly on my system. The problems occured with the update to 6.11. |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2263
|
| Posted: Thu Oct 03, 2024 9:36 am Post subject: |
|
|
| musv wrote: | | If the other keys (release keyboard, sigterm, sigkill, sync) are working I couldn't notice. |
You won't notice, because the graphic driver is unable to start. You can notice by probing with NumLock. Release the keyboard, then switch to a TTY and try NumLock. Repeat until NumLock starts working. Then leave it on on one TTY and off on another, so you can test if the system is responsive by switching between the two and the led changes state. You need to release the keyboard repeatedly because systemd will restart gdm or whatever desktop manager you use. In the meantime you try to login blindly and issue a reboot command. Be sure to check your bash history if you typed your password as a command.
Also simply pressing CTRL+ALT+DEL should work as soon as you switch on a TTY, but you can't know if systemd or openrc is waiting for a job to finish.
And ultimately, you may still need to hard reboot.
Best Regards,
Georgi |
|
| Back to top |
|
|
moamahii
n00b
Joined: 04 Oct 2024
Posts: 1
|
| Posted: Fri Oct 04, 2024 12:49 pm Post subject: |
|
|
My situation is similar with my new thinkpad T14 Gen 5 (intel core ultra 5 135U). After some troubles with Kernels < 6.8 I found a good bilance with 6.10.7 (unstable audio but Graphic card is ok ecc.), after this version I'm unable to exit the suspend mode. Explained better:
1) Computer works fine
2) I suspend it (even closing it or using the menu suspend)
3) the led on the cover not blinks
4) when I open it or I try to wake it up the gdm respond really slowly (1 minute or so)
5) at this stage I can use the trackpad, the touchpad is not working , the network connection manager is disappeared from the menu on the corner top right I can login with fingerprint or with password but after it nothing happen and after 30 seconds or so I'm asked again to login
6) I cannot ctrl+alt+f1 for having a console, as said the network is down so I can't ssh on the machine and after forced shutdown (15 seconds power button) The logs have not giving me any hint
I'm using openRC, gnome on 6.11.1 (but same from 6.10.10) and wayland
Note If I shut down display-manager before suspend, in this way I've only consoles active, the computer suspends correctly, the led start blinking and exit normally from the suspend mode |
|
| Back to top |
|
|
|
Kernel & Hardware
