upgrading kernel can make a system un-hibernatable

[Brian J. Murrell]

If one updates one's kernel, which causes the default kernel pointed to by grub to change, a system will not be straightforwardly resumable from hibernation. This is because when one does power back on, the kernel that will boot by default will not be the same kernel the on-disk hibernation image is for. One needs to be careful to boot the kernel that was booted when the system was hibernated -- if one even knows what that was.

It seems to me to be entirely useful that when you hibernate a system, the kernel and initrd that were booted at the time of hibernation are stashed away and a new, temporary grub menu item is created clearly indicating that it's for resuming of the hibernated image.

This framework should also be careful to stash the on-disk image of the running kernel if the package providing that image is removed from disk. In fact, perhaps it should be not allowed to remove the package providing the running kernel to prevent this situation.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 902903

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Brian J. Murrell (brian-interlinx)]

There are no logs to support this report. The situation described is quite clear as it is.