Description of problem: Since Fedora 20 update, my laptop can't resume after suspend. On resume, the waiting screen of GDM appears with animated arrows in the bottom of the screen but after 2~3 seconds, no more animations and my mouse is not working. I don't have keyboard leds, but my keyboard doesn't seem to work anymore. I can't access anymore to my laptop with ssh. If I'm fast enough, I can identify and access gnome-shell, but after 1~2 seconds, my laptop freeze with the same symptoms : no more mouse, no more keyboards & no more ssh access. Version-Release number of selected component (if applicable): Fedora 20 $ uname -r 3.12.5-302.fc20.x86_64 How reproducible: Steps to Reproduce: 1. Click on suspend in gnome shell or close my laptop screen. 2. Wake my laptop to resume, wait 2~3 seconds and my laptop freeze 3. Actual results: Laptop freezed Expected results: Laptop awaked
Hi, hard to say without more data. Would you be able to collect a crash dump when this happens? https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes If after the resume you quickly switch to a console tty (Ctrl-Alt-F3 for example) do you see any messages there? Thanks, Michele
(In reply to Michele Baldessari from comment #1) > Hi, > > Would you be able to collect a crash dump > when this happens? > > https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes > > If after the resume you quickly switch to a console tty (Ctrl-Alt-F3 for > example) > do you see any messages there? > > Thanks, > Michele Hi, I followed the How To, but the /var/crash directory is empty. I'll try to change config to write on a shared directory over network. May be I did something wrong, it's the first I try tu use kdump. I can't switch to tty, laptop freeze on keydown. If the session is just locked (without suspend), everything work fine. But on suspend, the laptop can't wake up normally. Thanks for you help, Loïc.
Hi Loïc, having a working kdump is always a good thing as it can help in other circumstances as well. Don't forget you can test if it is working or not without waiting for the resume hang ;) Without more infos it'll be hard. I'll see if other users have resume issues and see if they could be relevant here. Can you also upload the output of "lspci -vvv" and "dmidecode" as a file to this BZ so that we have a bit of an idea of what system this is? Thanks, Michele
Created attachment 848139 [details] Output from lspci -vvv
Created attachment 848140 [details] Output from dmidecode
I have what appears to be the exact same problem - when resuming after suspend neither mouse nor keyboard works, the animated arrows are shown once and the machine is otherwise completely unresponsive. The logs show absolutely nothing; no output at all. In my case the problem appeared before the upgrade to F20, so the regression has happened at version before that installed by F20. Output from lspci -vvv and dmidecode has been attached.
The recent update to 3.12.7-300 hasn't made any difference; it still hangs when resuming. The fan starts spinning after a couple of seconds which could indicate some kind of livelock? The part of /var/log/messages covering suspend and resume is as follows: Jan 15 15:46:47 localhost systemd: Starting Sleep. Jan 15 15:46:47 localhost systemd: Reached target Sleep. Jan 15 15:46:47 localhost systemd: Starting Suspend... Jan 15 15:46:47 localhost systemd-sleep: Suspending system... Jan 15 15:47:23 localhost systemd: Time has been changed Jan 15 15:47:23 localhost systemd-logind: Lid opened. Jan 15 15:47:23 localhost systemd: Time has been changed Jan 15 15:47:23 localhost systemd: Time has been changed Jan 15 15:47:24 localhost systemd-sleep: System resumed. Jan 15 15:47:24 localhost systemd: Started Suspend. Jan 15 15:47:24 localhost systemd: Service sleep.target is not needed anymore. Stopping. Jan 15 15:47:24 localhost systemd: Stopping Sleep. Jan 15 15:47:24 localhost systemd: Stopped target Sleep. Jan 15 15:47:24 localhost systemd: Starting Suspend. Jan 15 15:47:24 localhost systemd: Reached target Suspend. Jan 15 15:47:24 localhost systemd-logind: Operation finished. Jan 15 15:47:24 localhost NetworkManager[746]: <info> wake requested (sleeping: yes enabled: yes) Jan 15 15:47:24 localhost NetworkManager[746]: <info> waking up and re-enabling... Jan 15 15:47:24 localhost NetworkManager[746]: <info> WWAN now enabled by management service Jan 15 15:47:24 localhost NetworkManager[746]: <info> (p3p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 15 15:47:24 localhost NetworkManager[746]: <info> (p3p1): bringing up device. Jan 15 15:47:24 localhost NetworkManager[746]: <info> NetworkManager state is now DISCONNECTED Jan 15 15:47:24 localhost NetworkManager[746]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 15 15:47:24 localhost NetworkManager[746]: <info> (wlp2s0): bringing up device. Jan 15 15:48:28 localhost systemd[1]: systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) Jan 15 15:48:28 localhost systemd[1]: Running in initial RAM disk. Jan 15 15:48:28 localhost systemd[1]: Set hostname to <localhost.localdomain>.
I believe I'm experiencing this issue as well. I'm not running fedora 20 though, but the bug seems to be directly connected to the kernel version and not the fedora version. I have no issues when running a pre 3.12-kernel: 3.11.10-200.fc19.x86_64 But when I use one of the latest 3.12-kernels both suspend and hibernation are broken, below are the version I have tested on my system: 3.12.6-200.fc19.x86_64 3.12.7-200.fc19.x86_64 Also, the same issue seems to be affecting arch users and ubuntu users as well: https://bbs.archlinux.org/viewtopic.php?pid=1363702 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247654
Created attachment 852000 [details] lspci output
Created attachment 852001 [details] dmidecode output
As a data point, the arch issue listed above mentions that the problem has been seen on machines from Clevo (OEM'ed as System76 or Sager). Mine is a Clevo as well - output from inxi -M : Machine: Mobo: CLEVO model: W55xEU version: D02 Bios: American Megatrends version: 4.6.5 date: 11/02/2012
Same problem with an ASUS : Machine: Mobo: ASUSTeK model: UX32VD version: 1.0 serial: xxxxxxxxxxxxxx Bios: American Megatrends version: UX32VD.214 date: 01/29/2013
I have just upgraded to 3.12.8-300.fc20.x86_64 , and so far the problem seems to have been fixed - I've been able to succesfully resume from suspend.
I update the kernel to this version and the problem is still there.
My machine is also from Clevo: Machine: Mobo: CLEVO model: W55xEU version: D02 Bios: American Megatrends version: 4.6.5 date: 11/02/2012 As soon as I get the time I will try updating the kernel, and report back if it fixes the problem.
I have now updated my kernel to 3.12.8-200.fc19.x86_64, and standby and hibernation now works again on my machine.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Still works for me - as mentioned in comment 13 it started working again in 3.12.8-300
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.