Suspend and Hibernate: Waking right up again

[co0lingFir3]

Binary package hint: acpi-support

I have a Compal IFL90 laptop and suspending/hibernating does not work right in Lucid.
Upon suspending everything seems to work fine and it even appears to successfully write everything to RAM but then it wakes right up again.
Upon hibernating i get this error on the console:
PM: Device 00:08 failed to freeze: error -5
It then seems to try to hibernate nevertheless but as in suspending it wakes right up again and shows me the "Screen Locked" UI.
I would be glad to provide any additional information if possible.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: acpi-support 0.136
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat May 1 10:57:52 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: acpi-support

[Jeff Fortin Tam (kiddo)]

I saw something like this today on my Dell Inspiron 530n desktop computer. It *usually* suspends and resumes fine, but today it waked right up again and this is what I saw in kern.log:

PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
usbhid 5-2.1:1.0: suspend error -5
pm_op(): usb_dev_suspend+0x0/0x20 returns -5
PM: Device 5-2.1 failed to suspend: error -5
PM: Some devices failed to suspend
PM: resume of devices complete after 217.688 msecs
PM: resume devices took 0.284 seconds
PM: Finishing wakeup.
Restarting tasks ... done.

Interestingly enough, after unplugging all the usb devices except my keyboard, it still didn't work, but when I unplugged the keyboard (the only usb device left), it worked. After replugging, it still works.

For your particular issue, though, you are using an nvidia GPU. This is more likely to be the cause...

[co0lingFir3 (coolingfire)]

I tried resuming today again and obviously it didnt work. Here is the output of my kern.log

tg3 0000:04:00.0: PME# enabled
tg3 0000:04:00.0: wake-up capability enabled by ACPI
PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
sd 2:0:0:0: [sda] Synchronizing SCSI cache
sd 2:0:0:0: [sda] Stopping disk
PM: suspend of drv:sd dev:2:0:0:0 complete after 437.291 msecs
PM: suspend of drv:psmouse dev:serio1 complete after 402.029 msecs
PM: suspend of drv:atkbd dev:serio0 complete after 105.839 msecs
tpm_inf_pnp 00:08: saving TPM state
tpm_inf_pnp 00:08: Timeout while clearing FIFO
tpm_inf_pnp 00:08: error while saving TPM state
device_suspend(): pnp_bus_suspend+0x0/0x70 returns -5
PM: Device 00:08 failed to suspend: error -5
PM: Some devices failed to suspend
PM: resume of drv:usb dev:usb2 complete after 148.012 msecs
sd 2:0:0:0: [sda] Starting disk
PM: resume of drv:sd dev:2:0:0:0 complete after 1301.871 msecs
PM: resume of devices complete after 1673.031 msecs
PM: resume devices took 1.672 seconds
PM: Finishing wakeup.
Restarting tasks ... done.

So is the TPM module causing this even when I have it deactivated in the BIOS?

[Steve Langasek (vorlon)]

This shows a failure to suspend a USB device. Reassigning to the kernel.

[Maharifu (mail-lmcarvalho)]

Hi, I have a Compal FT00 and I am having this same issue. I get those same error messages as well.

[Ali Nadalizadeh (nadalizadeh)]

I have the same problem with my Lenovo 3000 V100, On 10.04 LTS (Lucid)
I had no problem with previous releases.

Here's the kernel log :
[ 6419.206787] PM: suspend of drv:sd dev:0:0:0:0 complete after 518.618 msecs
[ 6419.583772] PM: suspend of drv:psmouse dev:serio4 complete after 376.902 msecs
[ 6419.792066] PM: suspend of drv:atkbd dev:serio0 complete after 208.276 msecs
[ 6419.792714] pm_op(): usb_dev_suspend+0x0/0x20 returns -16
[ 6419.792717] PM: Device usb1 failed to suspend: error -16
[ 6419.792719] PM: Some devices failed to suspend
[ 6419.874267] sd 0:0:0:0: [sda] Starting disk
[ 6420.704105] PM: resume of drv:sd dev:0:0:0:0 complete after 829.833 msecs
[ 6420.807018] PM: resume of devices complete after 1014.292 msecs
[ 6420.807180] PM: resume devices took 1.012 seconds
[ 6420.807190] PM: Finishing wakeup.
[ 6420.807192] Restarting tasks ... done.

My USB Device List :
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 08ff:1600 AuthenTec, Inc. AES1600
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 192f:0616 Avago Technologies, Pte.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0402:5602 ALi Corp. Video Camera Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Aymeric (mulx)]

Hi same here on a Acer Aspire 9410z.

Suspend and Hibernate won't work, and by looking dmesg there is a problem with usb_dev_suspend.

[ 259.744267] pm_op(): usb_dev_suspend+0x0/0x20 returns -16
[ 259.744274] PM: Device usb1 failed to suspend: error -16
[ 259.744279] PM: Some devices failed to suspend

I have a Ali Corp. Video Camera hard plugged.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0402:5602 ALi Corp. Video Camera Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Suspend and Hibernate work fine on Ubuntu Karmic.

[Jeremy Foshee (jeremyfoshee)]

Hi co0lingFir3,

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.]

[co0lingFir3 (coolingfire)]

Hello Jeremy,

I installed the latest mainline kernel 2.6.34-999 and tried Suspend and Hibernate. Both of them work flawlessly with this it (should I post kern.log again?).

Greets!

[Jeremy Foshee (jeremyfoshee)]

co0lingFir3,
     Not if you are satisfied that it is resolved for you. Those affected by this that are still seeing issues after testing the latest mainline will need to open new bugs to address their issues. i'll be working with the team to see what needs to be pulled from mainline to address this issue in the next release kernel.

Thanks!

~JFo

[co0lingFir3 (coolingfire)]

Great! Does this mean that there should be a new kernel in lucid-updates sometime or will this bug only be fixed in Maverick?

[Jeremy Foshee (jeremyfoshee)]

co0lingFir3,
     If the bits that fix this in mainline get pulled into the stable branch, then you should see them pulled into Lucid in an update kernel. Part of the process now is to see exactly what fixes it (if possible) and verify that it has been pulled to stable.

Thanks!

~JFo

[conradoat (conradoat)]

Hi all

I have exactly the same problem on an Acer Aspire 5102. When I suspend, it wakes up immediately. And it seems to be because of the built-in webcam. I post here the pm-suspend.log and some lines from my dmesg, in case it can be useful.

[conradoat (conradoat)]

My lines from dmesg

[ 1584.282858] PM: Syncing filesystems ... done.
[ 1584.362565] PM: Preparing system for mem sleep
[ 1584.362572] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 1584.364071] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 1584.364186] PM: Entering mem sleep
[ 1584.364202] Suspending console(s) (use no_console_suspend to debug)
[ 1584.490056] PM: suspend of drv:ieee80211 dev:phy0 complete after 125.502 msecs
[ 1584.500402] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1584.500544] sd 0:0:0:0: [sda] Stopping disk
[ 1584.959339] PM: suspend of drv:sd dev:0:0:0:0 complete after 458.938 msecs
[ 1585.334659] PM: suspend of drv:psmouse dev:serio4 complete after 364.562 msecs
[ 1585.430292] pm_op(): usb_dev_suspend+0x0/0x20 returns -16
[ 1585.430295] PM: Device usb1 failed to suspend: error -16
[ 1585.430298] PM: Some devices failed to suspend
[ 1585.491243] sd 0:0:0:0: [sda] Starting disk
[ 1586.212916] PM: resume of drv:sd dev:0:0:0:0 complete after 721.671 msecs
[ 1586.226074] PM: resume of devices complete after 795.770 msecs
[ 1586.226268] PM: resume devices took 0.790 seconds
[ 1586.226280] PM: Finishing wakeup.
[ 1586.226282] Restarting tasks ... done.
[ 1586.500391] eth0: link up, 100Mbps, full-d

[Ali Nadalizadeh (nadalizadeh)]

Upgrading to Mainline build (2.6.34) fixed the problem for me too.

[Georg Sauthoff (g-sauthoff)]

On a thinkpad x200 I am affected by this bug as well under lucid.

But only if a USB-to-Parallel-port cable is attached to an USB port. If it is not attached suspend and resume works as expected.

In Karmic and earlier versions, pm-suspend etc. worked with this device attached.

The problematic device is:

Bus 001 Device 088: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port

  idVendor 0x067b Prolific Technology, Inc.
  idProduct 0x2305 PL2305 Parallel Port
  iManufacturer 1 Prolific Technology Inc.
  iProduct 2 IEEE-1284 Controller

[Julian Sanchez (julian-bidda)]

[SOLVED]
On a Macbook Air 2,1 I've same problem as I show you here:

This is my syslog reporting the problem:

kernel: [203060.044217] PM: Syncing filesystems ... done.
kernel: [203060.068040] PM: Preparing system for mem sleep
kernel: [203060.068045] Freezing user space processes ... (elapsed 0.00 seconds) done.
kernel: [203060.068728] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
kernel: [203060.068775] PM: Entering mem sleep
kernel: [203060.068788] Suspending console(s) (use no_console_suspend to debug)
kernel: [203060.069901] btusb_intr_complete: hci0 urb e3cd9600 failed to resubmit (1)
kernel: [203060.070891] btusb_bulk_complete: hci0 urb e3cd9380 failed to resubmit (1)
kernel: [203060.071891] btusb_bulk_complete: hci0 urb e3cd9880 failed to resubmit (1)
kernel: [203070.104110] usbhid 3-6:1.0: suspend error -5
kernel: [203070.104118] pm_op(): usb_dev_suspend+0x0/0x20 returns -5
kernel: [203070.104121] PM: Device 3-6 failed to suspend: error -5
kernel: [203070.104123] PM: Some devices failed to suspend
kernel: [203070.222573] PM: resume of devices complete after 118.446 msecs
kernel: [203070.272160] PM: resume devices took 0.168 seconds
kernel: [203070.272186] PM: Finishing wakeup.
kernel: [203070.272189] Restarting tasks ... done.
acpid: client 5303[0:0] has disconnected
acpid: client 5303[0:0] has disconnected
acpid: client connected from 5303[0:0]
acpid: 1 client rule loaded
anacron[5604]: Anacron 2.3 started on 2010-09-05
anacron[5604]: Normal exit (0 jobs run)
NetworkManager: <info> Waking up...
NetworkManager: <info> (eth0): now managed
NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2)
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: <info> (eth0): supplicant interface state: starting -> ready
NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 42)

------------

The suspend work fine before so I try to check what changes I've made before this happen.

Because I was using for a couple of months MacOS X and there you use the "cmd" key as "ctrl" key y change my keyboard map in System -> Preference -> Keyboard -> Distribution -> Options -> Behavior of Alt/Windows Key -> Control is asigned to Windows Key (selected)

After this the Upper Block Led get always on, and the suspend doesn't work.

I've turned back to the default the Alt/Windows key then restart and everything works OK again.

Julian-

[denis (denis-here)]

Same problem on HP EliteBook 8540p (has a Nvidia video card NVIDIA NVS 5100).

Suspend wakes up right away

PM: Entering mem sleep
Sep 12 15:46:17 denis kernel: [ 216.038201] Suspending console(s) (use no_console_suspend to debug)
Sep 12 15:46:17 denis kernel: [ 216.040556] pm_op(): usb_dev_suspend+0x0/0x20 returns -32
Sep 12 15:46:17 denis kernel: [ 216.040560] PM: Device 3-3 failed to suspend: error -32
Sep 12 15:46:17 denis kernel: [ 216.040563] PM: Some devices failed to suspend

[hyboro (hyboro)]

Suspend to Ram works with kernel commandline option i8042.reset=1
http://www.linlap.com/wiki/acer+travelmate+8471
tested on Acer travelmate 8471, kernel 2.6.32-25-generic #44-Ubuntu SMP

[Mike Rushton (leftyfb)]

i8042.reset=1 did not work on 10.04.1 on a new Dell XPS 17.

[Lorenzo Bernardi (fastlorenzo-gmail)]

Tested on MSI GX660R. Kernel 2.6.37-996-generic #201012161618 SMP x86_64 works fine.
No need of some specific boot options.

[Ville Ranki (ville-ranki)]

EliteBook 8540p, 2.6.38-11-generic #50-Ubuntu SMP and Natty here. Does NOT work.

Even this didn't help:
http://disi.unitn.it/~ferro/index.php/linux/8-suspendhibernate-in-ubuntu-1004-ubs3-problem

[Ville Ranki (ville-ranki)]

Adding SUSPEND_MODULES="xhci_hcd" to /etc/pm/config.d/unload_module seemed to work, as described in
http://www.linlap.com/wiki/hp+elitebook+8540p

[Ville Ranki (ville-ranki)]

This bug still exists in 12.04.

[muted (iataato)]

This bug still exists in 12.04.

but wasn't for me in 10.04
lspci -nn:
00:00.0 Memory controller [0580]: NVIDIA Corporation CK804 Memory Controller [10de:005e] (rev a3)
00:01.0 ISA bridge [0601]: NVIDIA Corporation CK804 ISA Bridge [10de:0050] (rev f3)
00:01.1 SMBus [0c05]: NVIDIA Corporation CK804 SMBus [10de:0052] (rev a2)
00:02.0 USB controller [0c03]: NVIDIA Corporation CK804 USB Controller [10de:005a] (rev a2)
00:02.1 USB controller [0c03]: NVIDIA Corporation CK804 USB Controller [10de:005b] (rev a3)
00:06.0 IDE interface [0101]: NVIDIA Corporation CK804 IDE [10de:0053] (rev f2)
00:07.0 IDE interface [0101]: NVIDIA Corporation CK804 Serial ATA Controller [10de:0054] (rev f3)
00:08.0 IDE interface [0101]: NVIDIA Corporation CK804 Serial ATA Controller [10de:0055] (rev f3)
00:09.0 PCI bridge [0604]: NVIDIA Corporation CK804 PCI Bridge [10de:005c] (rev f2)
00:0a.0 Bridge [0680]: NVIDIA Corporation CK804 Ethernet Controller [10de:0057] (rev f3)
00:0b.0 PCI bridge [0604]: NVIDIA Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0c.0 PCI bridge [0604]: NVIDIA Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0d.0 PCI bridge [0604]: NVIDIA Corporation CK804 PCIE Bridge [10de:005d] (rev f3)
00:0e.0 PCI bridge [0604]: NVIDIA Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
01:01.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev c0)
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1)

lsmod:
Module Size Used by
bnep 17830 2
rfcomm 38139 4
bluetooth 158438 10 bnep,rfcomm
vesafb 13516 1
nvidia 10962290 30
snd_usb_audio 101566 3
snd_pcm 80845 1 snd_usb_audio
snd_page_alloc 14108 1 snd_pcm
snd_hwdep 13276 1 snd_usb_audio
snd_usbmidi_lib 24603 1 snd_usb_audio
snd_seq_midi 13132 0
snd_rawmidi 25424 2 snd_usbmidi_lib,snd_seq_midi
snd_seq_midi_event 14475 1 snd_seq_midi
snd_seq 51567 2 snd_seq_midi,snd_seq_midi_event
snd_timer 28931 2 snd_pcm,snd_seq
snd_seq_device 14172 3 snd_seq_midi,snd_rawmidi,snd_seq
ppdev 12849 0
snd 62064 15 snd_usb_audio,snd_pcm,snd_hwdep,snd_usbmidi_lib,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 14635 1 snd
mac_hid 13077 0
i2c_nforce2 12906 0
parport_pc 32114 1
k8temp 12905 0
asus_atk0110 17742 0
lp 17455 0
parport 40930 3 ppdev,parport_pc,lp
firewire_ohci ...

[penalvch (penalvch)]

co0lingFir3, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]