Comment 81 for bug 160763

Revision history for this message
Maxim Levitsky (maximlevitsky) wrote :

For these of you who are too lazy/busy/... compiling the kernel, here is userspace workaround.
Compile attached program writereg.c (gcc -owritereg writereg.c), put it in /usr/local/bin, and then use attached script,
make_s2ram_work after first resume.

If the output is something like (you see FF):
writing 0 to <address> (current value = FF)

Then its likely that my fix works.
Try to suspend again. If works then you can use this script after each suspend to clear the state that causes the hang on following resume