ThinkPad R61i won't resume from hibernation

[Scott Severance]

My laptop is a Lenovo ThinkPad R61i running Hardy. When I hibernate, everything appears to be normal (is there a way to get a log of this so I can check?). The crescent moon light on my laptop blinks, there's a bunch of disk activity, then the machine powers off. However, when I power it back on, it's as if I shut down normally, instead of hibernating. Nothing is restored.

~:$ uname -a
Linux scott-laptop 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686 GNU/Linux

This might be related to bug 54382. Also, I'm really not sure which package to assign it to, as I don't know much about the kernel or how hibernation works. Please correct it if it's wrong.

[Leann Ogasawara (leannogasawara)]

There hasn't been any recent activity in this bug report and we were wondering if this is still an issue? The Ubuntu kernel team is actively working on the upcoming Intrepid Ibex 8.10 release. If you could please test the latest Alpha release for Intrepid it would be much appreciated - http://www.ubuntu.com/testing . Please let us know your results. If the issue still exists, please also provide the appropriate debugging information as outlined at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance.

[Scott Severance (scott.severance)]

This is still an issue. I'm still in Hardy. I'm not able to run Intrepid on this machine since I can't afford the potential downtime of an alpha release. If there's something I can do to help pin this down, I'd be glad to. But I know basically nothing about the kernel or hibernation, and so I don't even know where to start.

Additional info from the KernelTeamBugPolicies page, as requested (which wasn't provided above):

/proc/version_signature:
Ubuntu 2.6.24-19.41-generic

[Leann Ogasawara (leannogasawara)]

Thanks Scott.

I just wanted to let you know the kernel team is going to be putting out a call for testing in the next day or so. Your bug report will get this message, please just disregard it if you are unable to test because of the downtime it would cause. Thanks.

[Scott Severance (scott.severance)]

I might have made some progress on this. Reading this post: http://ubuntuforums.org/showpost.php?p=5168992&postcount=5 gave me the idea to check if my initramfs was incorrect. It turns out that my initramfs is missing the file conf/conf.d/resume.

I presume that this is because when I installed I didn't use swap. I have 3 GB of RAM, so the only use I have for swap is for hibernation--but I didn't know that swap was necessary for hibernation when I installed. I now have 3 GB of swap, but I haven't been able to find any documentation on how to rebuild initrd.img-2.6.24-19-generic with the proper resume information. I Googled this, but all I found was some kernel documentation and a Gentoo wiki page. The kernel docs were above my head (I know virtually nothing about the kernel), and the Gentoo page appeared to use Gentoo-specific commands. Later note: I just found the Debian kernel handbook page on initramfs, but if it answers my questions, I'm too dense to find the answer. I don't think I'm trying to generate a new initramfs using the method detailed there. I'm trying to change my existing one (or replace it with one that I altered).

I think there are two issues here:

  1. There should be some documentation about avoiding this situation, along with how to fix it.
  2. Changes to swap configuration should be automatically detected, and initramfs should be updated automatically. I have no idea how difficult this would be. Perhaps it's infeasible at present. But it really should be automated.

While I realize that this isn't a support forum, I would appreciate suggestions as to how to rectify this situation. You could consider it part of the documentation. :)

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Lynoure Braakman (lynoure)]

I had this problem with Intrepid 2.6.27-3 kernel (I have not tried with the 2.6.27-4 kernel, as that on seems not to finish booting most of the time on this R61i).

[Leann Ogasawara (leannogasawara)]

Care the test the newer 2.6.27-7.14 kernel. Thanks.

[Scott Severance (scott.severance)]

I've upgraded to Intrepid now and nothing's changed.

~:$ uname -a
Linux scott-laptop 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Scott Severance (scott.severance)]

After finally upgrading my machine to Lucid, this issue persists, exactly as before.

[penalvch (penalvch)]

Scott Severance, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Scott Severance (scott.severance)]

As the affected machine no longer works, I can no longer comment on whether this bug exists.