Fail to resume after suspend on Ubuntu 17.10 with Radeon RX 480

[Veron Rado]

After upgrading to Ubuntu 17.10 I can't resume from suspend.
When I try to resume the system is frozen/extremely slow and unresponsive.

Apparently it is due to a bug in the amdgpu driver.
Here is the upstream kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=196615

This failure to resume is new for me.
I used get intermittent failure to suspend on 17.04 but I could always resume.

Linux 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1725788

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.

[Veron Rado (junket)]

@ Ubuntu Kernel Bot: Logs aren't really necessary. Go to the kernel bug URL and the patch is there.

[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.14 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.14-rc6

[Veron Rado (junket)]

Has that patch been included in v4.14-rc6 ?

[Veron Rado (junket)]

I tried kernel 4.14.0-041400rc6.
System still fails to resume on RX 480 with it.

When I was removing the test kernel the last four line were worrying:

 The link /vmlinuz is a damaged link
 Removing symbolic link vmlinuz
  you may need to re-run your boot loader[grub]
 The link /initrd.img is a damaged link
 Removing symbolic link initrd.img
  you may need to re-run your boot loader[grub]

The system has rebooted fine and I'm back on UBuntu 17.10's default 4.13.0-16-generic kernel but do I need to "re-run my boot loader [grub]" or is that something I can ignore? (I don't know how to re-run my boot loader.)

Here is the full kernel removal command output:

sudo apt-get remove linux-headers-4.14.0-041400rc6 linux-headers-4.14.0-041400rc6-generic linux-image-4.14.0-041400rc6-generic

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED
  linux-headers-4.14.0-041400rc6 linux-headers-4.14.0-041400rc6-generic linux-image-4.14.0-041400rc6-generic
0 to upgrade, 0 to newly install, 3 to remove and 0 not to upgrade.
After this operation, 314 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 232942 files and directories currently installed.)
Removing linux-headers-4.14.0-041400rc6-generic (4.14.0-041400rc6.201710230731) ...
Removing linux-headers-4.14.0-041400rc6 (4.14.0-041400rc6.201710230731) ...
Removing linux-image-4.14.0-041400rc6-generic (4.14.0-041400rc6.201710230731) ...
WARN: Proceeding with removing running kernel image.
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 4.14.0-041400rc6-generic /boot/vmlinuz-4.14.0-041400rc6-generic
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.14.0-041400rc6-generic /boot/vmlinuz-4.14.0-041400rc6-generic
update-initramfs: Deleting /boot/initrd.img-4.14.0-041400rc6-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.14.0-041400rc6-generic /boot/vmlinuz-4.14.0-041400rc6-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.13.0-16-generic
Found initrd image: /boot/initrd.img-4.13.0-16-generic
Adding boot menu entry for EFI firmware configuration
done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
 you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
 you may need to re-run your boot loader[grub]

[KlavKalashj (klavkalashj)]

The patch in the kernel bug report was submitted to Linux 4.14-rc7. I tested the mainline ubuntu kernel, and it now works like it should. I'm tagging this as 'kernel-fixed-upstream'. Will this patch be backported to the 17.10 kernel or will 17.10 be upgraded to Linux 4.14 once released?

[Kai-Heng Feng (kaihengfeng)]

This patch also sends to stable kernel, so it'll be automatically pulled into Ubuntu's kernel.

[Veron Rado (junket)]

Apparently fix is due in kernel 4.13.11.

https://bugzilla.kernel.org/show_bug.cgi?id=196615#c33

[Veron Rado (junket)]

Got the latest Ubuntu kernel update 4.13.0.17.18 (it hung during kernel installation and had real pain figuring out how to get out of that mess[1])

Trying to figure out how Ubuntu's kernel numbering matches regular Linux kernel numbering it would appears (from the README[2]) that Ubuntu 4.13.0.17.18 brings us up to Linux 4.13.8 ?
So its not fixed yet.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686107/comments/11
[2] /usr/share/doc/linux-image-4.13.0-17-generic/changelog.Debian.gz

[Veron Rado (junket)]

Great, this is fixed with the latest Ubuntu kernel update 4.13.0.19.20 (which is equivalent to 'regular' Linux kernel 4.13.13 I think[1]). Thanks.

[1] /usr/share/doc/linux-image-4.13.0-19-generic/changelog.Debian.gz

[Veron Rado (junket)]

I changed status to fix released. I'd close it but I can't see how to.