Bug 217262 - Thinkpad X1 Carbon Gen 10 won't enter sleep on kernel 6
Summary: Thinkpad X1 Carbon Gen 10 won't enter sleep on kernel 6
Status: NEW
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Rafael J. Wysocki
URL: https://bugzilla.suse.com/show_bug.cg...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-28 17:33 UTC by victorfuga
Modified: 2023-03-29 10:38 UTC (History)
2 users (show)

See Also:
Kernel Version: 6.0+
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description victorfuga 2023-03-28 17:33:14 UTC
Coming from bug 1208728 on OpenSUSE bugzilla.
After kernel version 5.19 my Thinkpad X1 Carbon Gen 10 will not enter either s2idle or s3 sleep modes. I have had it working with 5.19.0 in Ubuntu 22.10. I have tried with lid close, inactivity timeouts, sleep button in the kde, and Fn + 4 key combo. Journalctl shows it entering a sleep state but exiting a few seconds after, usually followed with the screen coming back on to show sddm.
Comment 1 Takashi Iwai 2023-03-29 06:33:37 UTC
FWIW, the downstream report is:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1208728
The logs can be found there.
Comment 2 The Linux kernel's regression tracker (Thorsten Leemhuis) 2023-03-29 10:38:08 UTC
With a bit of luck maybe one of the ACPI/PM people will see this and have an idea what might be wrong (or how to find it).

But FWIW, this from my point of view is a tricky regression, as the 5.19 kernel you used with Ubuntu likely was likely heavily patched. And when you compare kernels from various distros you also might use quite different kernel configuration. And this sort of problem is something that can be caused by all sorts of changes in the kernel. And the firmware might have a influence, too, s there apparently are laptops that offer to enable ACPI S3, but the code paths that then get used are not working well, as nobody tested them.

It thus would be good to reduce the number of factors here. Ideally you would try vanilla 5.19 and 6.0 and bisect the problem if the latter works.

Note You need to log in before you can comment on or make changes to this bug.