tracking down suspend/hibernate bugs?
reacocard at gmail.com
Mon Jan 14 03:51:32 UTC 2008
In gutsy I believe the chain is this:
gnome-power-manager -> hal
(/usr/lib/hal/scripts/hal-system-power-suspend) -> acpi-support
most of the actual work occurs in acpi-support.
hal may call a different tool than acpi-support if it is available
though, see /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux
for full details.
On Jan 13, 2008 7:42 PM, Matt Price <matt.price at utoronto.ca> wrote:
> just upgraded to hardy and suspend-to-ram is broken again (as in feisty
> & other releases) i'm trying to figure out, again, how to track down
> this bug but i'm not entirely sure what the current chain of events is
> in the suspend process. can someone point me to a location where the
> process is described? or suggest best practice for finding bugs of this
> nature (in which resume is impossible, so messages e.g. from dmesg
> or /var/log/messages don't get captured?
> Matt Price
> matt.price at utoronto.ca
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
"Whoever said sunshine brings happiness has never danced in the rain."
- K. Jackson
Ubuntu Linux - www.ubuntu.com
More information about the Ubuntu-devel-discuss