JauntySuspendResumeHibernate

Differences between revisions 4 and 6 (spanning 2 versions)
Revision 4 as of 2008-11-26 19:23:38
Size: 2765
Editor: nc-65-40-95-196
Comment:
Revision 6 as of 2008-11-28 12:30:22
Size: 4340
Editor: 82-44-33-89
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
Getting down to one suspend/hibernate method of Jaunty, improving the experience.
Jaunty should be using just one method of Suspend/Resume/Hibernate and sticking to this one method.
Jaunty needs to improve the overall Suspend/Resume/Hibernate experience with the help of suitable debug tools to fix buggy suspend/resume/hibernate issues.
 
Line 20: Line 23:
##This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. There needs to be some rationalisation in the way suspend/resume/hibernate is controlled from userspace as there are several existing methods available:

 * Writing directly to /sys/power/state (lowest level)
 * Using /etc/acpi/sleep.sh (acpi-support)
 * pm-utils - current solution (as used by hal)
 * DeviceKit-power which supersedes the power-management functionality of hal and replaces pm-utils.

The acpi-support method of suspend/resume should be removed as it is legacy and should be transitioned into hal-info and pm-utils. Having this method as well as pm-utils seems unjustifiable - it's a different suspend/resume mechanism to pm-utils and duplication of different suspend/resume functionality is not helpful.

Either we continue with pm-utils or move to DeviceKit-power (which is supported by the new gnome-power-manager for GNOME 2.26). Depending on the choice, we should just have one solution for suspend/resume/hibernate instead of many.


Diagnosing and hence fixing broken suspend/resume/hibernate needs to easier. A Community based Wiki tutorial needs to be written to help users to gather information that can help pinpoint and fix problems.

Debugging suspend/resume/hibernate issues can be notoriously difficult; being able do dump kernel messages early to a serial console is useful, however modern PCs do not have legacy serial port hardware, so providing a USB serial console driver in initramfs is required.
Line 23: Line 40:

Line 66: Line 85:
 * https://wiki.ubuntu.com/UnderstandingSuspend

Summary

Jaunty should be using just one method of Suspend/Resume/Hibernate and sticking to this one method. Jaunty needs to improve the overall Suspend/Resume/Hibernate experience with the help of suitable debug tools to fix buggy suspend/resume/hibernate issues.

Release Note

Rationale

There needs to be some rationalisation in the way suspend/resume/hibernate is controlled from userspace as there are several existing methods available:

  • Writing directly to /sys/power/state (lowest level)
  • Using /etc/acpi/sleep.sh (acpi-support)
  • pm-utils - current solution (as used by hal)
  • DeviceKit-power which supersedes the power-management functionality of hal and replaces pm-utils.

The acpi-support method of suspend/resume should be removed as it is legacy and should be transitioned into hal-info and pm-utils. Having this method as well as pm-utils seems unjustifiable - it's a different suspend/resume mechanism to pm-utils and duplication of different suspend/resume functionality is not helpful.

Either we continue with pm-utils or move to DeviceKit-power (which is supported by the new gnome-power-manager for GNOME 2.26). Depending on the choice, we should just have one solution for suspend/resume/hibernate instead of many.

Diagnosing and hence fixing broken suspend/resume/hibernate needs to easier. A Community based Wiki tutorial needs to be written to help users to gather information that can help pinpoint and fix problems.

Debugging suspend/resume/hibernate issues can be notoriously difficult; being able do dump kernel messages early to a serial console is useful, however modern PCs do not have legacy serial port hardware, so providing a USB serial console driver in initramfs is required.

Use Cases

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Test/Demo Plan

Unresolved issues

BoF agenda and discussion

References


CategorySpec

KernelTeam/Specs/JauntySuspendResumeHibernate (last edited 2008-12-10 22:17:41 by 98)