@Matalak - took a look at your redhat bugzilla link and the behaviour that todd describes is an exact match! Curiously enough, todd seems to be using a standard PC setup rather than a laptop.
At the end of the redhat bugzilla post Laura Abbott suggests that todd files a bug report with the upstream maintainers at bugzilla.kernel.org and when I searched for suspend bugs I found: https://bugzilla.kernel.org/show_bug.cgi?id=199025 (last entry was 10th May) A few thoughts: - kernel bug 199025 'Suspend hangs. Never fully suspends and impossible to return to running state.' has been filed against this issue. The 'Status: NEEDINFO' and the last comment on it being from the 10th of May is not particularly encouraging :( - I'm not entirely sure how all of this works (this is the first bug report that I've filed) but my initial thoughts were to get anyone with suspend issues to add to the bug report and list their hardware, so that there might be a clearer picture of how many people this was affecting and what machines seem to be affected. - I assumed that nobody would pay any attention to this seemingly 'edge- case hardware combination issue' until it was ascertained that it affected a good many more people. - I'm pleased to see that I was incorrect in my assumption and that as far as I can tell from an email (think I got added to a list for starting the bug) a canonical team member, Kai-Heng Feng, has been in touch with a kernel.org developer about the kernel bisection report, who has made a patch to test. So I think what happens is that users report bugs to their specific distro (i.e Ubuntu, Fedora, Debian) and the distro developers/maintainers can then narrow it down and report the problem to the maintainers of the affected part of the project. In this case, what seems to be a kernel-related problem is reported to the kernel maintainers by the Ubuntu developers. Since it only seems to be affecting a few specific hardware combinations, it means any fixes will have to be tried out by someone with the 'problem hardware', who can then report back whether the issue is fixed. (I don't mind testing things out but don't really know what I'm doing, so if there is a patch to try I wouldn't know how to apply it.) I'm very tempted to let the bugzilla.kernel.org folks know that bug #199025 is affecting us too, but the Ubuntu maintainers might be in touch with them already. ** Bug watch added: Linux Kernel Bug Tracker #199025 https://bugzilla.kernel.org/show_bug.cgi?id=199025 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
