hi, 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?
thanks, matt -- Matt Price [EMAIL PROTECTED] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
