Regression in 5.13.0-23: laptop cannot suspend or turn off

Bug #1958007 reported by Daniel Szoboszlay
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Starting from 5.13.0-23-lowlatency my laptop fails to suspend, turn off or reboot.

On suspend the screen turns off, but the power button LED stays on (it should be blinking when suspended), the keyboard backlight and the CPU fan stays on. I cannot resume the laptop by pressing the power button or any other button.

On power off and restart I see the splash screen and nothing happens.

The last working Ubuntu kernel is 5.13.0-22-lowlatency. 5.13.0-23-lowlatency and 5.13.0-25-lowlatency are broken.
I also tried the latest upstream mainline kernel, linux-image-unsigned-5.16.0-051600-lowlatency_5.16.0-051600.202201091830_amd64.deb, and it doesn't have this regression.

This happens on a Lenovo IdeaPad Flex 5, the AMD variant (Ryzen 7 4700U).

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-lowlatency 5.13.0.25.36
ProcVersionSignature: Ubuntu 5.13.0-23.23-lowlatency 5.13.19
Uname: Linux 5.13.0-23-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dszoboszlay 2528 F.... pulseaudio
 /dev/snd/controlC0: dszoboszlay 2528 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 09:01:15 2022
InstallationDate: Installed on 2020-06-04 (589 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81X2
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-23-lowlatency N/A
 linux-backports-modules-5.13.0-23-lowlatency N/A
 linux-firmware 1.201.3
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-10-29 (77 days ago)
dmi.bios.date: 10/15/2020
dmi.bios.release: 1.29
dmi.bios.vendor: LENOVO
dmi.bios.version: EECN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Flex 5 14ARE05
dmi.ec.firmware.release: 1.19
dmi.modalias: dmi:bvnLENOVO:bvrEECN29WW:bd10/15/2020:br1.29:efr1.19:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
dmi.product.family: IdeaPad Flex 5 14ARE05
dmi.product.name: 81X2
dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
dmi.product.version: IdeaPad Flex 5 14ARE05
dmi.sys.vendor: LENOVO

Revision history for this message
Daniel Szoboszlay (dszoboszlay) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Spencer Ahn (grvstick) wrote (last edit ):

Same here with PN51 RYZEN 5 5500U

final msg during suspend

systemd-shutdown[1]: Waiting for process: systemd-udevd, systemd-udevd

Could this be related to this issue?

https://github.com/systemd/systemd/issues/14140

Revision history for this message
Daniel Szoboszlay (dszoboszlay) wrote :

At least in my case it's not just a 90 second delay. I once left the laptop alone assuming it was suspended. Hours later it was still stuck in the state I described.

Revision history for this message
Thomas (t.c) wrote (last edit ):

Interesting, I have the "same" problem on Jammy Jellyfish (22.04).

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041

My suspend is also not working, freezes at the same state. Mainline kernel works.

Also a Lenovo Device.....

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.