Description of problem: System hangs on resume; desktop dimly visible Version-Release number of selected component (if applicable): kernel-3.10.3-300.fc19.x86_64 How reproducible: Always Steps to Reproduce: 1.Suspend machine to ram 2.Resume 3. Actual results: System comes up and redraws desktop, then hangs Expected results: Not hanging. Additional info: Hardware is Lenovo X200 laptop. Internal LCD monitor only. Works with kernel-3.9.11-200.fc18.x86_64. Fails with kernel-3.10.3-300.fc19.x86_64 and kernel-3.10.4-300.fc19.x86_64. Enabling "echo 1 > /sys/power/pm_trace" gives [ 0.516877] hash matches drivers/base/power/main.c:573 [ 0.516925] mei_me 0000:00:03.0: hash matches [ 0.516939] acpi device:09: hash matches in the kernel log after resume fails. acpi device:09 is \_SB_.PCI0.AGP_.VID_.CRT0 After rebooting from a hang, the screen backlight is dim and needs to be increased with the Fn-Home key combination.
Hang is pretty hard; capslock doesn't toggle, and it needs a long-press on the power to restart.
I'm having the same problem with my Thinkpad X301. The system hangs every time trying to resume from suspend mode (suspend to RAM). The problem started appearing after upgrading to Fedora 19 using fedup a couple of weeks ago. It seems that the problem exists in all Fedora 19 kernels that have been released so far after my upgrade (if memory serves, from 3.10.6 up to 3.10.9). So far I have "solved" the problem by using old kernel-3.9.5-301. My Fedora 18 installation worked fine even with the 3.10 kernel (either 3.10.3 or 3.10.4).
Created attachment 789613 [details] Kernel 3.10.9-200.fc19.x86_64 crash dump vmcore-dmesg.txt The file contains lots of mei_me related errors.
It seems that this problem is related to mei kernel module and was reported already as bug 917081. Fortunately bug 917081, comment 6 and bug 917081, comment 7 contain a workaround. To summarize, I did: echo -e "blacklist mei\ninstall mei /bin/true" > /etc/modprobe.d/mei.conf dracut --force and rebooted my machine. Suspend and resume seem to work now.
Here's a scratch build with all known mei patches backported. Please test and let us know if your issue is resolved (without the mei modules blacklisted). http://koji.fedoraproject.org/koji/taskinfo?taskID=5847415
It seems that suspend/resume works with this patched kernel (based on a few successful attempts) on my Thinkpad X301. I have the mei module loaded: (mael@shadow, ~) >>= lsmod | grep mei mei_me 18421 0 mei 76781 1 mei_me
OK, one more scratch build to test, this time with just the 4 patches submitted for the 3.10.y stable kernel. Thanks for testing, we appreciate it: http://koji.fedoraproject.org/koji/taskinfo?taskID=5854464
The patch kernel fixes the issue on my X200s. Thanks.
The new scratch build 3.10.9-200.3.fc19.x86_64 seems to work on my Thinkpad X301 too. I have suspended/resumed several times since switching to this kernel and no crashes or flood of mei error messages yet.
I've added the patches to Fedora git. Should be fixed in the next update. Thank you for testing.
kernel-3.10.10-200.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.10.10-200.fc19
kernel-3.10.10-100.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.10.10-100.fc18
Package kernel-3.10.10-200.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.10.10-200.fc19' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15545/kernel-3.10.10-200.fc19 then log in and leave karma (feedback).
kernel-3.10.10-200.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.10.10-100.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Fixed for me. Thanks all!