I am running Ubuntu 8.10 on a Dell M1330 using linux kernel 2.6.31-22-generic. Recently, I gave 2.6.35-14-generic a try. Apart from a few issues a major problem was that the laptop did not resume from hibernation for this kernel but rebooted instead (resume from suspend worked fine). The reason was that the corresponding line for this kernel in grub's menu.lst was _below_ of that for the regular kernel. Putting the line on top of the menu.lst entries made it work. I can hardly believe that upon resume information on the running kernel is not retrieved from the system image but from the first kernel line of grub.

Huh? Not sure I understand you.

You can't hibernate with one kernel then reboot into a different kernel and expect it to work. The kernels must match.

Hmm, I think I don't understand you as well. How can you boot into a different kernel when it has to match? Anyway, what I wanted to say is that the first kernel in menu.lst did not match the one which was hibernated which eventually caused the reboot on resume. Hope the case is clear now.

Well, that's how hibernation works. The kernel starts then looks for a resume image. It's up to you to select the right kernel, either manually, or by making sure that the default is the right one, or by shutting down instead of hibernating when you install a new kernel.

Well, that's what I learned. But I think it is not impossible e.g. to modify menu.lst in a way that the hibernating kernel becomes the first entry, and reverse the change after resuming. This would alleviate the issue of manual seclection.