You are not logged in.
Hello, I use the following command to sleep my laptop (Lenovo T14):
systemctl suspend
However, since last week whenever I sent my laptop to sleep, it won't wake up. Not by any keyboard or trackpad buttons, not even by pressing the power button!
Any ideas please?
Thanks.
Info:
The system is updated to the latest packages.
$cat /sys/power/state
# Contains:
freeze mem disk
Last edited by light9876 (2024-01-12 21:00:25)
Offline
cat /sys/power/mem_sleep
cat /proc/acpi/wakeup
Can you still https://man.archlinux.org/man/rtcwake.8
ceterum censeo: is there a parallel windows installation?
since last week
What happened last week? Updates? kernel? systemd? firmware (uefi)?
Offline
I have exactly the same issue since a few days with my Lenovo Thinkpad z13 (AMD) not waking up from suspend. Not all the time but it is about 50/50. I have to still figure out how to secure the logs, because there are non when I do a hard reset.
Offline
Not all the time but it is about 50/50
Can you check if resume always works properly if you suspend the machine with the AC power kept plugged-in?
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
What i (hope) to have found out:
The Laptop does not even suspend (as it was the case until ~29 Dec) when I close the Lid and AC is connected. I then tried to suspend via systemctl suspend and could not resume anymore, display keeps black.
Jan 03 14:01:31 angus systemd[1]: Reached target Sleep.
░░ Subject: A start job for unit sleep.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sleep.target has finished successfully.
░░
░░ The job identifier is 4826.
Jan 03 14:01:31 angus systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-suspend.service has begun execution.
░░
░░ The job identifier is 4825.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Successfully made thread 2749 of process 2713 owned by '1000' high priority at nice level 0.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Supervising 8 threads of 5 processes of 1 users.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Supervising 7 threads of 4 processes of 1 users.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Supervising 7 threads of 4 processes of 1 users.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Successfully made thread 2749 of process 2713 owned by '1000' RT at priority 20.
Jan 03 14:01:31 angus rtkit-daemon[2438]: Supervising 8 threads of 5 processes of 1 users.
Jan 03 14:01:31 angus systemd-sleep[5446]: Failed to lock home directories: Unknown object '/org/freedesktop/home1'.
Jan 03 14:01:31 angus systemd-sleep[5446]: Performing sleep operation 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now entered the suspend sleep state.
Jan 03 14:01:31 angus kernel: PM: suspend entry (s2idle)
Jan 03 14:01:31 angus kernel: Filesystems sync: 0.016 seconds
Jan 03 14:01:33 angus kernel: Freezing user space processes
Jan 03 14:01:33 angus kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Jan 03 14:01:33 angus kernel: OOM killer disabled.
Jan 03 14:01:33 angus kernel: Freezing remaining freezable tasks
Jan 03 14:01:33 angus kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 03 14:01:33 angus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 03 14:01:33 angus kernel: ACPI: EC: interrupt blocked
Jan 03 14:01:33 angus kernel: ACPI: EC: interrupt unblocked
Jan 03 14:01:33 angus kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: SMU is resuming...
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: SMU is resumed successfully!
Jan 03 14:01:33 angus kernel: cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: DSP1: Firmware version: 3
Jan 03 14:01:33 angus kernel: cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: DSP1: cirrus/cs35l41-dsp1-spk-prot-17aa22f1.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe Daylight Time
Jan 03 14:01:33 angus kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jan 03 14:01:33 angus kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jan 03 14:01:33 angus kernel: [drm] JPEG decode initialized successfully.
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Jan 03 14:01:33 angus kernel: amdgpu 0000:e3:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Jan 03 14:01:33 angus kernel: OOM killer enabled.
Jan 03 14:01:33 angus kernel: Restarting tasks ... done.
Jan 03 14:01:33 angus kernel: random: crng reseeded on system resumption
Jan 03 14:01:33 angus systemd-sleep[5446]: System returned from sleep operation 'suspend'.
░░ Subject: System sleep state suspend left
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now left the suspend sleep state.
Jan 03 14:01:33 angus bluetoothd[1702]: Controller resume with wake event 0x0
Jan 03 14:01:33 angus kernel: PM: suspend exit
Last edited by gaelic (2024-01-03 13:05:42)
Offline
This one is related:
https://bbs.archlinux.org/viewtopic.php?id=291408
And the error seems to be systemd with the Failed to lock home directories: Unknown object '/org/freedesktop/home1'.
Other users using various dirstributions seem to report similar behaviour (googling this error message)
There is a pull request open regarding this issue:
https://github.com/systemd/systemd/pull/30638
Next I will try to downgrade systemd in the meantime.
Last edited by gaelic (2024-01-03 13:13:01)
Offline
Please never use "-x" w/ journalctl, it's pure spam.
Speaking of spam:
Failed to lock home directories: Unknown object '/org/freedesktop/home1'.
Do you even use systemd-homed (where "idk" == "no"); the related "errors" are usually pure spam. Lennart is nagging people into finding a usecase for that nonsense.
You can otherwise completely ignore that.
You're not using S3 but s2idle and if that's a complete (unfiltered) journal segment, that doesn't last long:
Jan 03 14:01:33 angus kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 03 14:01:33 angus kernel: ACPI: EC: interrupt blocked
Jan 03 14:01:33 angus kernel: ACPI: EC: interrupt unblocked
Jan 03 14:01:33 angus kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
1. same question as for the OP: parallel windows installation?
2.
cat /sys/power/mem_sleep
cat /proc/acpi/wakeup
Offline
Yep, so that was that, systemd downgrade was pointless (and of course I'm not using systemd-homed).
1) no parallel windows installation
2)
❯ cat /sys/power/mem_sleep
[s2idle]
❯ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
GPP0 S4 *disabled
GPP1 S4 *enabled pci:0000:00:01.2
GPP2 S0 *disabled
L860 S0 *disabled
GPP5 S4 *disabled
GPP7 S4 *disabled
GP11 S0 *enabled pci:0000:00:03.1
SWUS S4 *disabled
GP12 S0 *enabled pci:0000:00:04.1
SWUS S4 *disabled
GP17 S4 *enabled pci:0000:00:08.1
XHC0 S4 *enabled pci:0000:e3:00.3
XHC1 S4 *enabled pci:0000:e3:00.4
GP19 S4 *enabled pci:0000:00:08.3
XHC2 S4 *enabled pci:0000:e4:00.0
NHI0 S0 *enabled pci:0000:e4:00.5
XHC3 S3 *enabled pci:0000:e4:00.3
NHI1 S0 *enabled pci:0000:e4:00.6
XHC4 S3 *enabled pci:0000:e4:00.4
LID S4 *enabled platform:PNP0C0D:00
SLPB S3 *enabled platform:PNP0C0E:00
Offline
There're quite some devices enabled, anything w/ S3/S4 can wake the system from s2idle
XHC* is USB, NHI is thunderbolt, for GP you'll have to correlete "lspci -nn"
You can toggle the devices by writing the 3/4-letter code into /proc/acpi/wakeup
I'd just scratch anything what you do not absolutely want to wake the system and check the impact.
Offline
I've now downgraded the kernel to 6.6.7, as it worked without flaws until ca 1 week ago. And after 3 suspend/sleep cycles there were no problems. I'll keep you updated if this is the case after even more.
Offline
If tihs is a clear regression, a comparative journal segment and acpi/wakeup list might be insightful
Offline
After a few more sleep and wakeup cycles, with and without charger connected, I can confirm (at least for my case) that with kernel 6.6.7 it works, while 6.6.8, 6.6.9 and linux-mainline do not work.
It would be nice if the thread opener can confirm?
Offline
I just updated my computer after some 10 days absense. It works again. Whether it is a kernel update which was the cause I'm not sure, but it's working again. Thanks.
Offline
After a few more sleep and wakeup cycles, with and without charger connected, I can confirm (at least for my case) that with kernel 6.6.7 it works, while 6.6.8, 6.6.9 and linux-mainline do not work.
It would be nice if the thread opener can confirm?
Hey gaelic. Also https://bugzilla.kernel.org/show_bug.cgi?id=217239 could be related to your problem. At least that was the culprint on my Z16. linux 6.6.x and ath11k firmware version 09&16 worked really good. (So until today when I upgraded to linux 6.7.arch3-1 and s2idle is completely broken now.)
Offline
Yes it might be related to the ath11k driver/module/firmware. I do not have time at the moment to test and reboot a lot, I'm at kernel 6.6.7 at the moment with no issues and will come back to this. Thx.
And with kernel 6.7 things even got worse according to:
https://bugzilla.kernel.org/show_bug.cgi?id=217239#c27
"So with kernel 6.7 also using the old firmware does not work anymore. I get a hard freeze on suspend. If i disable the wifi & bluetooth in the firmware (so effectively disabling the QCNFA765) suspend works fine again."
And I also get these hard freezes with 6.7.
Last edited by gaelic (2024-01-18 11:05:50)
Offline
On Lenovo z13 gen 1, AMD 6840u :
Kernels > 6.5.13 are unstable
Kernel 6.7.0
SDDM comes up
login:
either black screen or "some part of the screen" but no panel
... freezes after a minute
Offline
What does that have to do with anything in this thread?
Open a new one and post a system journal there.
Offline