suspend.target: Job suspend.target/start failed with result 'dependency'.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
System fails to suspend, screen goes dark then turns back on. The lid won't suspend the system either.
Things I've tried:
turning off baloo, disconnecting from network.
From the logs:
I've observed this behavior a often enough during the past month that suspend is unpredictable. Luckily my computer has a suspend state indicator - some laptops don't.
A google search shows this to be a very old bug, earliest mentions are from 2014.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu5.3
ProcVersionSign
Uname: Linux 5.0.0-26-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Aug 20 17:34:30 2019
InstallationDate: Installed on 2018-11-15 (278 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: Upgraded to disco on 2019-04-27 (114 days ago)
dmi.bios.date: 03/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET98WW (2.48 )
dmi.board.
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQCTO1WW
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
Your ethernet driver or hw is preventing suspend:
[231201.406221] pci_pm_suspend(): e1000e_ pm_suspend+ 0x0/0x50 [e1000e] returns -2 suspend+ 0x0/0x140 returns -2
[231201.406226] dpm_run_callback(): pci_pm_
[231201.406230] PM: Device 0000:00:19.0 failed to suspend async: error -2
[231201.406291] PM: Some devices failed to suspend, or early wake event detected
This looks like maybe this kernel bug: /bugzilla. kernel. org/show_ bug.cgi? id=198519
https:/
Which maybe is bug 1865570. In any case, this is not a systemd bug, it's a kernel bug, so I'm changing the affected pacakge to the kernel.