uswsusp does not thaw/resume from hibernate/disk.. interaction with plymouth to blame

[insaner]

im just reporting this on launchpad, since it seems the fix hasnt found its way into ubuntu yet, and even the newest beta wont contain the fix.

this is an ao522 netbook, running ubuntu 12.04. i have tried several kernels including the default 2.6, 3.0, and currently 3.2 kernels.

 resume from suspend to ram (s2ram) works. hibernation itself works, but resuming from hibernate always leads to a hang.

WORKAROUND:

once the resume from hibernate process is hung, doing a
alt + ctrl + sysrq
alt + ctrl + K

kills the hung plymouth and actually correctly thaws the system.

for reference:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593795
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620145

http://lists.freedesktop.org/archives/plymouth/2012-May/000641.html
http://lists.debian.org/debian-kernel/2012/04/msg00320.html

it seems that the included uswsusp included in even the beta for 12.10 is 1.5 years old (uswsusp 1.0+20110509-2ubuntu1 ).. and i think at some point i read somewhere that the fix for this has already been implemented in git..

git clone git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-utils.git

though i have not tested it.

--
-insaner
www.insaner.com

[insaner (insaner)]

found it:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583525#18

----
which i found after finding this again:
----

http://www.kernelhub.org/?msg=71669&p=2

From: Mikko Vinni
Mon, 21 May 2012 08:52:24 +0200

"There was on May 18th a patch proposed for the vt_event_wait() function[4],
but that patch has no effect for this particular hang.

Apparently Mandriva has a patch[5] to add plymouth support to uswsusp, but one
would assume that s2disk/resume should not hang in its default state."

[4] "Race in vt_event_wait() during suspend/resume": http://article.gmane.org/gmane.linux.kernel/1299487

[5] changelog e.g.: http://rpmfind.net//linux/RPM/mandriva/2011/x86_64/media/main/release/suspend-0.8-12.20080612.x86_64.html

[insaner (insaner)]

hi, i think this bug was marked as fix released because of
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620145
being marked as closed.

however, if you read the message there:

"Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to <email address hidden> with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz"

it is clear that this bug has NOT been fixed, and is still present in ubuntu 13.04.

please change it back to "NEW"

[insaner (insaner)]

sorry, i pressed "post comment" by mistake.

also, the previous workaround no longer works, and now i must do:
alt + ctrl + sysrq
alt + ctrl + k
alt + ctrl + i

in that order to thaw my machine.

 thanks

[Launchpad Janitor (janitor)]

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

[hackel (hackel)]

I just tested this with uswswap 1.0+20120915-5 (latest version in Utopic) and the problem persists on my Dell Mini 9. SysRq-K still allows a successful resume from hibernation. It would be really nice if someone could solve this 3+ year old bug.

Also, why did you make this a separate bug report? Isn't it a dupe of bug #682604?

[hackel (hackel)]

Removing association because Debian bug #583525 was auto-closed due to inactivity. Fix was not released!