Jaunty should be using just one user space method of Suspend/Resume/Hibernate and sticking to this one method rather than having several different alternative implementations.
Jaunty needs to improve the overall Suspend/Resume/Hibernate experience. Tracking down broken drivers can be a pain. To facilitate this, better troubleshooting assistance is required, ranging from a one-stop-shop trouble shooting Wiki guide, suitable quirk checking tools and well documented trouble shooting and debug strategies to help identify and fix buggy suspend/resume/hibernate issues.
There needs to be some rationalisation in the way suspend/resume/hibernate is controlled from user space 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 is a different suspend/resume mechanism to pm-utils and the duplication of different suspend/resume functionality is confusing and 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 or troubleshooting guide (such as http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-debug.html) needs to be written as the de-facto reference page to help users to:
- identify known hardware issues
- step-by-step diagnose problems
- gather hardware and kernel specific information that can help pin-point and fix problems
Also having a program/script that can test for known quirks and suggest pm-suspend workarounds would be helpful.
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.
- A user cannot get their laptop to resume. They visit the trouble shooting guide which lists known hardware issues and pm-suspend workarounds that they can try.
- A user cannot get their laptop to resume. but the user is informed they can run a quirk checking program which can automatically suggest pm-suspend workarounds.
- A user cannot resume their laptop because they have problems with specific buggy drivers. The Wiki tutorial explains how to turn on the/sys/power/pm_trace "resume-trace" debugging procedure for finding buggy drivers to gather sufficient information to pin-point the relevant broken driver. They can then submit a bug report against this driver.
- A user cannot hibernate their laptop. The tutorial explains how to make the hibernation core run in a test mode and then run through the 5 different test modes: freezer, devices, platform, processors or core.
- A user wants to attach an early kernel log message to a bug report. By plugging in a USB-serial dongle and enabling the USB serial console driver they can then capture the log on another PC using hardware which does no have a legacy serial port. The tutorial should explain how to enable the driver using kernel boot line options and how to capture the dmesg log on a 2nd PC over serial using tools such as minicom.
pm-utils Quirk Checking Scripts
The Quirk checking script http://people.freedesktop.org/~hughsient/quirk/quirk-checker.sh perhaps could be included into the disto to help users pin-point suspend/resume quirks.
To facilitate the debug via USB Serial console, the USB serial console kernel driver needs to be included into initramfs. The user needs to also add in the appropriate USB console boot parameter, e.g.
This needs to be appropriately documented in the Wiki page.
Deprecating /etc/acpi/sleep.sh (et al) requires release note documentation at a minimum and perhaps modifications to the acpi-scripts informing the user that these are now deprecated and should not be used.
BoF agenda and discussion