Hello: In this time I conducted several more tests since now I'm running a Debian kernel, exactly experimental 3.3.2.
It's likely confirmed that the patch I tested was the fix for the hang problem. This is probably already addressed as [0] which is part of this bug. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645547 Once that is fixed, plymouth is not working fully right. Everytime I try to resume things goes as expected until some little time after I'm asked for the cryptroot password. At this point plymouth freezes and I got that I can alt- sysrq-K to kill it and resume with the resuming. Fortunately I unmasked that sysrq feature that is masked in default Debian kernels. After I do this I get the "Returning to userspace" message and resume ends up succesfully. I haven't test without uswsusp package. As a conclusion I'd say that the interface between uswsusp and plymouth is not working very well, but I'm not sure if such thing exist. I'd also say that if this freeze is fixed, this bug (and those merged) can be considered solved. HTH, best regards, -- Raúl Sánchez Siles ----->Proud Debian user<----- Linux registered user #416098
signature.asc
Description: This is a digitally signed message part.
