Regression. Recent updates to cosmic broke hybrid-sleep

Bug #1825402 reported by Sergio Callegari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Recently, hybrid-sleep has been broken on cosmic.

Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: systemd 239-7ubuntu10.13
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Apr 18 19:25:05 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1952 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Notebook W740SU
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor
SourcePackage: systemd
UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago)
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W740SU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

Revision history for this message
Sergio Callegari (callegar) wrote :
tags: added: regression-update
Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for taking the time to report this issue and help to improve Ubuntu.

The most recent systemd update published to cosmic on 15Apr contains only changes to the network stack; this is unlikely to be the cause of a regression in systemctl hybrid-sleep.

http://launchpadlibrarian.net/419387036/systemd_239-7ubuntu10.12_239-7ubuntu10.13.diff.gz

When did you first experience this problem? With what version of systemd, and with what kernel version booted? Does downgrading to an earlier version of the systemd packages restore the previous behavior? Does booting to an earlier kernel restore the previous behavior?

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Sergio Callegari (callegar) wrote :

Trying to downgrade systemd seems to be impossible. As soon as I try an apt install --reinstall systemd=<some version> apt tries to remove half of the system...

I have noticed the issue in the past 15 days, I think, but only had time to look at it more closely right now.

Some notes:

- Trying to upgrade the kernel to latest 5.0.x via the mainline ppa seems to make no difference.
- Issue is somehow erratic. Happens like 70% of the time. In some rare occasions the systems seems to save state and then suspend correctly.
- When the issue occurs, the beginning of the hybrid sleep seems OK: big activity on disk to save the state, then the disk is powered down. However at this point, rather than suspending the system re-spins up the disk a couple of times and then halts.
System logs show a HuHu unexpected nmi, dazed and confused, but it is unclear to me if it is related to the broken suspend
- Plain suspend and plain hybernate seem to work.
- Hybrid suspend has worked for years on this 2013 Haswell laptop, which is a Shenker, in fact a Clevo, substantially identical to the System 76 Galago UltraPro.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please attack `journalctl -k -b -1` after the issue occurs.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

s/attack/attach

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
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.