suspend-target and systemd-suspend.service hang on resume and blocks shutdown/reboot

Bug #2054861 reported by M. Kurt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happens only after I connect my Toshiba FireTV via HDMI. I don't need to be using the TV. If I have connected TV just once it is enough to trigger this bug. Laptop goes to sleep just fine but when it wakes up from sleep I see 5 services when I execute
$ systemctl list-jobs

JOB UNIT TYPE STATE
7348 nvidia-resume.service start waiting
7236 suspend.target start waiting
7346 grub-common.service start waiting
7237 systemd-suspend.service start running
7241 grub-initrd-fallback.service start waiting

In this state, I have to cancel suspend-target which in turn cancels
 7346 grub-common.service start waiting
 7237 systemd-suspend.service start running
 7241 grub-initrd-fallback.service start waiting

Then, I have to cancel cancelling systemd-suspend.service which cancels
 7348 nvidia-resume.service start waiting

I use the laptop without issues but then if I need to shut it down or reboot, system gets stuck after logging out of X. I end up doing a REISUB.

This only happens if I connect to TV via HDMI.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Feb 23 19:32:08 2024
InstallationDate: Installed on 2023-11-04 (112 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash amd_pstate=passive vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2023-12-10 (75 days ago)
dmi.bios.date: 12/28/2023
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.41
dmi.modalias: dmi:bvnLENOVO:bvrM3CN41WW:bd12/28/2023:br1.41:efr1.41:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO

Revision history for this message
M. Kurt (paralaks) wrote :
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.