"Power off" required for resume from hybrid-sleep

[Steven Ward]

Due to issues with "waking from suspend", I have modified a few entries in /etc/systemd/logind.conf to use hybrid-sleep instead of suspend, namely 'HandleSuspendKey=hybrid-sleep', 'HandleLidSwitch=hybrid-sleep' and 'HandleLidSwitchDocked=hybrid-sleep'. On a few occasions now, I have closed my laptop lid while it is plugged it and when I return to it later, it does not resume on lifting the lid. The disk spins up and the fan runs as if the laptop was resuming but I am unable to do anything other than hold the power button down until it shuts down - much as I had to when I was having problems with suspend. When I hit the power button again and select the entry for Ubuntu in grub, the laptop boots to the login screen normally. When I log in, everything is just as it was when I originally closed the laptop's lid - basically "resuming" the way I had hoped. I do not believe that this is the intended behavior as I have had my computer resume from hybrid-sleep without powering it off in 16.04 and in 16.10 (I have not, that I know of, experienced this problem while on battery power). In case it is relevant, the current values of 'Suspend when inactive for' and 'When the lid closes' in Settings > Power are "Don't suspend" (for battery and plugged in) and "Suspend" (for battery and plugged in), respectively.
I will attach the output from 'cat /proc/version_signature' and 'lspci -vnvn' but I would like to add that 'sudo lspci -vnvn' sent 'pcilib: sysfs_read_vpd: read failed: Input/output error' to stderr, which was not redirected to the log file.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-30-generic 4.8.0-30.32
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: steven 4004 F.... pulseaudio
 /dev/snd/controlC0: steven 4004 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 10 22:06:19 2016
HibernationDevice: RESUME=UUID=891e7a47-9f8c-4fc9-9fe3-fe5c88ef2147
InstallationDate: Installed on 2016-11-23 (17 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: LENOVO 20347
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=b40d7383-45c3-4885-a1df-0e534eb44fef ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-30-generic N/A
 linux-backports-modules-4.8.0-30-generic N/A
 linux-firmware 1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 99CN21WW(V1.04)
dmi.board.asset.tag: Std
dmi.board.name: Lenovo Y40-70
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: Std
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Y40-70
dmi.modalias: dmi:bvnLENOVO:bvr99CN21WW(V1.04):bd03/24/2014:svnLENOVO:pn20347:pvrLenovoY40-70:rvnLENOVO:rnLenovoY40-70:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY40-70:
dmi.product.name: 20347
dmi.product.version: Lenovo Y40-70
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9

[Steven Ward (stevenward94)]

I did not notice this problem while using ubuntu 16.04.1 with - I believe - linux 4.4.3* (cannot remember exactly which release, sorry). I should be able to test the latest upstream kernel and see if that fixes the issue. I also wanted to add that I have found what I believe is a "trigger" for the issue, as I experienced it while on battery power today. I am fairly certain that the problem occurs when AC power is added or removed while my laptop is in hybrid-sleep mode (i.e. if I plug it in or unplug it while lid is closed). Not sure if that is of any help but I will still test the mainline and attempt to trigger - or not trigger - the problem so that I can update this report as soon as possible. Note, however, that if I am unable to trigger the issue, I will update with a comment but still wait a day or two to add a tag and change bug status. This is my first bug report so if there is a preferred protocol, like updating as soon as I think it's fixed and then changing later if necessary, please let me know.

Thanks,
Steven

[Steven Ward (stevenward94)]

I encountered the issue again after upgrading to the the latest upstream kernel[0]. After booting with the new kernel version, I verified outputs from `uname` (all as expected) and `dmesg | egrep -i 'error|critical|failed'` (as expected) and then closed my laptop lid while it was connected to AC power. It remained connected to AC power until approximately 4:35, at which point I removed the AC power and placed the laptop in my backpack without opening the lid. At about 5:45, I opened my laptop's lid while on battery power and encountered the same problem as before. I tried all possible orders of "closing the lid", "connecting AC power" and "reopening the lid" but none worked, so I powered off my laptop using the power-button and booted it to find ubuntu in the same state as it was when I last used it. Then, after about 30 minutes of use, I repeated that process EXCEPT that I connected my laptop to AC power BEFORE opening the lid, and this time I did not experience any issues with resuming. I checked the output of dmesg piped to egrep (same command I mentioned earlier) and there appear to be some new messages. I have attached the new output of that command with this comment. Only the first 3 lines (false-positives from 'errors=' flag on mount) were logged last night when I checked. The rest are new and I am fairly certain that the first 2 'rebind failed' entries were logged at about the time that I removed AC power from my laptop the first time (~4:35pm). I hope that some of this information is useful to you.

[0] https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.9.tar.xz

[penalvch (penalvch)]

Steven Ward, the next step is to fully commit bisect from kernel 4.4 to 4.8 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Steven Ward (stevenward94)]

I would like to start by apologizing to anyone who may have wasted time/effort on resolving this non-existent bug; I promise that I was not being intentionally misleading. I was finally able to find the root of my issue and, as it turns out, the issue was not the new bug I reported here but instead was a combination of the "resume from suspend" bug and systemd ignoring my settings in /etc/systemd/logind.conf when an external display is connected.

I have changed the status of this bug to "Invalid" for the reasons stated above. Again, I am sorry for any time and/or effort that was wasted resolving or monitoring an issue that was actually just my misunderstanding of my own system.

- Steven