Bugs:Suspend Failure
From openSUSE
| Revision as of 23:35, 10 February 2007 Seife (Talk | contribs) add Category:Power_Management � Previous diff |
Current revision Seife (Talk | contribs) Update to current state, remove useless package versions request, mention to not attach hwinfo logs |
||
| Line 3: | Line 3: | ||
| = General information = | = 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 <tt>/usr/share/doc/packages/powersave</tt>. 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. | + | 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 <tt>/usr/share/doc/packages/pm-utils</tt>. |
| The articles in the [http://en.opensuse.org/Category:Power_Management Category Power Management] might also give some useful hints, especially [[Pm-utils|pm-utils]], [[S2ram|s2ram]] and [[ACPI Suspend debugging]]. | The articles in the [http://en.opensuse.org/Category:Power_Management Category Power Management] might also give some useful hints, especially [[Pm-utils|pm-utils]], [[S2ram|s2ram]] and [[ACPI Suspend debugging]]. | ||
| Line 11: | Line 11: | ||
| If you still cannot suspend after going through the documentation, file a bugreport and add the needed logfiles as attachments. | If you still cannot suspend after going through the documentation, file a bugreport and add the needed logfiles as attachments. | ||
| - | == systems using [[Pm-utils|pm-utils]] (openSUSE 10.2 and later) == | + | == Things never to attach to a bugreport == |
| - | The interesting files are | + | * hwinfo output (it is usually just useless for this kind of bug) |
| + | * dmesg output (unless you have a good reason to believe that there is something important in there or the assignee explicitly asks for it, of course) | ||
| + | == Systems using [[Pm-utils|pm-utils]] (openSUSE 10.2 and later) == | ||
| + | The interesting files are | ||
| /var/log/pm-suspend.log | /var/log/pm-suspend.log | ||
| /var/run/pm-suspend | /var/run/pm-suspend | ||
| - | == systems using [[Projects_Powersave|powersaved]] (up to SUSE 10.1) == | + | == Systems using [[Projects_Powersave|powersaved]] (SLED10) == |
| Most important logfiles regarding the powersave daemon are... | Most important logfiles regarding the powersave daemon are... | ||
| - | |||
| /var/log/suspend2disk.log | /var/log/suspend2disk.log | ||
| /var/log/suspend2ram.log | /var/log/suspend2ram.log | ||
| Line 28: | Line 30: | ||
| /var/lib/standby-state.resume | /var/lib/standby-state.resume | ||
| - | == for all systems == | + | == For all systems == |
| - | Clarify the versions of some important packages: | + | Debug information: |
| - | + | ||
| - | 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 | kernel: uname -r | ||
| suspend to RAM problems: s2ram -n | 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 | + | 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 (as root) with: |
| + | |||
| + | pm-hibernate set machine into suspend-to-disk | ||
| + | pm-suspend set machine into suspend-to-ram | ||
| + | On old SLED10 systems, powersave is used instead (no root privileges needed): | ||
| powersave -U set machine into suspend-to-disk | powersave -U set machine into suspend-to-disk | ||
| powersave -u set machine into suspend-to-ram | powersave -u set machine into suspend-to-ram | ||
Current revision
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/pm-utils.
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.
Things never to attach to a bugreport
- hwinfo output (it is usually just useless for this kind of bug)
- dmesg output (unless you have a good reason to believe that there is something important in there or the assignee explicitly asks for it, of course)
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 (SLED10)
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
Debug information:
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 (as root) with:
pm-hibernate set machine into suspend-to-disk pm-suspend set machine into suspend-to-ram
On old SLED10 systems, powersave is used instead (no root privileges needed):
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.

