Hibernation broken when using USB devices (Latitude D810)

[Nikolaus Rath]

Since the upgrade to hardy, my Dell Latitude D810 refuses to Hibernate when USB devices have been used at some point.

If I start the computer without any usb devices plugged in (and do not plug in any devices in while the computer is running), Hibernation works. However, if at any point there is anything connected to the usb port, hibernation breaks even after the device has been removed again.

Hibernation fails with the messages

[ 1811.208411] Suspending console(s)
[ 1811.209886] drm_sysfs_suspend
[ 1811.216539] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1811.219446] serial 00:0b: disabled
[ 1811.220431] ACPI: PCI interrupt for device 0000:00:1f.2 disabled
[ 1811.220859] ACPI: PCI interrupt for device 0000:00:1e.2 disabled
[ 1811.220994] usb_hcd_pci_suspend(): ehci_pci_suspend+0x0/0xb0 [ehci_hcd]() returns -22
[ 1811.221042] pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x160 [usbcore]() returns -22
[ 1811.221088] suspend_device(): pci_device_suspend+0x0/0x60() returns -22
[ 1811.221104] Could not suspend device 0000:00:1d.7: error -22
[ 1811.221198] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[ 1811.221292] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 16 (level, low) -> IRQ 16
[ 1811.221307] PCI: Setting latency timer of device 0000:00:1e.2 to 64
[ 1811.242555] PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was 2b8000

and

$ lspci | grep 1d.7
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)

so there really seems to be some USB related problem.

[Nikolaus Rath (nikratio)]

No longer reproducible after the last kernel upgrade.

[Nikolaus Rath (nikratio)]

Ok, today it happened again. Apparently there is a different reason why it worked the last few times.
I also found a workaround:

# rmmod usbcore usb_storage snd_usb_lib usbhid ehci_hcd uhci_hcd libusual

before starting Hibernation circumvents the problems (but one has to manually modprobe the modules after resume)

[ethanay (ethan-y-us)]

This might be the issue I'm having...In my case hibernation continues through successfully despite the error and the reported failure. However, I have been unable to recover the error message right before everything shuts down. Where did you find the hibernation failure messages?
------------------------------
I have some MINOR problems with hibernate that is causing the "sleep failure" balloon to pop up which offers absolutely NO help in debugging (which I can imagine also makes things harder on developers....)

1) I invoke hibernate
2) there is a brief pause, then drm_sysfs_suspend starts
...and at the very end of the process, right before power off
3) a failure message flashes RIGHT as the hard disk is turning off, causing it to suddenly power up again to print/write the failure message
(like a hiccup)
4) the system shuts down
5) power on
6) the boot process finds the restore image successfully and loads it back into memory
7) I am fully resumed, with the error message about a failure
8) I cannot find the error message in ANY log file in /var/log

[ethanay (ethan-y-us)]

The closest I can find is this:

Jun 3 21:24:07 ethan-laptop kernel: [ 32.832510] usb usb3: root hub lost power or was reset
Jun 3 21:24:07 ethan-laptop kernel: [ 32.836409] ehci_hcd 0000:00:1a.7: debug port 1

But again, if anyone has suggestions about how to collect more information, greatly appreciated :)

[Nikolaus Rath (nikratio)]

ethanay: I got the messages from running dmesg after the failed hibernation attempt.

[ethanay (ethan-y-us)]

hmm, running dmesg doesn't find the error that appears right before the computer enters hibernation (even grepping for keywords that i remember). but it appears on screen and is noticeable enough to wake up the hard drive again right after it has shut down. i have no clue whether the error is logged, and if so, where, and if not, how to get it logged. any suggestions?

i will also post on ubuntu forums...

[Phillip Susi (psusi)]

8.10 is no longer supported. If this is still an issue for you under 10.04, please change the status back to new and add any more information you might have.