REGRESSION: resume fails on recent 4.4.0-31, works on -28

[Reece]

Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31. The machine appears to suspend, and this is confirmed in syslog. However, when attempting resume, the screen is black and there is no indication of resumption. The machine automatically reboots within ~15 seconds. I did this three times with -31. Reverting to the -28 kernel restored suspend/resume.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: reece 2194 F.... pulseaudio
 /dev/snd/controlC0: reece 2194 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
InstallationDate: Installed on 2016-05-11 (65 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Precision 5510
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-28-generic N/A
 linux-backports-modules-4.4.0-28-generic N/A
 linux-firmware 1.157.2
Tags: xenial
Uname: Linux 4.4.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1603283

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

apport information

[Reece (reece)]

Disregard comment #3... the endpoint seems to be working now.
Let me know if other info would help.
Note that the apport info was collected with 4.4.0-28 after rebooting, not the -31 that's causing issues.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.4.15

[Reece (reece)]

Joseph- I went back to -31 and have tried it for 2 days, including at least 10 successful suspend/resume cycles. I cannot reproduce the original issue.

I have no explanation for why my previous repeatable observations are no longer repeatable, although I did make a couple minor and (seemingly) unrelated bios setting changes (e.g., fn key lock).

I'm going to mark the issue as invalid. Sorry for the goose chase.