FS#74387 - [linux] REGRESSION: linux-5.17 beaks suspend on Thinkpad X1 Carbon Gen 9

Attached to Project: Arch Linux
Opened by ifaigios (ifaigios) - Thursday, 07 April 2022, 12:26 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 02 September 2022, 15:46 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

Description:
After upgrading to linux-5.17, my laptop (Thinkpad X1 Carbon Gen 9) wakes up from suspend immediately after entering it. The bug persists with linux-5.17.1
I can provide logs if needed.
The only workarounds I have found is to disable BOTH Bluetooth and "Always on USB" from BIOS, or to downgrade to linux-5.16.16

Additional info:
* package version(s): linux-5.17 , linux-5.17.1
* link to upstream bug report, if any: https://bugzilla.kernel.org/show_bug.cgi?id=215768

Steps to reproduce:
1. Close the laptop lid
2. Laptop enters suspend (red LED stars blinking) and then immediately wakes up (red LED on, fan comes up)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 02 September 2022, 15:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.19.2
Comment by Pavel Pivovarov (PivPav) - Thursday, 14 April 2022, 12:46 GMT
Having the same issue with Clevo NP50HP laptop (Metabox Alpha-S) on both 5.17.1 and 5.17.2 kernels.

Disabling Bluetooth prior to closing lid helps as a workaround.
Comment by Cihat Ertem (fincan) - Friday, 15 April 2022, 08:36 GMT
Same issue with my huawei matebook 14s i7 system. At least in my system issue is related with bluetooth. When BT enabled, sleep is broken and wakes immediately. When BT is offi there is no problem.
I created sleep/suspend hooks to disable/enable BT for sleep/awake process till fix released.
Comment by Jan Alexander Steffens (heftig) - Tuesday, 26 April 2022, 20:04 GMT
If this is solved in 5.18-rc1 as mentioned in the upstream bug, maybe someone who is affected can determine which commit needs to be cherry-picked to fix this?
Comment by leorac (leorac) - Tuesday, 17 May 2022, 17:23 GMT
Same problem with Lenovo t14 and kernel 5.17. Does 5.18 solve the issue?
Comment by ifaigios (ifaigios) - Wednesday, 18 May 2022, 04:54 GMT
Still not fixed as of linux-5.17.8
Comment by ifaigios (ifaigios) - Friday, 27 May 2022, 13:27 GMT
Bug still persists in linux-5.18 :(
Comment by jck (jck) - Saturday, 25 June 2022, 18:47 GMT
This bug is fixed for me on 5.18.6
Comment by Pavel Pivovarov (PivPav) - Tuesday, 28 June 2022, 08:35 GMT
I still can reproduce the bug on 5.18.7.
Comment by Reik Keutterling (Spielkind) - Tuesday, 28 June 2022, 08:36 GMT
It's partial fixed since 5.18.4, see upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=215768
Comment by ifaigios (ifaigios) - Saturday, 09 July 2022, 13:37 GMT
Workaround for this very annoying bug: (credit to liskin)

https://github.com/liskin/dotfiles/blob/fd4787f2fd2bda3792e4ffd25a8cdcc6471fc963/usr/lib/systemd/system-sleep/liskin-bluetooth-disconnect

Put the file in /usr/lib/systemd/system-sleep/ and make it executable to automatically disconnect bluetooth devices prior to suspending.
Comment by Marek Howard (marekhwd) - Thursday, 04 August 2022, 22:11 GMT Comment by Serhii Tsynailo (uzver) - Saturday, 06 August 2022, 17:03 GMT
With 5.18.16.arch1-1 laptop still immediately awake when bluetooth headphones connected before closing lid
Comment by Pavel Pivovarov (PivPav) - Sunday, 21 August 2022, 06:56 GMT Comment by leorac (leorac) - Monday, 22 August 2022, 20:25 GMT
Has any of you tried this workaround? It's worth it or it's still better to stay at 5.15 and wait for better fixes?

Anyway, just for notes: on 5.18.17 the pc correctly goes and stays on sleep, but when I open the lid, all the Bluetooth devices results disconnected, which is pretty annoying for mouse/keyboard. (Lenovo ThinkPad T14 here)
Comment by ifaigios (ifaigios) - Friday, 02 September 2022, 12:28 GMT
Bug fixed in linux-5.19.2, time to close this

Loading...