fedora will not hibernate or suspend

Nick Name · #1 25th April 2010, 08:03 PM

Hello,

my system will not go to suspend, if I was logged on. It will turn off the fan and harddrive and than nothing will happen. I can't stroke a key, it will only blink on a blank screen. So I have to switch off my system by holding down the power-key for a while. But if I was never loggod on, I can suspend properly on the welcomescreen. In my pm-suspend.log there are no useful informations.

Thanks in advance!

---------- Post added at 09:03 PM CDT ---------- Previous post was at 07:04 PM CDT ----------

I have tried to suspend with debug-flag, maybe someone can see the fault.

Quote:

++ set -a
++ PM_UTILS_LIBDIR=/usr/lib/pm-utils
++ PM_UTILS_ETCDIR=/etc/pm
++ PM_UTILS_RUNDIR=/var/run/pm-utils
++ PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/lib/pm-utils/bin
++ PM_LOGFILE=/var/log/pm-suspend.log
++ TEMPORARY_CPUFREQ_GOVERNOR=performance
++ LOCKDIR=/var/run/pm-utils/locks
++ STORAGEDIR=/var/run/pm-utils/pm-suspend/storage
++ NA=254
++ NX=253
++ DX=252
++ PM_FUNCTIONS=/usr/lib/pm-utils/functions
++ LC_COLLATE=C
++ HIBERNATE_MODE=
++ HIBERNATE_RESUME_POST_VIDEO=no
++ SLEEP_MODULE=kernel
++ SUSPEND_MODULES=
++ HOOK_BLACKLIST=
++ ADD_PARAMETERS=
++ DROP_PARAMETERS=
++ PARAMETERS=/var/run/pm-utils/pm-suspend/storage/parameters
++ INHIBIT=/var/run/pm-utils/pm-suspend/storage/inhibit
++ PM_CMDLINE=
++ BEFORE_HOOKS=
++ MODULE_HELP=
++ SUSPEND_MODULE=
++ HIBERNATE_MODULE=
++ SUSPEND_HYBRID_MODULE=
++ '[' -f /usr/lib/pm-utils/defaults ']'
++ . /usr/lib/pm-utils/defaults
++ '[' -f /usr/lib/pm-utils/pm-suspend.defaults ']'
++ set +a
++ for cfg in '"${PM_UTILS_ETCDIR}"/config.d/*[!~]' '"${PM_UTILS_ETCDIR}/${STASHNAME}.config.d"/*[!~]'
++ '[' -f '/etc/pm/config.d/*[!~]' ']'
++ continue
++ for cfg in '"${PM_UTILS_ETCDIR}"/config.d/*[!~]' '"${PM_UTILS_ETCDIR}/${STASHNAME}.config.d"/*[!~]'
++ '[' -f '/etc/pm/pm-suspend.config.d/*[!~]' ']'
++ continue
++ . /usr/lib/pm-utils/functions
+++ '[' true = true ']'
+++ set -x
+++ command_exists service
+++ type service
+++ return 0
++ command_exists hal-get-property
++ type hal-get-property
++ return 0
+++ hal-get-property --udi /org/freedesktop/Hal/devices/computer --key system.chassis.type
++ export CHASSIS_TYPE=Notebook
++ CHASSIS_TYPE=Notebook
++ '[' kernel = auto ']'
++ for mod in '$SLEEP_MODULE'
++ mod=/usr/lib/pm-utils/module.d/kernel
++ '[' -f /usr/lib/pm-utils/module.d/kernel ']'
++ . /usr/lib/pm-utils/module.d/kernel
++ '[' -z '' ']'
++ grep -q mem /sys/power/state
++ SUSPEND_MODULE=kernel
++ '[' -z '' ']'
++ '[' -f /sys/power/disk ']'
++ grep -q disk /sys/power/state
++ HIBERNATE_MODULE=kernel
++ id -u
+ '[' 0 '!=' 0 ']'
+ try_lock pm-suspend.lock
+ mkdir -p /var/run/pm-utils/locks
+ local lock=/var/run/pm-utils/locks/pm-suspend.lock
+ return 0
+ trap remove_suspend_lock 0
+ rm -rf /var/run/pm-utils/pm-suspend/storage
+ mkdir -p /var/run/pm-utils/pm-suspend/storage
+ '[' -f /var/run/pm-utils/pm-suspend/storage/parameters ']'
+ echo ''
+ add_parameters
+ remove_parameters
+ local p
+ '[' '' = all ']'
+ echo ''
+ grep -vxFf /var/run/pm-utils/pm-suspend/storage/parameters.rm /var/run/pm-utils/pm-suspend/storage/parameters
+ cp -f /var/run/pm-utils/pm-suspend/storage/parameters.new /var/run/pm-utils/pm-suspend/storage/parameters
+ update_parameters
+ '[' -f /var/run/pm-utils/pm-suspend/storage/parameters.new ']'
++ get_parameters
++ cat /var/run/pm-utils/pm-suspend/storage/parameters
+ export PM_CMDLINE=
+ PM_CMDLINE=
+ rm -f /var/run/pm-utils/pm-suspend/storage/parameters.new
+ '[' 0 -gt 0 ']'
+ command_exists check_suspend
+ type check_suspend
+ return 0
+ command_exists do_suspend
+ type do_suspend
+ return 0
+ check_suspend
+ '[' -n kernel ']'
+ case "$METHOD" in
+ ACTION=suspend
+ REVERSE=resume
+ init_logfile /var/log/pm-suspend.log
+ '[' -z /var/log/pm-suspend.log ']'
+ '[' -h /var/log/pm-suspend.log ']'
+ '[' -f /var/log/pm-suspend.log -a '!' -O /var/log/pm-suspend.log ']'
+ export LOGGING=true
+ LOGGING=true
+ exec

shri19 · #2 26th April 2010, 11:00 AM

I have the same problem with my laptop and the simplest way to solve this is run system update. Once you do that some of the silly problems with these will solve by themselves...

Nick Name · #3 27th April 2010, 05:27 PM

If you mean with "system update" "yum update", then I have done it many times, without any effect.

---------- Post added at 06:26 PM CDT ---------- Previous post was at 09:50 AM CDT ----------

I have tried the LiveCD, from which I also installed. And this will also not suspend. So I thing it is a general Bug in this configuration. Could someone confirm this?

My Modell is Lenovo 3000 N200 0769BFG with Fedora 12.

---------- Post added at 06:27 PM CDT ---------- Previous post was at 06:26 PM CDT ----------

Some similar modell is also okay.

Nick Name · #4 1st May 2010, 07:15 PM

Today I have tried to suspend and it works. Strange behaviour, but I will test it, if it will be reliable.

BugRocks1 · #5 2nd May 2010, 02:06 AM

http://www.mjmwired.net/kernel/Docum...-debugging.txt

---------- Post added at 05:06 PM CDT ---------- Previous post was at 05:04 PM CDT ----------

http://www.columbia.edu/~ariel/acpi/acpi_howto.txt

wt6g · #6 14th May 2010, 01:39 PM

I have now traced this problem on my toshiba laptop to Open Office. It's easy to repeat.

If I do a fresh boot, FC 12 hibernates and restores just fine.

If I do a fresh boot, and then start open office write and do nothing with it (ie just start it so a blank document appears) from that point on FC12 will not hibernate.

I do not know what Open Office does to FC12, but it does not crash (otherwise it would get reported as a bug on my system) but this seems to be the reason FC12 has trouble hibernating. There may be other programs that cause this problem too, but I've at least identified one procedure that is repeatable.

THIS IS AN IMPORTANT BUG. It's causing a lot of us to leave computers on 24/7 because FC12 won't reliably hibernate. Given the number of installations of fedora if 10% of the people using it are doing what I'm doing we're causing a lot of resource depletion and pollution!

/Len

BugRocks1 · #7 14th May 2010, 04:08 PM

Gnome (and probably KDE) have a feature to send signals to disable suspend modes.

It is done to allow video players for example to send messages to gnome to say "hey I alive here, don't blank the screen".

http://live.gnome.org/GnomePowerMana...-suspending.3F

Quote:

Then you can use the Inhibit() and UnInhibit() DBUS methods built into the newest versions of gnome-session

There may be a way to monitor those methods using dbus-monitor but I only know how to monitor signals for now so I can't help there sorry.

jorymil · #8 15th July 2010, 06:20 AM

(FC 13 on Dell Latitude X1)

I'm having the same problem on my end, and as others have mentioned, I can suspend prior to logging into GNOME, but once I log in and try suspending, or log out and try suspending, my system does a hard crash. /var/log/pm-suspend.log didn't contain any useful info that I could see, so I experimented a bit.

Comparing the output of lsmod before logging into GNOME, while logged into GNOME, and after logging out, I found three modules that were not loaded beforehand, but stayed loaded afterwards:

fat
vfat
fuse

Guess what? I had my SD card loaded the whole time. Looks like GNOME mounts the SD card (as it should), but it stays mounted after logout (also probably smart, as you might log in again).

A quick workaround script (use at own risk):

Code:

#!/bin/sh
umount $(df | grep mmc | awk '{print $6}')
modprobe -r vfat fat fuse

I'll try to find an actual fix (why do these modules make pm-suspend crash the system?), but can't say it's super-high on my list of priorities right now. It's annoying, but I can live with it, since this is a work laptop and I don't use SD cards that often.

Let me know if this is helpful!

John

Zanpactou · #9 15th July 2010, 07:21 AM

Bug report it.

Thanks,
Zanpactou

Nick Name · #10 15th July 2010, 12:54 PM

@jorymil

Your hint will fix the issue. But isn't a simple unmounting the SD-Card enough? I will try it later myself and report.
I have never noticed the relation with the SD-Card, so I can't say anything if this issue is happend with all kernels.

Thanks for your hint!

---------- Post added at 01:54 PM CDT ---------- Previous post was at 11:17 AM CDT ----------

A simple unmounting before suspending your computer, worked. The Card will be remounted, if you wake up your computer.