Hibernate/resume is very slow and work once

Hi efa,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I'm running:
linux-image-2.6.32-02063211-generic_2.6.32-02063211_i386.deb
the suspension and resume time is again 1.45 - 1.55 minutes, very slow.

The good news is that it work more than once, with some strange desktop wallpaper reload error (video ram garbled when the desktop appear, and is corrected after 10 seconds).

With this k version I see a lot of error on the console while suspension or resume is ongoing.
They are about:
[drm:radeon_fence_wait] *ERROR* fence(xxxx:xxxx) 512 ms timeout going to reset GPU
(many many times)
ata1: ACPI set timing mode failed (status:0x200b)
1-0061: Error: firmware xc3028-v27.fw not found.

With the standard Ubuntu k I got no messages on the console (also with splash remove in the grub menu).

I have a similar problem. I have a system with 4GB of RAM, and more than sufficient space in a swap partition (about 8GB). I can hibernate more than once (at least twice), but if more than a small fraction of the RAM is in use (e.g., say about 2GB or more), then the suspend to disk process hangs. It seems like it is about to shut down (e.g., USB and wireless devices are turned off), but ultimately it never writes the RAM to disk. I can hear the CPU fan spinning up suggesting something is taking alot of CPU processing, and there is infrequent disk activity (but nothing like the consistently lit state of the disk indicator during a successful hibernate). After about 10 minutes or so, I gave up and powered it down. I could try letting it go longer, but that seems pointless, as 10 minutes is ample time to close everything on the desktop and shut down normally.

Is there something that tries to compress the RAM during the hibernate process to conserve space? If so, is there a way to disable that?

mgl described what's happening with my machine quite well: 4GB RAM, large swap partition, hibernate works but resume is extremely slow with continuous disk activity...

In my case, it seems to be more or less reliable (hibernate worked always, suspend wouldn't resume once). I'm using a PAE kernel:
$ uname -a
Linux *** 2.6.32-24-generic-pae #41-Ubuntu SMP Thu Aug 19 02:43:57 UTC 2010 i686 GNU/Linux

efa, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

now I'm using:
Linux 02cor2133 3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux
Ubuntu 12.04 LTS

the hibernate option is always disabled, so I cannot test it anymore.
Should I open e new bug for hibernate disabled?

efa, no you should not file a new bug for hibernate being disabled. The hibernate option is disabled intentionally as per https://help.ubuntu.com/community/PowerManagement/Hibernate#Troubleshooting . Please follow the directions in that link to enable it, and then follow the directions requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580757/comments/6 .

enabled hibernate, tested and now work.
Just one think left: after the save2disk process end, the PC reboot instead of switch off.
Pressing off switch prevents reboot.
On reboot recover everything at the point of hiberante command.

efa, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

looking to status description list, invalid is particularly wrong. Probably "Fix Released" best matches the situation

eta, regarding your post https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580757/comments/11 :
>"looking to status description list, invalid is particularly wrong."
No, it's not.

>"Probably "Fix Released" best matches the situation"
Fix Released is reserved only for when a documented fix was released by a developer, with accompanying changelog, as documented in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580757/comments/10 . This did not happen in this report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580757/comments/10 was the correct action as per https://wiki.ubuntu.com/Bugs/Responses#Bugs_resolved_after_update_or_config_change .

If you have more inquiries to make, please do not comment here. Instead, please redirect them to irc://irc.freenode.net/ubuntu-bugs or <email address hidden> . As well, there is no need to respond to my post as this report is closed. Instead, please redirect to above mentioned.

Thanks!