Ubuntu 16.04 suspend works only twice or thrice in a row, freezes at next attempt

[Marek]

This problem was introduced with Ubuntu 16.04 or rather with kernel 4.4; I never had this problem on Ubuntu 14.04 and kernels from 3.x line.

Suspend works only twice in a row, sometimes three times, the next attempt of suspending results in basically dead machine but system fans are spinning, monitor back light is on etc. My problem is similar to #1634446, #1566302, #1574125, symptoms are basically the same.

I tried more recent kernels: 4.6, 4.8, but its all the same. The problem existed after upgrading my system from 14.04 to 16.04 and after fresh installation of 16.04. If I recall correctly the problem existed with proprietary graphic drivers (nvidia-367 for my GTX770) and also for default open source graphic drivers. I have an encrypted home folder, 8GB of RAM and 16GB swap partition.

WORKAROUND: In the systemd-suspend.service file modify ExecStart line to look like:
ExecStart=/usr/bin/acpitool -s

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-47-generic 4.4.0-47.68
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: marek 1962 F.... pulseaudio
 /dev/snd/controlC0: marek 1962 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 11 23:45:45 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=efc7d3d0-4d67-4835-acc7-651d70791aed
InstallationDate: Installed on 2016-11-06 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lo no wireless extensions.

 enp3s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P67-DS3-B3
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=a4f5390e-8590-4868-a259-6bafb52a2901 ro quiet splash nomodeset vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.157.4
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: P67-DS3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67-DS3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67-DS3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P67-DS3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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-rc5

[Marek (marecki)]

Unfortunately the bug exists on the newest mainline kernel. It was hard to test because it made my system very unstable (which is expected) and I had trouble to get couple straight wake-ups from suspend to be able to tell if it freezes like it did before. But it did freeze on third or fourth attempt of suspending like on default kernel.

[Marek (marecki)]

I'm attaching crash log from one of the occurrences of the problem

[penalvch (penalvch)]

Marek Stasiak, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.9) as it is released.

Could you please advise?

[Marek (marecki)]

I installed the latest 4.9 kernel (4.9.0-040900-generic #201612111631) and tested both default open source nouveau driver and proprietary nvidia-367 driver. Unfortunately problem still persists but now I can do three successful suspends instead of two :))

I think my only way to get rid of this issue is to upgrade to newer motherboard... The current is quite old. Maybe I'll do another test with new Ubuntu (let's say 17.04 daily build) on another drive without encrypted home folder and see if there is the same problem. I'll let you know. Thanks

[penalvch (penalvch)]

Marek Stasiak, the latest mainline kernel since Dec. 26 is 4.10-rc1.

Could you please advise?

[Launchpad Janitor (janitor)]

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

[Marek (marecki)]

I had too many problems with kernel 4.10 to be able to test this, so I just let this report expire. Anyway, I kinda gave up with investigation.

One thing I discovered, and this is to people who may be reading this and looking for a solution, was that suspend with 'sudo acpitool -s' command was working very good! So I just edited my systemd-suspend.service file and modified ExecStart line to look like this:

ExecStart=/usr/bin/acpitool -s

and thats it. Suspend is now working as it should be.