Sign up ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

I used to have Fedora 14 installed on this HP Compaq 610, and the suspend feature worked fine. Now that I've installed Scientific Linux 6.1 suspend doesn't work anymore. How do I debug/fix it?

share|improve this question
Is this the shell suspend (<kbd>Cntl-z</kbd>) or the OS (sleep or hibernate)? – Arcege Dec 31 '11 at 21:06
@Arcege: I would assume he meant ACPI suspend, as it's become such a common problem these days. – TechZilla Jan 14 '12 at 9:04

3 Answers 3

up vote 9 down vote accepted

There are many ways to handle suspend and hibernate capabilities, many of the old methods are deprecated. This has made searching for solutions difficult, as it seems every solution is completely unrelated to the next. With that said...

The method currently recommended, advocated from, should be available for most recent distributions. I would first check if you have pm-utils installed, and if the included commands are operating as expected.

View if the package is installed, enter this command in terminal

rpm -qa | grep pm-utils

This should output the version you have installed. If you don't get the expected output, you need to install the package.

sudo yum install pm-utils

Once you get that verified, test out your ability to suspend.

sudo pm-suspend

If You don't suspend, and get no output why, check the your recent dmesg output

dmesg | tail -50

This should help get you started, once you get some clues its much easier to go further down the trail. Post back with comments regarding your results, I can get you through the rest.

share|improve this answer
I even installed pm-utils-devel. pm-suspend with root user does the same as with a normal user when it clicks in GNOME/menu->suspend->nothing, the machine just says "network is off", then it just waits and waits, etc.. i can't start anything after i'm trying to suspend. I will see the dmesg later, thank you! – LanceBaynes Jan 14 '12 at 10:01
The dmesg output will tell you what is happening behind the scene. More importantly, what in particular might be failing. O and BTW, you don't need the devel package. You only need them when compiling code, so feel free to purge. There are many direction to go from here, I just don't to send you barking up the wrong tree. – TechZilla Jan 14 '12 at 10:05
@LanceBaynes did you try running the pm-suspend commands from a shell and not through the GNOME menu? Try echo -n "mem" >/sys/power/state as root. Also if you're using acpi you can do a acpi_listen see what events are being generated e.g. upon closing the lid. – user13742 Jan 16 '12 at 14:10
WOW, wtf? I "echo -n "mem" >/sys/power/state" with the root user, and my actually suspended!!!! WOW. The only problem is now that when I'm doing this kind of suspend, then gnome-screensaver doesn't starts, and leaves me an unlocked PC. How to get around this? How can I make a script/anything so that a normal user could use this kind of suspend too? not just the root user? - and one more thing: THANK YOU! – LanceBaynes Jan 17 '12 at 18:57
@LanceBaynes: Its now working? ... I used to belive these kind of "surprise" Break/Repair's only happened with Widoze. Unfortunately, I've stopped believing that for a while. But... on the bright side, it does happen less often! And your suspend is working, so that's great news! – TechZilla Jan 17 '12 at 21:22

Try this as root:

PM_DEBUG=true pm-suspend

Then check /var/log/pm-suspend.log for hints on what might go wrong.

If you can suspend, but not resume, there's a good article on the Ubuntu wiki on how to debug this problem.

share|improve this answer

As is suggested by Mika, as root:

PM_DEBUG=true pm-suspend

Details within:


In this case you're looking for where

[...] service [servicename] suspend suspend success

ends, and

[...] service [servicename] suspend resume success

begins. Somewhere in between you may find calls returning error, at which point suspend is inhibited. In this case, you may have suspend changes being rolled back. Figure out what service call is throwing the error, open it up in vi and take a look at it.

I had the same problem where after installing xboxdrv on an Ubuntu 12.04, a call being made in a rule in /etc/pm/sleep.d/ was trying to stop a service that was never started or non-existent, in this case, xboxdrv. Turns out it could never be started in the first place, because there was no /lib/modules/uinput.ko module, because that module is merged into the kernel. This caused the case statement in /etc/pm/sleep.d/xboxdrv to throw an error when it case matches "suspend" to the call service xboxdrv stop. Prepending the line with # bypasses the statement, at the expense of having to unplug and re-plug your controller on suspend then resume.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.