restore after hibernate freezes the computer

Bug #816859 reported by Marko Vendelin
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
uswsusp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On Lenovo Thinkpad X201 (amd64) uswsusp doesn't work in Natty. I have tried the default kernel vmlinuz-2.6.38-10-generic and a newer one from linux-image-3.0.0-0300-generic_3.0.0-0300.201107220917_amd64.deb . Hibernate works successfully, restore reads the image and reports success, but the system is frozen (no response to Alt-Fx, Ctrl-Alt-Fx). This does not depend on whether I used GUI or command line to initiate hibernate. Restore fails even if the system was hibernated just after reboot from console using pm-hibernate command. In 10.10 uswsusp worked on my system. This maybe a duplicate of 682604, except it occurs in natty.

I wanted to use uswsusp since the default hibernate frequently resulted in unstable system (crashed after using it for a while after restore).

Please let me know if any additional info is needed.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: uswsusp 0.8-1.2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Wed Jul 27 11:36:02 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: uswsusp
UpgradeStatus: Upgraded to natty on 2011-07-12 (14 days ago)

Revision history for this message
Marko Vendelin (marko-vendelin) wrote :
Revision history for this message
Marko Vendelin (marko-vendelin) wrote :

I have tried to modify default /etc/uswsusp.conf , but that made no difference:

# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/sda6
#splash = y

compress = y
#early writeout = y

#image size = 1751899504
#RSA key file = /etc/uswsusp.key
shutdown method = platform

compute checksum = y

Revision history for this message
Marko Vendelin (marko-vendelin) wrote :

After installing an upgraded kernel, I had no problems with uswsusp. Kernel 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux . I suggest to close the bug.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in uswsusp (Ubuntu):
status: New → Confirmed
Revision history for this message
markusj (markusj) wrote :

uswsusp did not work on my T520, both with 10.10 and 11.10.
It loads the image from disk and restores it, shows some nice statistics on the commandline and then the system freezes instead of starting up.

System is a freshly installed Ubuntu 11.10 oneiric x64 with full disk encryption (lvm2 in a luks container).

> markus@markusnb:~$ uname -a
> Linux markusnb 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

> markus@markusnb:~$ cat /etc/uswsusp.conf
> # /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
> resume device = /dev/disk/by-uuid/e79ca499-0f10-4214-a422-66d40787746a
> splash = n
> compress = y
> compute checksum = y
> early writeout = y
> image size = 536870912
> # 1831375257
> shutdown method = platform

Revision history for this message
joe richter (joe-r) wrote :

This also occurs on 3.0.0-16-generic in oneiric.
I figured the boot process continues normally if the resume task is killed with SysRq-e, but i'm currently not sure where to fix this.

Rgds - Joe

Revision history for this message
markusj (markusj) wrote :

This also occurs on precise (12.04 AMD64 with the same lvm/luks setup mentioned above), Kernel 3.2.0-30-generic

I just figured out (independent from your report, funny ...) SysRq-e makes the resume continue. Is there any way to figure out which process is blocking? As far as i know vanishes SysRq-e all traces.

Revision history for this message
markusj (markusj) wrote :

Maybe the debian guys nailed this issue down? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593795
It looks like uswsusp conflicts with plymouth ...

Revision history for this message
Lars Ellenberg (just-do-it) wrote :

I found the following workaround to be good enough for me: basically just tell the initrd plymouth to quit before resume.

sudo -i # become root
cd /usr/share/initramfs-tools/scripts/local-premount
patch <<EOF uswsusp
--- uswsusp.orig
+++ uswsusp
@@ -34,4 +34,6 @@
      mknod /dev/snapshot c ${DEV%:*} ${DEV#*:}
 fi

+[ -x /bin/plymouth ] && plymouth quit
+
 /sbin/resume
EOD

update-initramfs -u # still root

Done.

Have fun.

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.