Description of problem: I seted up hibernation by timeout in Gnome Shell properties. And after waking up I've got very strange situation. Seems that workable only X-server I can open and close windows, but no reaction on command insertion in terminal- it hungs up after pressing enter and no reaction to clicking on buttons "Power off" or "Restart" just closing dialog windows. But most strange thing is if I type pm-suspend or pm-hibernate in system in normal state (after hard reset) I've got normal suspending to RAM or disk and normal waking up. Version-Release number of selected component (if applicable): 3.11.6-200.fc19.i686.PAE gnome-shell-3.8.4-2.fc19.i686 kmod-nvidia-3.11.6-200.fc19.i686-325.15-1.fc19.5.i686 xorg-x11-drv-nvidia-325.15-1.fc19.i686 akmod-nvidia-325.15-1.fc19.1.i686 xorg-x11-drv-nvidia-libs-325.15-1.fc19.i686 kmod-nvidia-3.11.6-200.fc19.i686.PAE-325.15-1.fc19.R.1.i686 How reproducible: every time Steps to Reproduce: 1. set up hibernate by timeot in gnome system settings 2. wait 3. try to wake up system 4. issue Additional info: bash-4.2$ lspci|grep VGA 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [ION] (rev a2) I don't know what logs you need. Please tell me about it. Regards, Dennis.
It that failed state after waking up after hibernation even extension "sensors" on panel doesn't show anything network is down too.
hi you filed this bug for a wrong component. hibernate is a java library, and you confused this one with pm-hibernate (pm-utils)
please select the right one
I think, that pm-utils is wrong component too, because I haven't problems with pm-suspend and pm-hibernate as I write earlier. I have problems with hibernation on timeout in F19 and GS3. I don't know a component to associate this bug with.
Additional very strange info: hibernate by pressing power button and from user-menu works pretty good.
Additional info: hibernate by pressing power button bring to the same state after waking up only after waiting some time after suspending. For example: yesterday I hibernated my machine by pressing power button and today I've got the state discribed above. But if I just hibernate and wakes up little after hard disk switched off machine wakes up pretty good.
This is probably not pm-utils. The pm-utils are only helper scripts for suspend/hibernate. There is no such thing like hibernate by timeout in pm-utils. Also currently all pm-utils tasks are done by systemd. For me this seems like kernel or nvidia driver bug (please note that nvidia binary drivers are not supported and it is very likely that this bug will be closed as wontfix), but reassigning to kernel.
Please try to recreate without the nvidia module installed.
Created attachment 819342 [details] pm-suspend.log Seems that with nouveau pm-hibernate works fine, but after pm-suspend (and systemctl suspend) machine never wakes up. After pressing power button there is no activity a long time, after 3-5 minuts hard disk starts to spin and continue cracks periodically , but screen doesn't switches on. Here is pm-suspen.log file. Is there any way to configure GS auto-suspend function to act like auto-hibernate?
I've got the same bug on my laptop with intel video card. Even sudo reboot doesn't work- reports that some devices is missing.
This is a cause: https://bugzilla.kernel.org/show_bug.cgi?id=61781
*********** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. 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 have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
Dennis, the patch you mention has made it in 3.12. So if you can confirm that 3.12.6 fixes things please go ahead and close this BZ thanks, Michele
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.