Suspend not working on Ubuntu 16.04

[Tom Louwrier]

Suspend stopped working after upgrade from 15.10 to 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thomas 2349 F.... pulseaudio
Date: Fri Jun 24 13:32:38 2016
HibernationDevice: RESUME=UUID=d2b33e2c-e0ac-4439-8484-3c684ac09f84
InstallationDate: Installed on 2014-06-24 (730 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude 3540
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=6f195f6e-f9f2-4c1a-bc96-3bf4a5516379 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157.1
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-26 (58 days ago)
dmi.bios.date: 04/17/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 02RKKX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Latitude 3540
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Tom Louwrier, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Tom Louwrier (tom-louwrier)]

Hi Christopher,

I noticed the tag ;bios-outdated-a10'.
I'm aware of the newer bios being available, but although Dell offers this laptop with Ubuntu preinstalled and supported they somehow don't seem to offer a bios update that is not windoze dependent :-(

Downloaded kernel 4.6-rc7 from mainline as in your instructions and things are working fine. I can manually suspend and resume and when I close the lid it goes to sleep nicely. Fan cuts out, hdd spins down. When opening the lid I'm back where I was, so all works as it should.

Fan is a lot quieter too, so I guess it's using less power now as well.

regards
Tom

[penalvch (penalvch)]

Tom Louwrier, one may consult https://help.ubuntu.com/community/BIOSUpdate for help in updating the BIOS.

Despite this, the next step is to fully reverse commit bisect from kernel 4.4 to 4.6-rc7 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

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

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

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

[Tom Louwrier (tom-louwrier)]

hi again Christopher,

Found some time to test various kernels as indicated. Here are the results in correct chronological order:

0) 15.10 / kernel 4.2.0: last known good configuration
1) 16.04 / kernel 4.4.0: error found, bug reported
then tested:
2) v4.6-rc7-wily / 4.6.0: works as expected
3) v4.5-wily / 4.5.0: error found
4) v4.5.7-wily / 4.5.7: works as expected
5) v4.5-4-yakkety / 4.5.4: works as expected
6) v4.5-2-wily / 4.5.2: works as expected
7) v4.5-1-wily / 4.5.1: works as expected

My conclusion would be that the error was introduced in 4.4.0, persisted in 4.5.0 but got fixed in 4.5.1.

If you want me to test any versions between 4.2.0 and 4.4.0, let me know.
For now I'll be running one of the higher versions that work for me as daily driver.

cheers
Tom

[Tom Louwrier (tom-louwrier)]

Reading back I see I haven't really done all I should, but a complete commit bisect may well be beyond the limits of my knowledge and time.
On the other hand: last weekend I received an update to kernel 4.4.0 and that does seem to solve the issue. I can now suspend/resume on 4.4.0-31-generic as well as on 4.6.4 from mainline.

cheers
Tom

[penalvch (penalvch)]

Tom Louwrier, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595935/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.