System: Debian Stable 12 x86_64
Old notebook Intel Core™ i7-2720QM and Nvidia GeForce® GTX 560M, and I'm using a self encrypting SSD configured with sedutil.
I boot with the parameter libata.allow_tpm=1 and I have a systemd service to store the password in the kernel allowing it to decrypt the disk on waking up.
Problem: since linux-image-6.1.0-14-amd64 (through 15, 16, 17 and 18) the system is unable to fully wake up from suspend. Most of the time it wakes up to a black screen and CAPS LOCK led doesn't change when pressing the CAPS LOCK button. Sometimes the monitor turns on and I can login in a tty but no command ever works. Not even `reboot` `shutdown` etc. Regardless if the monitor turns on, I can shutdown with Alt + SysRq + B.
(bug reports: 1058028, 1058052, 1058890)
What I've tested:
1) Adding: nomodeset, init_on_alloc=0, intel_iommu=off to boot the kernel. No change at all.
2) I tested suspend by writing to /sys/power/pm_test the following successively "freezer", "devices", "platform", "processors", "core". Every single test was successful, ie, the system wakes up on its own after 5 seconds.
3) `echo mem > /sys/power/state"` instead of `systemctl suspend`. No change.
4) Changing /etc/systemd/sleep.conf to have "SuspendState=standby" or "SuspendState=freeze" seems to make things worse because the notebook seems unable to enter sleep mode, while "SuspendState=mem" causes the same behavior as reported here.
5) I recompiled sedutil after booting linux-image-6.1.0-18-amd64 (git clone --branch s3-sleep-support https://github.com/badicsalex/sedutil.git). It made no difference.
Old notebook Intel Core™ i7-2720QM and Nvidia GeForce® GTX 560M, and I'm using a self encrypting SSD configured with sedutil.
I boot with the parameter libata.allow_tpm=1 and I have a systemd service to store the password in the kernel allowing it to decrypt the disk on waking up.
Problem: since linux-image-6.1.0-14-amd64 (through 15, 16, 17 and 18) the system is unable to fully wake up from suspend. Most of the time it wakes up to a black screen and CAPS LOCK led doesn't change when pressing the CAPS LOCK button. Sometimes the monitor turns on and I can login in a tty but no command ever works. Not even `reboot` `shutdown` etc. Regardless if the monitor turns on, I can shutdown with Alt + SysRq + B.
(bug reports: 1058028, 1058052, 1058890)
What I've tested:
1) Adding: nomodeset, init_on_alloc=0, intel_iommu=off to boot the kernel. No change at all.
2) I tested suspend by writing to /sys/power/pm_test the following successively "freezer", "devices", "platform", "processors", "core". Every single test was successful, ie, the system wakes up on its own after 5 seconds.
3) `echo mem > /sys/power/state"` instead of `systemctl suspend`. No change.
4) Changing /etc/systemd/sleep.conf to have "SuspendState=standby" or "SuspendState=freeze" seems to make things worse because the notebook seems unable to enter sleep mode, while "SuspendState=mem" causes the same behavior as reported here.
5) I recompiled sedutil after booting linux-image-6.1.0-18-amd64 (git clone --branch s3-sleep-support https://github.com/badicsalex/sedutil.git). It made no difference.
Statistics: Posted by asana — 2024-02-17 11:21 — Replies 0 — Views 22