Double suspend to ram and system malfunction after 2nd sleep.

[Luis Silva]

After one or two successful suspend-to-ram cycles the system wakes up and immediately goes back to sleep. After this double suspend, some systems like rfkill, for example, will only work after a reboot.

Steps in which I can consistently reproduce the bug:
1. suspend to RAM;
2. Wake up the computer;
3. Repeat 1. and 2. two or more times (sometimes is one cycle, sometimes it's two cycles and I even went 4 cycles without incidents only to have this behaviour on the 5th.)

The double suspend behaviour seems to happen more consistently if a long time (a day or so) goes by between the suspend and the resume.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.18
ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lacsilva 4364 F.... pulseaudio
 /dev/snd/controlC0: lacsilva 4364 F.... pulseaudio
Date: Fri Oct 11 14:37:39 2013
HibernationDevice: RESUME=UUID=cd871376-0405-4aa9-a824-6643baad5594
InstallationDate: Installed on 2012-07-20 (447 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
Lsusb:
 Bus 002 Device 003: ID 04f2:b044 Chicony Electronics Co., Ltd Acer CrystalEye Webcam
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5740
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=8652aded-5fcc-4ed8-9334-dbec7c1b985d ro radeon.audio=1 radeon.dpm=1 splash vt.handoff=7
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
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-09-06 (34 days ago)
dmi.bios.date: 11/26/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.09
dmi.board.name: Aspire 5740
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Rev
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd11/26/2009:svnAcer:pnAspire5740:pvrRev:rvnAcer:rnAspire5740:rvrRev:cvnAcer:ct10:cvrRev:
dmi.product.name: Aspire 5740
dmi.product.version: Rev
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

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-rc4-saucy/

[Luis Silva (lacsilva)]

This bug started happening on Saucy only.
I have been testing the latest v3.12 kernel and can report that the double suspend part of the bug is still there.
However, contrary to the 3.11 kernel, all systems seem to be working properly after resume.

[Cavia Porcellus (caviaporcellus)]

Since I upgraded to 13.10, just after my laptop wakes up from suspend it immediately puts itself back to sleep. I assume this is the same problem. It never happened in 13.04 or previous versions of Ubuntu. I can't vouch for the malfunctioning systems though; haven't noticed anything not working afterwards.

[Andy Buckley (andy-insectnation)]

@Aibara, are you using Lubuntu or Xubuntu? If so, this thread about xfce4-power-manager interacting badly with systemd (with a couple of workaround suggestions) might be useful: http://ubuntuforums.org/showthread.php?t=2184892

Andy

[Cavia Porcellus (caviaporcellus)]

No, regular Ubuntu with Unity.

[Cavia Porcellus (caviaporcellus)]

@Andy, I tried that fix regardless, and it seems to have worked. I don't get why that's the case, since I've never used Xfce or LXDE. I don't even have my laptop set to suspend when the lid is closed. Oh well!

[Launchpad Janitor (janitor)]

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

[Luis Silva (lacsilva)]

This bug was correct at some point in the report version of Kubuntu but is now back in 14.4.

[Cavia Porcellus (caviaporcellus)]

This is indeed still an issue. I upgraded a laptop (Thinkpad T60) from stock Ubuntu 12.04 to 14.04, and while it did not have this problem before, it now does. The workaround suggested in comment #6 seems to have worked though.

[Hans Deragon (deragon)]

Same problem Ubuntu 14.04 LTS running Unity. I cannot figure out what are the two systems that compete with the lid going down. Workaround consist at suspending manually and waiting for suspend to complete before closing the lid.

[Hans Deragon (deragon)]

In my case, here is a scenario to reproduce it.

- Have the laptop configured to suspend upon lowering the lid.
- Suspend the laptop with other means, such as <fn><suspend key>, going through the Unity menu or on a terminal sending 'sudo bash -c "echo mem >/sys/power/state',
- Immediately after the previous step, before the computer has actually suspended, close the lid.

This sequence of events sends two 'suspend' signals. Thus when resuming from the first one, the system suspends again.

The fix: The kernel / OS should ignore a suspend/hibernate/poweroff request if any of these is already in progress.

[Robert Jansen (rj6603)]

Aloha, is there anybody in there. It is April 2016.
The problem started after 12.04. That is 4 years and 2 LTS releases ago.
OpenSUSE does not have this problem.

Is there antbody in there ?

Does anybody ever actually read these bug reports ?