Suspend failure

Bug #1570820 reported by petersaints
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on).

I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked.

Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug.

I'll gladly perform any testing procedures that you may need to try to identify what the problem may be.

I really hope that you are able to fix this soon, even if it will probably after the final release.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-18-generic 4.4.0-18.34
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pedro 2579 F.... pulseaudio
CurrentDesktop: GNOME
Date: Fri Apr 15 12:39:05 2016
HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18
InstallationDate: Installed on 2015-10-27 (170 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-18-generic N/A
 linux-backports-modules-4.4.0-18-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P05ADH.017.140421.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP870Z5E-X01PT
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 870Z5E/880Z5E/680Z5E
dmi.product.version: P05ADH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
petersaints (petersaints) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
petersaints (petersaints) wrote :

Meanwhile I tried to install the latest 4.4.x mainline kernel and it works nicely.

uname -a
Linux alpha 4.4.7-040407-generic #201604121331 SMP Tue Apr 12 17:33:19 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

The official 4.4.0-18-generic kernel is based on which mainline kernel?

Revision history for this message
petersaints (petersaints) wrote :

So I just found this site "Ubuntu to Mainline kernel version mapping" that the official 4.4.0-18 kernel is based upon the updstream 4.4.6 kernel. So I just tried installing that version and suspend is broken. So this is something this must be something that was fixed upstream between 4.4.6 and 4.4.7.

I'm not knowledgeable enough to go through all the commits between 4.4.6 and 4.4.7 and find out exactly which one fixed the bug so that you can create a patch for it. However, I did find out that the word "suspend" is mentioned a few times in the 4.4.7's changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.7 So maybe someone else can pick up whatever is needed to fix the kernel suspend issues that I'm facing and import it as a patch to the official kernel. Or maybe you can rebase the oficial kernel to the 4.4.7 version after the oficial LTS release. I don't know if that's possible since I'm not aware of the kernel update policy.

Revision history for this message
petersaints (petersaints) wrote :

-- PLEASE DISREGARD MY PREVIOUS COMMENT --

The suspend issue is not present on 4.4.6 mainline kernel. So this must be some issue with some additional patching that is done to the official kernel. Meanwhile, I also went back to the 4.4.5 kernel and it suspends and resumes flawlessly.

----
Besides that, I noticed that 4.4.7 is not without its share of problems. First of all, it displays an error on boot stating that radeon VCE failed to initialize (I have a dedicate AMD GPU on my laptop, besides the Intel GPU bundled with the CPU). This is a minor thing (I guess). However, the more concerning issue I noticed is that resuming from a suspended state, I just can't shutdown or reboot the system. It freezes while shutting down on a black screen with a white blinking cursor. I waited for a while and nothing happened. This is probably unrelated with the rest of the bug. Notwithstanding, I thought that I should mention it just so that you are aware that 4.4.7 also introduces a few issues, even though it seems to be unaffected by the suspending issues that I've been facing on the official 4.4.0-18 kernel.

tags: added: kernel-fixed-upstream
Revision history for this message
petersaints (petersaints) wrote :

I found some possible duplicates or related bugs:
#1566302
#1565994
#1561301 (Same laptop series as mine)
#1560202
#1559469

Revision history for this message
petersaints (petersaints) wrote :

I added the "kernel-fixed-upstream" because the bug is also fixed on the latest upstream kernel available at http://kernel.ubuntu.com/~kernel-ppa/mainline/, which is 4.6.0rc3 at this time.

However, please note that the shutdown/reboot issues that I found on 4.4.7 (comment #5) are also present on this kernel.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
status: Incomplete → Triaged
Revision history for this message
Ralph (axllent) wrote :

The latest v4.6-rc4-wily kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/) fixed the issue for me. Now my laptop suspends, resumes and reboots without an issue again.

Revision history for this message
Jean-Max Reymond (jmreymond-free) wrote :

Same issue and the test with the latest v4.6-rc4-wily kernel is not full OK
If I close the top of my laptop, the bug is still present but if I select the menu entry "Go to sleep", it is now OK

Revision history for this message
Peter Ries (peterriesde) wrote :

Same effect here as you described (Samsung Ativbook 7 730U3E with Intel/ATI graphic). Xubuntu 15.10 with all the updates worked. After upgrading to 16.04 suspend stopped working.

Due to some issues with systemd during the upgrade I did a fresh install of 16.04 Xubuntu but ran into the same suspend problem.

I hope you can fix this in the official Kernel as I'd like to stick to the "original" an 16.04 is a LTS version.

I guess petersaints gave enough information (thanks for this!) - I just want to push this with my vote :-)

Revision history for this message
petersaints (petersaints) wrote :

@peterriesde
My thoughts exactly. I want to avoid having to run an unofficial kernel. I mean, on one hand I'm glad that I was able to find a work around (other than switching to another distro, since from I tested 2 other 4.4 based distros that don't appear to have this problem), but I'd rather be using the official supported kernel for added stability and security.

The latest official kernel that was pushed to proposed (4.4.0-22.38), which is based on 4.4.7, still has this same bug, even though the mainline 4.4.7 doesn't. However, it has another (unrelated) bug regarding the my AMD Radeon HD 8870M, which doesn't happen on the xenial-proposed build. Strange stuff...!!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.