Laptop suspends again after waking up

[Patrick Mertens]

Linux Mint 17 Qiana, Cinnamon Edition (all updates, Linux kernel 3.13.0-35 or 3.13.0-24) on my Asus X53S.

Have it set to suspend when closing the lid, and all working fine so far. Later, when I then open the lid again and press any key, Linux resumes as usual but after a second or so it goes to suspend again, so I have to wake it up by pressing a key again (but then it stays on). Please note that this does not happen every time, maybe when I press a key to quick after opening the lid, not sure.

I've attached the relevant part of my pm-suspend.log if that helps anyone.

[Patrick Mertens (pmertens16)]

One thing to add, I noticed this occuring a bit more recently, something like 3 out of 5 times I open my Laptop... I consider this rather often, if you need another log or something I can easily provide that!

[poine (poinix)]

I am seeing the same bug on my lenovo t61. For me it is happening on every resume. The laptop is equiped with a SSD and resumes quickly. Not sure where to start digging.

[poine (poinix)]

I was seeing that bug with kernel 3.13.0-39-lowlatency. It disappeared after upgrading to 3.17

[Patrick Mertens (pmertens16)]

Thanks for pointing that out! I just upgraded to 3.17. Haven't had this issue so far and wow is that wake up fast!!! So the bug seems to be kernel related, even though it did not appear in Ubuntu 14.04...

[Patrick Mertens (pmertens16)]

Ok nevermind ran into it again on 3.17. Here is the log, probably similar to the one postet above. I'm trying to play around with the power settings a bit, maybe I can find some configuration that works.

[andreyvk (digicraft)]

I have same problem with my desktop computer. Linux mint 17.3, kernel 4.2.0-27.

[Launchpad Janitor (janitor)]

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

[Paul White (paulw2u)]

According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate, this bug should have initially been reported against the Linux kernel so much time has been wasted.

Please don't file bugs against the project as they will seldom see any action.

[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 1379912

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.

[Pavel (ppv)]

ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pavel 1687 F.... pulseaudio
 /dev/snd/controlC0: pavel 1687 F.... pulseaudio
CRDA:
 country RU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5735 - 5835 @ 20), (N/A, 30)
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=e21b20e6-4008-4ca2-9b16-98e05bf885f7
MachineType: ASUSTeK Computer Inc. X55SR
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=16825594-5b5f-4847-a64f-54589ff2bde1 ro quiet
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-92-generic N/A
 linux-backports-modules-3.13.0-92-generic N/A
 linux-firmware 1.127.22
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-92-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom lpadmin plugdev sudo
_MarkForUpload: True
dmi.bios.date: 01/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X55SR
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr202:bd01/14/2008:svnASUSTeKComputerInc.:pnX55SR:pvr1.0:rvnASUSTeKComputerInc.:rnX55SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: X55SR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Pavel (ppv)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 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'.

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/v4.8-rc1

[Pavel (ppv)]

As far as I remember, this issue started happening after installing Ubuntu Trusty with the default Linux 3.13 kernel. After I had upgraded kernel to the 3.19 version (linux-image-generic-lts-vivid), the issue stopped happening. On the Linux 4.4 kernel (linux-image-generic-lts-xenial) this issue did not happen too.
The issue also does not happen on the Linux 4.8.9, 4.8.10 and 4.8.11 mainline kernels. Is it necessary to test the latest 4.9 kernel now?

[Pavel (ppv)]

kernel-fixed-upstream

[TGP1994 (tgp1994)]

This is happening to me, kernel 4.4.0-79. From what I've found searching this issue, it's been a bug for years? Someone on reddit seems to think this is related to systemd-logind: https://www.reddit.com/r/razer/comments/447vrn/razer_blade_stealth_linux/d4zfspx/