3.13.0-149-generic: suspend/resume issue on 14.04

[Kevin Donnelly]

On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot.

The 144 kernel is OK, and this question:
https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04
suggests that 147 is OK too.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1774150

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.

[Jan-Pieter (jpieter)]

I have exactly the same issue with an MSI MS-1492 (GE40). I'll run the command and change the status.

[Jan-Pieter (jpieter)]

Ah... while submitting the info I figured out it is apparently the idea to create a new bug and mark it as duplicate... Will do so.

[Jan-Pieter (jpieter)]

New bugreport created: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583

[Bruno Sevennec (bsevenne)]

I also have the same issue with a Clevo laptop (W55xEU).

[Kevin Donnelly (donnek)]

Sorry, I can't generate the log files:
$ apport-collect 1774150
ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyKDE4.kdecore

[Gerd Bavendiek (gerd-bavendiek)]

ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bav 2145 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=a9a9ea54-d360-476c-b598-fd19723969cf
InstallationDate: Installed on 2014-07-24 (1412 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Shuttle Inc. DS437
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=8395af97-4ad8-4e0c-8fd4-ac1f64aaa902 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-149-generic N/A
 linux-backports-modules-3.13.0-149-generic N/A
 linux-firmware 1.127.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-149-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.01
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FS437
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd09/25/2013:svnShuttleInc.:pnDS437:pvrV1.0:rvnShuttleInc.:rnFS437:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: DS437
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

apport information

[Gerd Bavendiek (gerd-bavendiek)]

This affects me too. No laptop here, but a Shuttle FS437. Used to work rock solid all the time.

I ran apport-collect 1774150 succesfully.

[Jan-Pieter (jpieter)]

FYI: after installing the latest updates (containing kernel 3.13.0-151-generic) it all seems to work fine again for me.

[Bruno Sevennec (bsevenne)]

Same issue now on a Dell desktop with Lubuntu, and kernel 3.13.0-151 didn't solve it, unfortunately.

[Bruno Sevennec (bsevenne)]

Unable to give apport info, but wakeup on a console also hangs, writing more and more infrequently messages containing "perf samples too long" with numbers in the 1.5 million and "lowering kernel.perf.event_max_sample_rate" from 500,000 then 250,000 all the way down to 250.

In the beginning I also saw "perf_event_nmi_handler took to long to run 208.309 ms".

Hope this helps.

[Bruno Sevennec (bsevenne)]

In case it helps (which I doubt, this would be too simple), I restored wakeup after suspend by downgrading intel-microcode 3.20180425.1 to previous version 2.20140122.1

I found it by listing/examining the updates made to the system in days preceding the malfunction, a possibility I didn't find in synaptic or software center (they seem to care only about their own activity). I sorted down possible culprits to procps (and a dependency) or intel-microcode (and iu-tools from backports, which was listed as modified the same day but not updated, strangely). Turns out procps wasn't responsible (for me).

HTH (with doubts).

[spacefight (spacefight)]

I am also affected on Thinkpad T440p on 3.13.0-151-generic. Couldn't submit via apport.

[spacefight (spacefight)]

How would you do the downgrade of the intel-microcode?

[spacefight (spacefight)]

Will this bug get assigned? It totally breaks the daily workflow routine while on the move etc.

[kovserg (kovserg33)]

I've reinstall ubuntu from 14.04 to 14.04.5 and have same problem notebook (Asus N56VJ). After it suspend it unable to resume. Only black screen and no reaction caps lock. Previous version work fine with all kernels it updates.
Setting kernel in grub GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 3.13.0-147-generic" did not help. It hungs when resume.

[Kevin Donnelly (donnek)]

The latest 13.0.151 kernel has the same issue, at least on this laptop. This also means that whatever security updates are rolled into the mainline kernels are in effect inaccessible to laptop users affected by this issue. :-(

[Bruno Sevennec (bsevenne)]

Sorry to be late, but to downgrade intel-microcode I used synaptic, which in the packages menu has the option to force version of a package and then (after applying change) to hold it against updates. I chose the only other version listed (2.2014something) and it worked. Hope this helps.

[spacefight (spacefight)]

Thanks Bruno. I now hesitate to downgrade the microcode - since in there are some new CPU design flaw mitigations if I remember correctly.

[kovserg (kovserg33)]

Thank you. Now resume works fine. This helps:

sudo apt-get install intel-microcode=2.20140122.1

But now ubuntu wants to upgarade it back to 3.20180425.1 on every update.

[kovserg (kovserg33)]

To pin intel-microcode version:

echo "intel-microcode hold" | sudo dpkg --set-selections

[spacefight (spacefight)]

I can confirm that the downgrade helped. But then again - is anyone looking into a regression on the new version? I'd rather have the newest microcode, not the one from 2014.

[Peter Antoniac (pan1nx)]

I also confirm that the downgrade of the microcode helped. So the issue seems to be with the intel-microcode version 3.20180425.1~ubuntu0.14.04.1. Version 2.20140122.1 seems to work well. So the security-updates is the cause of all this trouble...

[Matheus S. Fontana (fontanams)]

I had to use kernel 3.13.0-157 to have suspend + newest microcode working together without problems. Newer kernel versions would freeze after suspend.

I downgraded microcode to 2.20140122.1 and then I could use the newest kernel version to this date (3.13.0-162) without problems after suspend.