can't hibernate - get screensaver then unlock dialogue

Bug #113159 reported by Joachim Noreiko
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Just updated my system to Feisty and now I can't hibernate.

Choosing Hibernate gets me:
- a few seconds of screensaver
- a black screen with flashing cursor
- black screen with the unlock screen dialogue

I've seen this problem before on a previous version of Ubuntu.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This symptom can sometimes occur if you swap partition is not activated. Could you please add the full output of the command 'free' to your bug report? Thanks in advance.

Revision history for this message
Joachim Noreiko (jnoreiko) wrote :

I had this problem when I upgraded from Edgy to Dapper. At the time, the instructions here fixed it for me: https://launchpad.net/distros/ubuntu/+bug/66637/comments/23
However this time, after performing those steps I still have the problem. In particular, one step gave me these errors:

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.20-15-386
W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf
W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz .
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.

Here's the output from free:

joachim@ubuntu:~$ free
             total used free shared buffers cached
Mem: 1035952 927804 108148 0 257512 340356
-/+ buffers/cache: 329936 706016
Swap: 2096440 0 2096440
joachim@ubuntu:~$

Revision history for this message
Joachim Noreiko (jnoreiko) wrote :

Just tried this again and I very briefly saw a black screen with log output saying something about 'try "swapon -a"'
So I have, and this is what it says:

joachim@ubuntu:~$ swapon -a
swapon: /dev/disk/by-uuid/18e6bce0-6c48-49a6-af84-35f58d0af0cf: Operation not permitted

Revision history for this message
Brian Murray (brian-murray) wrote :

Could you please add the full contents of your '/boot/grub/menu.lst' file as an attachment to your bug report? Thanks again. By the way you would need to execute 'sudo swapon -a' as that requires root permissions.

Revision history for this message
Joachim Noreiko (jnoreiko) wrote :

Here's the menu.lst file.

And also:

joachim@ubuntu:~$ sudo swapon -a
Password:
swapon: /dev/disk/by-uuid/18e6bce0-6c48-49a6-af84-35f58d0af0cf: Device or resource busy

Revision history for this message
Brian Murray (brian-murray) wrote :

Your menu.lst file is missing information about where to resume from the relevant lines follow:

## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

I believe you need to add the following to the 'defoptions' line.

# defoptions=quiet splash resume=UUID=18e6bce0-6c48-49a6-af84-35f58d0af0cf

After modifying that line in your menu.lst file (as root) you will also need to run 'sudo update-grub'. In regards to the 'Device or resource busy' message I believe your swap partition is already activated.

Revision history for this message
Joachim Noreiko (jnoreiko) wrote :

I've done the above, and still get the same problem.
I briefly saw lines of text output, but I didn't have time to read them. Is there a log I can get them from?

Revision history for this message
Brian Murray (brian-murray) wrote :

Kernel messages can be reviewed using the command 'dmesg'. After resuming from hibernation please execute 'dmesg' and add the full output as an attachment to your bug report. Thanks again.

Revision history for this message
Joachim Noreiko (jnoreiko) wrote :

Do you mean after attempting hibernation and returning to the login screen? I can't hibernate, so I can't resume from it ;)

I did dmesg first to see where the log was up to.
The last message before attempted hibernation is '[ 188.412000] eth0: no IPv6 routers present' (that's probably bug 50099)

Here's the full output from dmesg.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.