Reboot when resume from suspend

[tim474]

When I resume my computer from suspend2ram, after about 2 seconds it shutdowns and after about 3 seconds swithces on, and system starts to boot from GRUB as it was poweroff.

But if I resume my computer right away after it was suspended, it resumes properly. I occur this problem if some amount of time passed between suspend and resume.

And I didn't reproduce this problem when lightdm was stopped (but the screen is black after resume, but I can login via SSH). But with launched X Server the problem occurs both with nouveau and Nvidia proprietary driver.

There is not this problem on Ubuntu 14.04 (it is installed on this computer too but without madm and root partition encryption).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.64.68
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tim 2077 F.... pulseaudio
CurrentDesktop: XFCE
Date: Fri Mar 3 02:43:35 2017
EcryptfsInUse: Yes
IwConfig:
 tun0 no wireless extensions.

 lo no wireless extensions.

 enp4s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. EP43-DS3L
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=UUID=77b30501-4b3e-4223-8e1c-ee51e9f214d7 ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-64-generic N/A
 linux-backports-modules-4.4.0-64-generic N/A
 linux-firmware 1.157.8
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: EP43-DS3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd07/08/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP43-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-DS3L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP43-DS3L
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.10 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.10.1

[tim474 (tim474)]

Yes, with kernel 4.10.1-041001-generic there is the same problem.

[Chris Roth (chris-roth)]

I believe I have the same issue.

Kernel 4.10.1 reboots, but kernel 4.10.0 does not suffer from the same
problem.

I also notices this problem at some point in the 4.8.x series for a
couple of the patches, around 5-6, but then it got fixed and wasn't an
issue for me anymore.

If I can output anything to help debug, let me know.

I'm running a dell xps15 9550, 16.10.

Chris

[tim474 (tim474)]

I tested with 4.10.0, and I have the same problem.

[Kai-Heng Feng (kaihengfeng)]

I'd say nvidia driver is somewhat necessary for new cards, this can be done by

$ sudo apt install nvidia-367

Reboot and test if suspend works.

[tim474 (tim474)]

I'll try, but on Ubuntu 14.04 suspend works with 340. It's not new card, it's about 10 years old. And there wasn't this problem with this card on previous Ubuntu versions.

[Kai-Heng Feng (kaihengfeng)]

Oops, I misread 9800 as 980. Sorry.

So we need to know what's the result of the following...
Executes these commands as root:
# echo devices > /sys/power/pm_test
Then suspend and check if the issue happens. If not

# echo platform > /sys/power/pm_test
Suspend and check again. If not

# echo core > /sys/power/pm_test
Do same as above. And see if this will cause the issue.

[tim474 (tim474)]

I tested with another video card (GeForce 8400 GS), and suspend works normally.

[Kai-Heng Feng (kaihengfeng)]

Can you make persistent log by
$ sudo mkdir -p /var/log/journal
$ sudo systemd-tmpfiles --create --prefix /var/log/journal

Then reboot the system, and add "drm.debug=0x0e" to kernel parameter?
After the resume failed, attach the output of `journalctl -b -1`, thanks!

[Jean-Pierre van Riel (jpvr)]

No sure if this will help, but there are plenty of debian bugs related to this to check

If you are relying on the `resume=` kernel parameter with /etc/default/grub, that might well be ignored. According to the message below, there are various bugs in upstream debian (and I'm not sure if Ubuntu patches/changes this):

https://lists.debian.org/debian-kernel/2017/04/msg00348.html

After installed, I noted `/etc/initramfs-tools/conf.d/resume` uses a UUID, but I had issues getting resume to work, possibly because I recreated my swap partition. As far as I could tell, Ubuntu 16.04.2 LTS seems to ignore the `resume=` kernel parameter as a UUID or LABEL.

`apt-cache show initramfs-tools` shows Ubuntu 16.04.2 LTS currently has `Version: 0.122ubuntu8.8`, so it should be free of the bug/regression that caused UUID or LABEL to be ignored in `conf.d/resume`

[Jean-Pierre van Riel (jpvr)]

Apologises, I think I'm conflating a resume from hibernate issue vs a resume from suspend issue, so the previous comment is probably not that relevant.