Suspend only works once, fails second time

[Sascha]

Binary package hint: pm-utils

had this problem now since 10.10 64 bit, and I was hoping it would go away in Natty 64 bit, but it didn't.

In short: Suspend only works once, the second attempt at a suspend results in the monitor going blank as it was entering suspend, but the computer still running, as evidenced by the hard drive and fans still running. The computer can then not be awaken anymore, only a hard reset and subsequent reboot returns the PC to working state.

When I check for errors after the first suspend, I see the following errors in the log:
Code:

[ 8461.100062] ahci 0000:05:00.0: failed to stop engine (-5)
[ 8461.600062] ahci 0000:05:00.0: failed to stop engine (-5)
[ 8463.170076] ata9: failed to resume link (SControl FFFFFFFF)
[ 8463.170109] ata10: failed to resume link (SControl FFFFFFFF)
[ 8467.510109] ata9: failed to resume link (SControl FFFFFFFF)
[ 8467.510163] ata10: failed to resume link (SControl FFFFFFFF)

So it seems to me that it has something to do with AHCI. I searched for this error in the forum, but I could not find anything. I also tried various suggestions, such as using uswsusp and the hibernate scripts, and including ahci in the suspend module lust. But each of the result in the exact same behavior: First suspend works fine, second suspend fails and reset is necessary.

My Hardware configuration:
- AMD Phenom II 965
- GeForce GTX 460
- GA-880GA-UD3H
- 8 GB DDR RAM
- SAMSUNG HD103SJ

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: pm-utils 1.4.1-7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu May 12 22:09:42 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[robik (bigkahunaburger)]

Confirmed on Asus S6F notebook for both standby and suspend.
Attached dmesg output for standby.

The relevant lines:

[ 251.348088] PM: Entering mem sleep
[ 251.348130] Suspending console(s) (use no_console_suspend to debug)
[ 251.348966] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 251.349845] sd 0:0:0:0: [sda] Stopping disk
[ 251.436092] legacy_suspend(): pnp_bus_suspend+0x0/0x90 returns 38
[ 251.436097] PM: Device 00:0b failed to suspend: error 38
[ 251.436100] PM: Some devices failed to suspend
[ 251.436336] sd 0:0:0:0: [sda] Starting disk

[Witold Krecicki (wpk)]

I have the same problem on Dell Latitude E6500. It was working perfectly on 11.04, bug was introduced in 11.10.

[gcb (gcb0)]

Asus X202E, clean install of ubuntu 12.10 with UEFI

dmesg:

[ 3032.321251] PM: Syncing filesystems ... done.
[ 3032.323632] PM: Preparing system for mem sleep
[ 3032.338265] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 3032.354246] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[ 3032.370239] PM: Entering mem sleep
[ 3032.370713] Suspending console(s) (use no_console_suspend to debug)
[ 3032.371233] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 3032.384156] alx 0000:03:00.0: PHY SPD/DPLX unresolved :ffff
[ 3032.384158] alx 0000:03:00.0: eth0: shutown err(ffffffea)
[ 3032.384160] alx 0000:03:00.0: shutdown fail in suspend -5
[ 3032.384172] pci_pm_suspend(): alx_suspend+0x0/0x90 [alx] returns -5
[ 3032.384176] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -5
[ 3032.384180] PM: Device 0000:03:00.0 failed to suspend async: error -5
[ 3032.472044] sd 0:0:0:0: [sda] Stopping disk
[ 3032.502194] PM: suspend of drv:snd_hda_intel dev:0000:00:1b.0 complete after 118.461 msecs
[ 3033.053917] PM: suspend of drv:sd dev:0:0:0:0 complete after 682.570 msecs
[ 3033.054095] PM: Some devices failed to suspend
[ 3033.054263] mei 0000:00:16.0: irq 42 for MSI/MSI-X
[ 3033.054468] sd 0:0:0:0: [sda] Starting disk
[ 3033.060968] mei 0000:00:16.0: wd: failed to find the client
[ 3033.066357] i915 0000:00:02.0: setting latency timer to 64
[ 3033.066398] snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
[ 3033.121841] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 3033.742281] PM: resume of drv:scsi_device dev:0:0:0:0 complete after 687.679 msecs
[ 3033.742284] PM: resume of drv:scsi_disk dev:0:0:0:0 complete after 605.892 msecs
[ 3033.742425] PM: resume of devices complete after 688.197 msecs
[ 3033.742529] PM: resume devices took 0.692 seconds
[ 3033.742719] PM: Finishing wakeup.
[ 3033.742720] Restarting tasks ... done.
[ 3033.745885] video LNXVIDEO:00: Restoring backlight state
[ 3034.054757] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3036.127588] wlan0: authenticate with 00:26:5a:fb:47:7f
[ 3036.136032] wlan0: send auth to 00:26:5a:fb:47:7f (try 1/3)
[ 3036.138151] wlan0: authenticated
[ 3036.146782] wlan0: associate with 00:26:5a:fb:47:7f (try 1/3)
[ 3036.150063] wlan0: RX AssocResp from 00:26:5a:fb:47:7f (capab=0x411 status=0 aid=4)
[ 3036.150148] wlan0: associated
[ 3036.150687] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 3139.296578] CPU0: Package power limit notification (total events = 110)
[ 3139.296580] CPU2: Package power limit notification (total events = 110)

i guess the offending device was the ethernet? lspci:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Device 0153 (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset...

[gcb (gcb0)]

Confirmed it was the device: 03:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)
(at least in my case, as the original reporter have a realtek not an atheros, maybe it's something on the network stack... maybe some code that tries to keep network somewhat up for wake-on-lan?)

i disabled it in BIOS and now i can suspend/resume more than once. (only tested twice so far, will report if it fail again without that device.)

here's my lspci output now, with suspend/resume working

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Device 0153 (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

[gcb (gcb0)]

Oops, no, on the original reporter case it has nothing to do with ethernet or network. his culprit device seems to be the Sata controller, if i read his data correctly.

his dmesg:
[ 8461.100062] ahci 0000:05:00.0: failed to stop engine (-5)

hist hwinfo:
                description: SATA controller
                product: JMB362/JMB363 Serial ATA Controller
                vendor: JMicron Technology Corp.
                physical id: 0
                bus info: pci@0000:05:00.0

[penalvch (penalvch)]

Sascha, thank you for reporting this bug to Ubuntu. Natty reached EOL on October 28, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in the latest release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ ?

If so, please execute the following via a terminal in order for the necessary debugging information to be attached:
apport-collect 781977

[rewound (rewound)]

Ubuntu 14.04 (trusty) Kernel 3.13.0-44-generic
HP laptop Compaq nx6325
A working suspend via Applications Menu/Log Out results in power switch green LED blinking on/off every few seconds.
The laptop will do this the first time after a reboot but then every second attempt to suspend results in power switch green LED staying on.
Screen goes black and have not found any key sequences that respond.
The only option is to hold the power switch down for several seconds to do a hard reset.
On restart it says...
System program problem detected
Report problem
Clicked above several times, nothing happens, eventually pop up(s) go away.
After this a dmesg doesn't seem to give clues - it does not even contain the word suspend for instance.
Following the reboot the laptop will now suspend correctly once, wake up ok but then fail to suspend when asked the second time. What clues to search for to suspend everytime?

[penalvch (penalvch)]

rewound, thank you for your comment. So your issue may be dealt with as soon as possible, and so your hardware may be tracked by having necessary debugging information automatically attached, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu repository kernel via:
ubuntu-bug linux

For more on why this is most helpful, please read the official Ubuntu documentation from the respective Ubuntu developer groups, and triage teams:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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