Description of problem: Configured serial console by putting "console=ttyS0,115200" into the boot line. pm-hibernate then runs through hibernate and thaw hooks without attempting to hibernate. It appears that: remove_suspend_lock 200 dbus-send --system --print-reply \ --dest=org.freedesktop.Hal \ --type=method_call \ /org/freedesktop/Hal/devices/computer \ org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate does not work. No idea why. Version-Release number of selected component (if applicable): pm-utils-0.99.3-6.el5.19 How reproducible: everytime
Is dbus running properly on the system?
# ps -fe | grep dbus dbus 2132 1 0 Dec18 ? 00:00:00 dbus-daemon --system If I run the dbus-send command by hand in my ssh session, it goes into hibernate. Is this an authorization issue? dbus need to be running on the console, but it isn't with the serial console enabled?
Created attachment 327496 [details] strace of dbus-daemon while pm-hibernate is run
(In reply to comment #0) > Configured serial console by putting "console=ttyS0,115200" into the boot line. > pm-hibernate then runs through hibernate and thaw hooks without attempting to > hibernate. Does this also happen with pm-suspend in your case?
# pm-suspend Error: kernel cannot suspend to ram.
Created attachment 329693 [details] pm-suspend.log It turns out running PM_DEBUG=true pm-suspend provides an interesting log file. I'm a little dead at the moment but I'll try taking a closer look at it tomorrow.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
I'm no longer using EL5
Thanks for reply, closing WONTFIX for RHEL 5.