Bugs:Suspend Failure

From openSUSE

Contents

Important

The default suspend framework has changed for openSUSE 10.2 from powersaved to pm-utils. There are different bug reporting instructions for both.

General information

Suspending notebooks is a somewhat experimental feature. It depends heavily on the used hardware if it works or not. Find or add some information at the page HCL/Laptops about your special hardware. Before reporting a bug, have a look at the documentation provided in /usr/share/doc/packages/powersave. The HTML version is in powersave_manual.html and the equivalent text version is in powersave_manual.txt. On older versions of SUSE, there are a number of README files such as README.suspend and README.suspend2ram and README.faq gives hints on what to do when common problems occur.

The articles in the Category Power Management might also give some useful hints, especially pm-utils, s2ram and ACPI Suspend debugging.

If you find a solution to an existing problem, file a bugreport that describes the problem, and what you had to do to solve the issue.

If you still cannot suspend after going through the documentation, file a bugreport and add the needed logfiles as attachments.

systems using pm-utils (openSUSE 10.2 and later)

The interesting files are

  /var/log/pm-suspend.log
  /var/run/pm-suspend


systems using powersaved (up to SUSE 10.1)

Most important logfiles regarding the powersave daemon are...

  /var/log/suspend2disk.log
  /var/log/suspend2ram.log
  /var/log/standby.log
  /var/lib/suspend2disk-state.resume
  /var/lib/suspend2ram-state
  /var/lib/standby-state.resume

for all systems

Clarify the versions of some important packages:

              powersave:  rpm -q powersave
               pm-utils:  rpm -q pm-utils
                suspend:  rpm -q suspend
                   dbus:  rpm -q dbus-1
                    hal:  rpm -q hal
                 kernel:  uname -r
suspend to RAM problems:  s2ram -n

More useful information is often found on the screen. If something is broken, it is usually some kernel driver, therefore trying with as little as possible modules loaded helps a lot. Also try to suspend from console, preferably without X running. Booting with init=/bin/bash, then swapon and starting suspend sequence manually usually does the trick. Then it is good idea to try with latest vanilla kernel. Manual suspending may be done with

powersave -U     set machine into suspend-to-disk
powersave -u     set machine into suspend-to-ram

For more information about powersave see the manual page powersave(8).

For suspend-to-RAM, things are complicated by video problems. After installing the package kernel-source, you find more information in the file /usr/src/linux/Documentation/power/video.txt. The s2ram-Page is also very helpful to debug suspend-to-RAM issues.