Hibernate: "failed to thaw"

tyko · 09-06-2013, 04:52 AM

I'm running Linux Mint 15 Cinnamon. When my notebook is hibernating, it shows error(s) something like:

dpm_run_callback()...
...failed to thaw error -19

If someone can tell me how to see the log then I can tell what goes in the dots (...).

Please guide me here.

goumba · 09-07-2013, 07:11 AM

Type [b]dmesg=/b] at a shell prompt, and it will show some messages. You can also check the contents of the file /var/log/messages. It's been a while since I've had a problem with hibernation, I don't remember exactly where the messages go.

Is this occurring on a system on which hibernation previously worked? If this is a new install, check the size of your swap space. If it is not greater than the amount of physical RAM, hibernation will not work.

Edit: Looking at launchpad, there were some reports that Casper was causing a problem as well. As Mint is Ubuntu-based (unless you chose the Debian edition, in which case you can ingnore this paragraph), see if the Casper package is installed.

In any case, give this command a try, as root:

Code:

update-initramfs -k all -u

I've seen some reports of a 'stock' initramfs that doesn't play nice with some systems.

tyko · 09-08-2013, 04:40 AM

Thank you for your time. After my post I found a bug report of the same problem:
https://bugs.launchpad.net/ubuntu/+bug/1094595 (maybe u also found the same webpage)
But unlike some users, hibernation is working for me. I raised this issue mainly because it can be related to a problem I'm sometimes facing while switching (powering) on Mint. It's a fresh install.

Swap is bigger than RAM. Casper isn't installed. update-initramfs -k all -u ran successfully but error persists.

I searched /var/log for files containing words "failed to thaw" (including sub-folders and hidden files) but no such file exists. In the output of dmesg, I found:

Code:

[   39.398939] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19
[   39.398941] PM: Device 00:07 failed to restore: error -19

Note that it's using word "restore" instead of "thaw" in 2nd line.

lspci -n and lsusb lists no device as "00:07".

Including some lines before the above quoted lines:

Code:

[   39.387170] ehci-pci 0000:00:1a.0: setting latency timer to 64
[   39.387181] usb usb1: root hub lost power or was reset
[   39.387225] ehci-pci 0000:00:1d.0: setting latency timer to 64
[   39.387232] snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
[   39.387237] usb usb2: root hub lost power or was reset
[   39.387304] ahci 0000:00:1f.2: setting latency timer to 64
[   39.387321] ath: phy0: ASPM enabled: 0x42
[   39.391064] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[   39.391124] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[   39.398939] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19
[   39.398941] PM: Device 00:07 failed to restore: error -19

goumba · 09-08-2013, 07:58 AM

Are there any other lines in dmesg that contain '00:07'? There should be, and that would point toward the device causing issues.

tyko · 09-10-2013, 04:52 AM

Yes, one line:

Quote:

[ 0.161163] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)

goumba · 09-10-2013, 06:23 AM

Is this an HP laptop? The only device I could find with that ID is the Keyboard/"HP Hotkeys" device, which I wouldn't believe to interfere with hibernation, but hey, strange things happen.

tyko · 09-10-2013, 08:32 AM

Thanks for the searches you've done for me

It's Samsung. But let's leave this. Thanks for ur time