[Asus 1005HA] Resuming from suspend mode : suspend loop

[Fred Saunier]

Using 13.10 on my laptop (Asus EeePC 1005HA), the system goes into suspend mode when I close the lid. When opening the lid and pressing a key, the system wakes up and asks me for my password. This is the expected behavior.

However, if the laptop is running on battery, the system will go back into suspend mode, within a few seconds ; it will do so each and every time I wake it up subsequently.

If I connect the laptop to its PSU, it is acting as expected when resuming from suspend mode.

I did not experience any such problem with 13.04.

Kernel : Ubuntu 3.11.0-12.19-generic 3.11.3
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fred 3205 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=f25cda9a-ab3e-4873-9752-74587b66e784
InstallationDate: Installed on 2010-05-26 (1245 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer INC. 1005HA
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=cdc8fdab-17fe-413b-a9be-4e534a1e2776 ro quiet splash acpi_osi=Linux elevator=deadline vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic i686
UpgradeStatus: Upgraded to saucy on 2013-10-21 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd04/18/2011:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Fred Saunier (fsaunier)]

Upon further testing, I can add the following details the this 'suspend loop' issue.

- It does not matter if the laptop was running on battery or on power when put into suspend mode for this suspend loop to happen.
- When is 'suspend loop', the network is deactivated (only lo is shown from ifconfig), like bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262

- To exit the suspend loop: disconnect laptop from power, wake it up, enter password, wait for it to go back into suspend mode (after 1 or 2 seconds);
- Connect laptop to PSU, resume from suspend mode

- When exiting properly from suspend mode, the network interfaces are present and running properly.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1243647

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Fred Saunier (fsaunier)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc6-saucy/

[Fred Saunier (fsaunier)]

I am happy to report that upgrading to kernel 3.12.0-031200-generic has fixed the issue.

[Fred Saunier (fsaunier)]

Edit on comment #21 : issue only partially solved.

Upgrading to kernel 3.12.0-031200-generic has only partially solved the issue.

There is no more suspend loop if and only if there is no modification to the power of the computer (power vs battery) between going to hibernation mode and the wake up. In other words, if the computer is on power at the time the lid is closed AND is still on power when woken up, OR the computer is on battery when closing the lid and still on battery when woken up, there is no more suspend loop.

However, IF the system is on power when going to hibernate mode, and the power is removed - resulting in the system going on battery - and the system is then woken up, THEN the suspend loop still happens.

Let me know when you want to me to do any additional testing.

[penalvch (penalvch)]

Fred Saunier, is this partially solved scenario reproducible in the Trusty live environment via http://cdimage.ubuntu.com/daily-live/current/ ?

[Owen Williams (ywwg)]

I am also seeing this on a Dell XPS 13 -- I'm trying a recent kernel to see if it helps

[Owen Williams (ywwg)]

This is not fix with kernel linux-image-3.13.0-999-generic_3.13.0-999.201312110530_amd64.deb on my system. I still get a double suspend:

Lid closed.
Suspending...
Failed to execute operation: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Suspending...
Operation finished.
Lid opened.

[Owen Williams (ywwg)]

Thanks for the information, I'll file a new bug. From your instructions I couldn't figure out which folder to get a kernel from. I don't understand "the one all the way on the bottom," since the daily folder appears on the bottom for me.

[Launchpad Janitor (janitor)]

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