Created attachment 274905 [details] dmesg output from not_able_to_suspend (4.15.10 from updates-testing repository) kernel For the past few weeks, suspend doesn't seem to complete on a ThinkPad p50. Previously, it was working fine. When I initiate the suspend, the laptop monitor + second monitor go blank and it appears that the system has (almost fully suspended), except that the power button light is not flashing, as it should after suspending (instead it is solid on). If I attempt to resume, pressing the power button is ignored. Workaround: The workaround is to hold the power button down until full power down. After that, I am able to do a full boot cycle. Another workaround is to to install older 4.14.18-300.fc27.x86_64 kernel. Version-Release number of selected component (if applicable): Occurs with 4.15.8-300.fc27.x86_64 How reproducible: Recreates every time on ThinkPad p50 Steps to Reproduce: 1. Boot Fedora (currently using GNOME with Wayland disabled). 2. Click on Suspend in menu. 3. wait for power button to flicker but that will not happen, it stays solid on.
Created attachment 274907 [details] dmesg output for able_to_suspend (4.14.18)
> Version-Release number of selected component (if applicable): > > Occurs with 4.15.8-300.fc27.x86_64 Yes, I have seen this occurring repeatedly with 4.15.8 as well as 4.15.10.
Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1558023 I see this problem, but with testing I've found that "echo mem > /sys/power/state" suspends and resumes with no problem. It's only when using the suspend key or window manager suspend button that it hangs. Also, a clean Fedora install with less packages installed but with the same kernel doesn't have the problem. The strange thing is that a 4.14 kernel on the install with the problem does work, so there seems to be some kernel interaction involved, but not directly with the suspend function.
I recently found this problem on another laptop which is AMD, no NVidia or Intel. I also found that the /sys/power/state option caused the hang on my laptop once as well, so I've gone back to 4.14 there.
People have reported similar issue at https://bugzilla.kernel.org/show_bug.cgi?id=199025#c17 "In my case, I have an NVIDIA Quadro FX 880M in my DELL M4500 laptop and am using the nouveau drivers. I have attempted a git bisect between kernel versions 4.14.18 and 4.15.2 and reached the following: d7722134b8254bcee6086230723814cddf9ab54b is the first bad commit commit d7722134b8254bcee6086230723814cddf9ab54b Author: Ben Skeggs <bskeggs@redhat.com> Date: Wed Nov 1 03:56:20 2017 +1000 drm/nouveau: switch over to new memory and vmm interfaces Signed-off-by: Ben Skeggs <bskeggs@redhat.com> " Could you please first check if the suspend/resume is ok w/o any graphic driver(nouveau, eg) loaded, or try reverting the commit above and recompile the upstream kernel(not the Fedora customized kernel)?
I have the same issue on an Acer E13 laptop (ES1-311-C4Q6). Works fine on 4.14.18, no joy on any later kernel. No nouveau: # lsmod | grep i915 i915 1908736 6 i2c_algo_bit 16384 1 i915 drm_kms_helper 196608 1 i915 drm 434176 5 i915,drm_kms_helper video 45056 2 acer_wmi,i915
Not sure if this helps, working config: # modinfo -F filename `lshw -c video | awk '/configuration: driver/{print $2}' | cut -d= -f2` /lib/modules/4.14.18-300.fc27.x86_64/kernel/drivers/gpu/drm/i915/i915.ko.xz Anything newer does not work. I am running F28 and KDE Plasma.
How about reverting 08810a4119aaebf6318f209ec5dd9828e969cba4 and try again?
I upgraded to Fedora 28 (kernel-4.16.11-300.fc28.x86_64) and have been able to suspend the OS 3 times so far.
I experience the same problems with 4.15.0-22-generic on X1 Carbon, running an up to date Kubuntu bionic (18.04) Suspend by closing lid has so far not worked for me. Suspend by systemctl suspend sometimes works. Suspend by echo mem > /sys/power/state has worked a couple of times so far. Booting from 4.13 worked alright.
(In reply to Scott Marlow from comment #9) > I upgraded to Fedora 28 (kernel-4.16.11-300.fc28.x86_64) and have been able > to suspend the OS 3 times so far. have you tried more times? is the problem gone with later kernel release? It would be nice if you can try the latest upstream kernel instead.
(In reply to mkaelb from comment #10) > I experience the same problems with 4.15.0-22-generic on X1 Carbon, running > an up to date Kubuntu bionic (18.04) > > Suspend by closing lid has so far not worked for me. > Suspend by systemctl suspend sometimes works. > Suspend by echo mem > /sys/power/state has worked a couple of times so far. > > Booting from 4.13 worked alright. mkaelb, the problem you're experiencing may or may not be the same problem. So first please confirm the problem still exists in the latest upstream kernel, say 4.17-rc7, and then please confirm the problem can not be reproduced using "echo mem > /sys/power/state".
>have you tried more times? I have successfully suspended about 10 times since upgrading to the newer Fedora 28 release. > is the problem gone with later kernel release? I was previously using Fedora 27 and upgraded to Fedora 28 (now up to kernel version 4.16.12). >It would be nice if you can try the latest upstream kernel instead. I can definitely try 4.17-rc7, I found https://mirrors.kernel.org/fedora/development/rawhide/Everything/x86_64/os/Packages/k/, which contains 4.17-rc7 modules but are for the next Fedora release (Fedora 29). For example, I see file kernel-4.17.0-0.rc7.git1.1.fc29.x86_64.rpm listed. Is it typical to try newer kernel modules that are written for a newer distribution release?
There should not be a problem with installing a kernel from a newer release. You can also go to https://koji.fedoraproject.org/koji/packageinfo?packageID=8 to find various kernel builds.
Thanks, I installed 4.17.0-0.rc7.git1.1.fc29.x86_64 and restarted. I was able to repeatedly (OS) suspend four times without trouble. uname -a Linux smarlowp50.localdomain 4.17.0-0.rc7.git1.1.fc29.x86_64 #1 SMP Wed May 30 16:05:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux RPMs that I installed: kernel-4.17.0-0.rc7.git1.1.fc29.x86_64 kernel-core-4.17.0-0.rc7.git1.1.fc29.x86_64 kernel-devel-4.17.0-0.rc7.git1.1.fc29.x86_64 kernel-headers-4.17.0-0.rc7.git1.1.fc29.x86_64 kernel-modules-4.17.0-0.rc7.git1.1.fc29.x86_64 kernel-modules-extra-4.17.0-0.rc7.git1.1.fc29.x86_64
I installed 4.17-rc7 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/ linux-headers-4.17.0-041700rc7-generic_4.17.0-041700rc7.201805272130_amd64.deb linux-image-unsigned-4.17.0-041700rc7-generic_4.17.0-041700rc7.201805272130_amd64.deb linux-modules-4.17.0-041700rc7-generic_4.17.0-041700rc7.201805272130_amd64.deb and can confirm that the system suspends with "echo mem > /sys/power/state". Tried four times. System resumes again as it should, by hitting Fn. Can also confirm that the system suspends by "systemctl suspend", and resumes. As well as by closing the lid, and opening it again.
(In reply to mkaelb from comment #16) > I installed 4.17-rc7 from > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/ > > linux-headers-4.17.0-041700rc7-generic_4.17.0-041700rc7.201805272130_amd64. > deb > linux-image-unsigned-4.17.0-041700rc7-generic_4.17.0-041700rc7. > 201805272130_amd64.deb > linux-modules-4.17.0-041700rc7-generic_4.17.0-041700rc7.201805272130_amd64. > deb > > and can confirm that the system suspends with "echo mem > /sys/power/state". > Tried four times. System resumes again as it should, by hitting Fn. > > Can also confirm that the system suspends by "systemctl suspend", and > resumes. > As well as by closing the lid, and opening it again. Sorry, this should have been in reply to Zhang Rui comment 12.
Given that the problem can not be reproduced for now, bug closed. Please feel free to reopen it if you run into the same problem again.