it appears that the update to kernel should occur only on a clean start up specifically for the update of the kernel... then another reboot to continue on.
A kernel update should give warning that the system needs to be restarted, and NOT apply the patches that break suspend/hibernate to disk until the user has indicated that the system can go down. If the user says dont restart the computer, it is implied that the customer might want the stuff written to disk. I dont know if I can get the conditions to reproduce again.... and a new kernel might work with an old ones info, and then again another might not... This is when CHANGING between two kernels. I dont see how a specific kernel could have a problem, or be expected to be future compatible with every little thing that could ever possibly go wrong. I was basically hypothesising that the kernel was switched out from under the hibernation image, or the format of the image changed between kernels. On Wed, Aug 26, 2009 at 5:15 PM, kernel-janitor<le...@canonical.com> wrote: > Hi AaronPeterson, > > Please be sure to confirm this issue exists with the latest development > release of Ubuntu. ISO CD images are available from > http://cdimage.ubuntu.com/releases/karmic . However, note you can only > test Suspend, not Hibernate, when using a LiveCD. If the issue remains, > run the following command from a Terminal > (Applications->Accessories->Terminal) it will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux 289258 > > Also, please be sure to take a look at > https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . If you > can provide any additional information outlined there it would be much > appreciated. > > Additionally, if you could try to reproduce this with the upstream > mainline kernel that would be great. It will allow additional upstream > developers to examine the issue. Refer to > https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the > upstream kernel, please remove the 'needs-upstream-testing' tag. This > can be done by clicking on the yellow pencil icon next to the tag > located at the bottom of the bug description and deleting the 'needs- > upstream-testing' text. Thanks in advance. > > [This is an automated message. Apologies if it has reached you > inappropriately; please just reply to this message indicating so.] > > > ** Tags added: kernel-suspend > > ** Tags added: needs-kernel-logs > > ** Tags added: needs-upstream-testing > > ** Tags added: kj-triage > > ** Changed in: linux (Ubuntu) > Status: New => Incomplete > > -- > certain updates ( to kernel?) might make suspend to disk not work -- make > unavailable or fix--resume didn't occur > https://bugs.launchpad.net/bugs/289258 > You received this bug notification because you are a direct subscriber > of the bug. > -- certain updates ( to kernel?) might make suspend to disk not work -- make unavailable or fix--resume didn't occur https://bugs.launchpad.net/bugs/289258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
