Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

Bug #1566302 reported by macias
This bug affects 211 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm using ubuntu 16.04 on a XPS 15 9550.

Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something.

Booting with 4.4.0-15 makes the suspend to work perfectly.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: macias 1770 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Tue Apr 5 14:56:17 2016
HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
InstallationDate: Installed on 2016-03-07 (28 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-15-generic N/A
 linux-backports-modules-4.4.0-15-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.01.19
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

Revision history for this message
macias (macias-depeca) 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
Joseph Salisbury (jsalisbury) wrote :

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.6 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.6-rc2-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
macias (macias-depeca) wrote :

Yes, the issue start happening after update to 4.4.0-16 on 5/04/2016 (morning update). The problem did not happened with 4.4.0-15.

I tested uptream kernels 4.5 and 4.6 and I didn't have the freeze after suspend. Actually, yesterday night (5/04/2016) there was another ubuntu update (including kernel update to 4.4.0-17) and I can confirm that the bug seems to be fixed also for 4.4

I then booted again with the supposedly buggy kernel 4.4.0-16, and I couldn't replicate the bug, so my guess is that the bug reason was not actually in the kernel, but due to some other package.

So: the bug seems to be fixed with the ubuntu distribution as of yesterday night (kernel 4.4.0-16 and whatever additional updated packages). Also fixed for 4.5 and 4.6.

Thanks for your time and great work!

Revision history for this message
Bruno Jesus (brunojesus) wrote :

In my case none of the 4.4 kernels have suspension working, but in 4.6 it's working fine.

I also have a Dell but it's an Inspiron 17R-5737.

Revision history for this message
Jeroen van der Gun (jeroen-0) wrote :

I have similar experiences since I upgraded from Ubuntu 15.10 to 16.04. I can no longer suspend or hibernate, the screen goes black but the PC stays on, heating up and triggering the fan after a while.

When I run Ubuntu 16.04 with kernel 4.2.0-35-generic (which was still installed) instead of kernel 4.4.0-21-generic, the problem does not occur, so I've uninstalled 4.4.0-21-generic for now until there's a better solution. I have no kernel versions in between available in my package manager.

Ubuntu 16.04 xenial (x86-64)
Cinnamon 2.8.6
Kernel 4.4.0-21-generic
Processor AMD A8-5550M APU with Radeon(tm) HD Graphics x 2
7.0 GiB memory
315 GB hard disks
Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8550G] (prog-if 00 [VGA controller]) graphics card
No proprietary drivers in use
For completeness: unlike suspend, hibernate has never worked perfectly (screen would stay black after resume, workaround to wake up screen was suspend and resume from suspend)

Revision history for this message
BobbyHo (bobbyho) wrote :

I'm using Ubuntu 16.04.
I can wake up from suspend in 4.6, but not in 4.4.0-35.

tags: added: regression-update
Revision history for this message
Petr Gladkikh (petrglad) wrote :

I have this problem since upgrade from 15.10 to 16.04

I have disabled discrete video card in bios and now use Intel HD graphics only. With this configuration suspend works.

My environment Xubuntu 16.04, kernel 4.4.0-21-generic

Revision history for this message
Jeroen van der Gun (jeroen-0) wrote :

I also tried upstream kernel 4.5.2-040502-generic, which solves the problem except that it cannot wake up from hibernate. So I'm sticking with 4.2.0-35-generic for now.

Revision history for this message
Christian Prim (christian-prim) wrote :

I can confirm, that kernel 4.6.0-040600rc5-generic solves the problem on Dell Inspiron N5110 (latest BIOS A11). Kernel 4.4.0-21-generic fails to suspend on newest BIOS. On my Inspiron I have no BIOS options to disable the discrete video card.

Revision history for this message
milton hagler (miltonh26) wrote :

On my Asus U44S optimus laptop with Nvidia Geoforce GT 610M kernel 4.5.2 -040502-generic solve the issue for me.

Revision history for this message
Olivier Febwin (febcrash) wrote :

Same here: Dell Latitude E6520

Revision history for this message
Braiam Peguero (braiampe) wrote :

macias, since you were able to find that the issue was fixed upstream, could you follow the procedure that Joseph explained? Specifically:

> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

and

> Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

This will allow the team to pinpoint what went wrong, and offer a solution for everyone else.

Revision history for this message
mookey41 (redguy41) wrote :

Same here, 4.4. kernel on Ubutnu 16.04 LTS and Lenovo z51-70 80K, i5.

macias (macias-depeca)
tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Installing recent Kernel 4.4.9 also resolves the issue. Suspend and Hibernate works.
Dell Inspiron 15R 5537.

Revision history for this message
Mochamad Syarief Maulana (alanmsm) wrote :

Confirming that this bug occurred at all 4.4.0 kernel, including the latest 4.4.0-22 kernel update.

Installing newer kernel solve the issue.

Revision history for this message
Roygbiv (silentvoice37) wrote :

I can also confirm that the bug persists even after the 4.4.0-22 kernel update. (Dell Inspiron 15)

Revision history for this message
claudio (cardi-93) wrote :

I also confirm for samsung series 7 ultra

Revision history for this message
Mattias Lindskog (mattias-f-lindskog) wrote :

Confirming that this bug also appears on HP ZBook 15u G2 with the 4.4.0-22 kernel.

Revision history for this message
rim (rim-a) wrote :

I can also confirm for Lenovo C560 (Kubuntu 16.04). I've tried 4.4.0, 4.4.6, 4.4.8, 4.5.3, 4.6-rc7 kernels. but it didn't help

Revision history for this message
Kaushik Evani (kaushik-evani) wrote :

I can confirm that I also had the issue with 4.4.0. Recent upgrade to 4.4.9 has fixed the issue!

Revision history for this message
El Pocho (elpochodelagente) wrote :
Revision history for this message
ianholing (ianholing) wrote :

I've never install an updated package manually which I already have into system packages. Will this manual update block the future patch update?

Revision history for this message
Rien Heuver (rienheuver) wrote :

I have this problem too on Dell XPS 13 (9350 model). Tried kernels:
4.4.2
4.4.8
4.4.9
None fixed it for me. Neither did I find a kernel that does (yet).

Revision history for this message
Rien Heuver (rienheuver) wrote :

Update: I just tried 4.6 RC7 and it didn't fix it either.

Revision history for this message
Álvaro Guimarães (alvaroguimaraes) wrote :

What is the normal schedule to fix this bug for 16.04 users?

If I decide to install the 4.4.9 packages elpocho indicated, will it block the official package to be upgraded via apt-get dist-upgrade?

Revision history for this message
Ismail Gjevori (isgjevori) wrote :

I think that the importance of this bug should be High...
@alvaroguimareaes https://wiki.ubuntu.com/Kernel/MainlineBuilds

Revision history for this message
raphael (raphdruon) wrote :

I'm using a Dell Inspiron 5537, it hangs only the second time I try to suspend it.
I tried kernels 4.4.8 and 4.4.9

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Strange raphael, I also have a Dell Inspiron 5537 and all works with Mainline Kernel 4.4.9. I can suspend and hibernate lots of times with no problem!?!?
I think is related to ati radeon graphis card! I don't need it so I turn it off in /etc/rc.local with the command "echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch".
If it's Your case try it and see if works for you.

Revision history for this message
Rien Heuver (rienheuver) wrote :

Perhaps that's the case for the Inspiron model(s), but definitely not for all devices nor Dell models. My Dell XPS 13 (9350) has Intel HD Graphics but this bug too.

Revision history for this message
raphael (raphdruon) wrote :

Thanks cascagrossa #29 , this solved my problems :-)

Revision history for this message
Claudio Pacchierotti (cpacchierotti) wrote :

Bug confirmed on 4.4.0-22.

Dell 7000, with
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265]

Revision history for this message
Miguel A. Martinez (migmartri) wrote :

I can confirm the issue in my Dell XPS 13 9350

Kernel version: 4.4.0-22-generic

Revision history for this message
bill (bill-zannoni) wrote :

I confirm that here the problem is still there with kernel 4.4.0-22, I have a Lenovo ThinkPad S540 with i7 and:
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330]

I first noticed the problem with kernel 4.4.0-21, but I can't be sure with which update it appeared. What I can say is that if I start with kernel 3.16.0-34 (only other version of the kernel I Have a part from 4.x) suspension feature work normally.

Revision history for this message
adutzu89 (verbanady) wrote :

Confirming here also, Ubuntu 16.04 fresh install, with Kernel 4.4.0-22-generic on a Dell Inspiron 15 5555

Revision history for this message
Michele (michele-spartano) wrote : Re: [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Download full text (6.0 KiB)

I confirm this bug on Thinkpad S540.
System specs:

-Computer-
Processor : 4x Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz
Memory : 7817MB (3057MB used)
Operating System : Ubuntu 16.04 LTS
Date/Time : mer 18 mag 2016 09:13:04 CEST
-Display-
Resolution : 1920x1980 pixels
OpenGL Renderer : Mesa DRI Intel(R) Haswell Mobile
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel HDMI
Audio Adapter : HDA-Intel - HDA Intel PCH
-Input Devices-
 Power Button
 Lid Switch
 Power Button
 AT Translated Set 2 keyboard
 Video Bus
 Video Bus
 SynPS/2 Synaptics TouchPad
 Logitech USB Receiver
 Logitech USB Receiver
 ThinkPad Extra Buttons
 HDA Intel HDMI HDMI/DP,pcm : 3=
 HDA Intel HDMI HDMI/DP,pcm : 7=
 HDA Intel HDMI HDMI/DP,pcm : 8=
 SYNAPTICS Synaptics Large Touch Screen
 HDA Intel PCH Mic
 HDA Intel PCH Headphone
 Integrated Camera
 TPPS/2 IBM TrackPoint
PDF : <i>Default</i>
-SCSI Disks-
ATA SAMSUNG MZ7TE256

-Version-
Kernel : Linux 4.4.0-22-generic (x86_64)
Compiled : #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016
C Library : Unknown
Default C Compiler : GNU C Compiler version 5.3.1 20160413 (Ubuntu
5.3.1-14ubuntu2)
Distribution : Ubuntu 16.04 LTS
-Current Session-
Computer Name :
Desktop Environment : Unity (ubuntu)
-Misc-
Uptime : 8 minutes
Load Average : 0,00, 0,00, 0,00

$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated
Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller
(rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev
04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev
04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev
e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev
e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev
e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev
e4)
00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev
e4)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI
mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227
PCI Express Card Reader (rev 01)
06:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT
[Radeon HD 8670A/8670M/8690M / R5 M330]

=========================

*Michele Spartano*

OSCP certified

Email: <email address hidden>

Mobile: +39 3484023371

2016-05-17 19:01 GMT+02:00 adutzu89 <email address hidden>:

> Confirming here also, Ubuntu 16.04 fresh install, with Kernel
> 4.4.0-22-generic on a Dell Inspiron 15 5555
>
> --
> You received this bug notification becaus...

Read more...

Revision history for this message
Sergio Callegari (callegar) wrote :

Same issue here: DELL Precision T5400 with nvidia graphics cannot suspend anymore after upgrade to xenial.

Revision history for this message
ronexus (ronexus) wrote :

Same issue here: Thinkpad T410 with nvidia graphics cannot suspend anymore after upgrade to xenial.
Tested with 4.4.0-21-generic & 4.4.0-22-generic

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :
Revision history for this message
capaj (capajj) wrote :

I have Dell inspiron and I can confirm this bug as well. Started after upgrading to 16.04. My uname -r prints out:
4.4.0-22-generic

Will test with a newer one.

Revision history for this message
capaj (capajj) wrote :

I had the same problem after updating to 16.04. My kernel was
4.4.0-20

After I downloaded kernel 4.4.9 posted here by @elpochodelagente it works like a charm. Thank you so much.

Revision history for this message
Haakon Nilsen (haakonn) wrote :

Confirming: resume wasn't working on default 4.4.0 kernels in Xenial. Installed 4.4.11 mainline, and now it works.

Revision history for this message
Michele (michele-spartano) wrote :
Download full text (3.4 KiB)

I confirm that the suspend issue is fixed in the kernel 4.4.11. I got it
from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.11-xenial/

=========================

*Michele Spartano*

OSCP certified

Email: <email address hidden>

Mobile: +39 3484023371

2016-05-20 9:03 GMT+02:00 Haakon Nilsen <email address hidden>:

> Confirming: resume wasn't working on default 4.4.0 kernels in Xenial.
> Installed 4.4.11 mainline, and now it works.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1578135).
> https://bugs.launchpad.net/bugs/1566302
>
> Title:
> Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
> 4.4.0-16
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I'm using ubuntu 16.04 on a XPS 15 9550.
>
> Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
> standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
> the system freezes when attempting a suspend. I get no response from
> the system (nor keyboard, nor screen, nor touchpad), but it gets very
> hot, so that it must be running something.
>
> Booting with 4.4.0-15 makes the suspend to work perfectly.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
> ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
> Uname: Linux 4.4.0-15-generic x86_64
> ApportVersion: 2.20.1-0ubuntu1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: macias 1770 F.... pulseaudio
> CurrentDesktop: X-Cinnamon
> Date: Tue Apr 5 14:56:17 2016
> HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
> InstallationDate: Installed on 2016-03-07 (28 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160304)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
> Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
> Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Dell Inc. XPS 15 9550
> ProcEnviron:
> LANGUAGE=es_ES
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=es_ES.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed
> root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.4.0-15-generic N/A
> linux-backports-modules-4.4.0-15-generic N/A
> linux-firmware 1.157
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/25/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 01.01.19
> dmi.board.name: 0N7TVV
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A00
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc...

Read more...

Revision history for this message
Zaphod (flerche) wrote :

For my Machine (Lenovo Thinkpad X201) 4.4.0-21 works with minor glitiches, 4.4.0-22 breaks it: Graphic errors after resume, correction requires reboot.
4.2 (used on the 14.04-Installation before) worked perfectly. 4.4 on the 14.04 worked with glitches.

Revision history for this message
claudio (cardi-93) wrote :

4.4.9 works on smasung series 730 ultra

Revision history for this message
Mattia (io-mattia98) wrote :

4.4.9 works with glitches:
- Mouse pointer not visible after resume. Need to Ctrl+Alt+F1 and the Ctlr+Alt+F7.

Please fix this and merge the fixes into the kernel of the official repo so everyone can finally suspend their pcs without installing some kernel downloaded from a launchpad bug report.

Please and thank you

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Currently tested with LTS mainline kernels 4.4.9, 4.4.10 and 4.4.11.
They all work with the ATI Radeon disabled with the command "echo" OFF "> / sys / kernel / debug / vgaswitcheroo / switch" on "/etc/rc.local" file.
Dell 15R Inpiron 5537.

Revision history for this message
jose (o1485726) wrote :

Affects my system too, a HP Pavilion laptop, model dv6-6174la (AMD APU + dedicated GPU), running linux-lts-xenial on Kubuntu 14.04. I can suspend just fine with Linux 4.6.0-040600-generic from the mainline repo.
There are LOTS of reports of problems with suspend/resume related to kernel 4.4...

Revision history for this message
jose (o1485726) wrote :

I can also confirm that Linux 4.4.9-040409-generic does suspend just fine.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Same thing with a Samsung 700Z3A/700Z4A/700Z5A/700Z5B. Fixed by upgrading to 4.4.8 kernel; followed instructions in comment #22 fixed the problem completely.

Revision history for this message
raxp (raxp) wrote :

Same thing WAS on Asus U31Sg with kernel 4.4.0-21. I don't have this issue on 4.4.0-22 or 4.6.0. On the 2nd or 3rd suspend it freezes, no response from anything. All I can do is to hold power button to turn it off.
This device has a HM65 Intel chipset.
Some responses from here are related to video card, so, it has an NVIDIA 610M and I'm using it with nouveau driver.

Revision history for this message
Paolo Pustorino (stickgrinder) wrote :

Same here on Dell Inspiron 7548. Installing mainline 4.6 yakkety solved the problem to mee too.
I'd like to stay with official kernel but until this is fixed I will stick to mainline...

Revision history for this message
Miro Janosik (miro-janosik-geo) wrote :

Experiencing the same on my desktop of xubuntu 16.04, where I have core 4.4.0-21. Fixed by rebooting into older available core (in my case '4.2.0-30').

Revision history for this message
Edgar (edgar-dev) wrote :

The kernel 4.5.2 solved the problem in my laptop, a Dell Inspiron 7520. The kernel 4.4.0 seems to be the reason of the problem.

Revision history for this message
Ismail Gjevori (isgjevori) wrote :

I'm using kernel 4.4.11 from Kernel MainlineBuilds and the suspend works. I can say that also the PC is a lot cooler, with the default kernel(4.4.0....) the fan was working almost all of the time.

Revision history for this message
David Southwood (ds-mailbag) wrote :

Experiencing the same on my desktop of ubuntu 16.04, where I have core 4.4.0-22

Revision history for this message
Guilherme Flach (guilherme-augusto-flach) wrote :

The kernel 4.6 solved the issue in my Dell Inspiron 15 7000 series (with nVidia) laptop.

Revision history for this message
StefanoG (stefano-gadaleta) wrote :

Kernel 4.6 not solved with my Dell Inspiron 531 ATI Radeon X1600.

Revision history for this message
Lucas B. (benja-junin) wrote :
Revision history for this message
jose (o1485726) wrote :

I'm wondering: since canonical people in launchpad.net insist on creating new bug reports for different issues, and this one seems to be solved for the op (comment #4) but not for everyone else (and people seem to have different experiences: for some, not even 4.6 fixes it, some still report freezes after a couple of suspend/resume cycles), should we make new bug reports?

Also, is ANYTHING being done about this bug?

Revision history for this message
bastien (bastien-bernard) wrote :

Indeed, there seems to be different problems. Personally I did not find a kernel on which it works, even on 4.6. But it works fine on 4.2.
Is there a fix planned? This bug is critical!

Revision history for this message
Tomas Kral (kralutomas) wrote :

I can confirm this on Lenovo z50-70, kernel 4.4.0-22.

Revision history for this message
Guex (guex) wrote :

>Is there a fix planned? This bug is critical!

the bugs is still "unassigned" and only on medium importance..
i'd really love to see this fixed on default kernel, rather than installing one of mainlinebuild kernels.
my family is affected on 3 devices.

- Samsung 700 series notebok with intel/nvidia hybrid card
- IBM thinkpad Z61p with radeon fireGL
- desktop with core i7 and GeForce GTX 960

Revision history for this message
Geraldo Luiz (geraldolmr) wrote :

The same problem occurs in a Sony Vaio VPCSA laptop (i5, 6 Gb RAM), with the following configuration, using kernel 4.4.0-22 with Ubuntu 16.04. I've changed back to version 4.2.0-35 and the problem's gone. I hope you find a solution soon.

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

Revision history for this message
penalvch (penalvch) wrote :

macias, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

tags: added: bios-outdated-01.02.00 kernel-fixed-upstream-4.6-rc2 needs-reverse-bisect
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Guex (guex)
Changed in linux (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Fork (nicolas-diener) wrote :

Great thing it's working for macias now!
The issue persists for me and others. Please reopen.

Revision history for this message
Guex (guex) wrote :

i find it very offending to change the state to invalid, based on single report from (comment #4) a user, while more than 100 users reported to be affected also. feels like treated by a billion dollar company.

considering that this affects an LTS release it does not help the affected users to know that it's fixed (for the majority) upstream in 4.5 and higher. installing a mainlinebuild kernel via dpkg is only a workaround - we need a fix as patch on v4.4.0, being published to the apt repositories.

Revision history for this message
Álvaro Guimarães (alvaroguimaraes) wrote :

I endorse everything Guex said.
The so called solution is absurd.

Em sáb, 4 de jun de 2016 13:11, Guex <email address hidden> escreveu:

> i find it very offending to change the state to invalid, based on single
> report from (comment #4) a user, while more than 100 users reported to
> be affected also. feels like treated by a billion dollar company.
>
> considering that this affects an LTS release it does not help the
> affected users to know that it's fixed (for the majority) upstream in
> 4.5 and higher. installing a mainlinebuild kernel via dpkg is only a
> workaround - we need a fix as patch on v4.4.0, being published to the
> apt repositories.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1566302
>
> Title:
> Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
> 4.4.0-16
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions
>

Revision history for this message
penalvch (penalvch) wrote :

Fork / Guex / Álvaro Guimarães, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: Invalid → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Ismail Gjevori (isgjevori) wrote :

@Christopher why this bug status first is changed to "Invalid" and then to "Won't fix"? This bug is confirmed from a lot of people and the original report says that the Ubuntu repository kernel has the bug (not the mainline/upstream).

Revision history for this message
penalvch (penalvch) wrote :

Ismail Gjevori, please more closely read this report, specifically https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/comments/4 .

Despite this, if one has an issue with their hardware, they would want to follow the instructions provided in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/comments/69 .

Revision history for this message
Michael Kofler (michael-kofler) wrote :

This bug report is a collection of important information for anyone interested in fixing the problem. It summarizes under which circumstances and on which hardware the bug occurs, and what Kernel versions might fix it. It is a cry of help from users who would like to use Ubuntu but can't do so because of hardware problems.

From a bureaucratic and formalistic point of view, it may be correct that the bug report is not correctly assigned here.

However, a lot of Ubuntu users spent time and energy to explain under which conditions this bug happens, and they had hope to find someone willing to fix it. By simply marking this bug as *won't fix*, https://bugs.launchpad.net/ubuntu/+bug/1 will remain forever. This is the kind of reaction you might expect from software companies which became too big and important to hear to their users.

Welcome to the Kafka version of Ubuntu, bye bye to Ubuntu for human beings.

Revision history for this message
Michael Stucki (mstucki) wrote :

I have a Lenovo Carbon X1 4th Gen which is most of the time connected to a OneLink+ dock. I encounter the same problem with kernel 4.4.0-22: Resume sometimes works, but sometimes not.

I have tested a few of the recent kernels available on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and here are my results:

Not booting with Ubuntu 16.04 on Lenovo Carbon X1 4th Gen:
- drm-intel-next/2016-06-02-yakkety/linux-image-4.6.0-997-generic_4.6.0-997.201606012202_amd64.deb
- drm-next/2016-06-03-yakkety/linux-image-4.7.0-996-generic_4.7.0-996.201606022202_amd64.deb

Boots but fails to resume on 1st try:
- drm-next/2016-05-09-wily/linux-image-4.6.0-996-generic_4.6.0-996.201605082201_amd64.deb

Resumes fine:
- drm-intel-nightly/2016-06-05-yakkety/linux-image-4.7.0-994-generic_4.7.0-994.201606042201_amd64.deb
- daily/2016-06-05-yakkety/linux-image-4.7.0-999-generic_4.7.0-999.201606042201_amd64.deb

In both cases I've made a few resumes and also plugged the dock on and off several times without any issues so far.

Currently I'm running the latest daily kernel and it seems to work good.

Revision history for this message
jose (o1485726) wrote :

"Welcome to the Kafka version of Ubuntu, bye bye to Ubuntu for human beings."
That's bugs.launchpad.net, part of Canonical, for you!

Revision history for this message
benjamin button (canavaroski90) wrote :

Still I can confirm with Linux 4.4.0-22-generic #40-Ubuntu SMP.

Using HP Pavilion dv6.

Also no updates or upgrades available.

Revision history for this message
Ismail Gjevori (isgjevori) wrote :

I've submitted a more general bug here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589139. If you want you can subscribe to this bug.

Revision history for this message
Álvaro Guimarães (alvaroguimaraes) wrote :

Done.

On Thu, Jun 9, 2016 at 3:46 PM Ismail Gjevori <email address hidden> wrote:

> I've submitted a more general bug here
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589139. If you
> want you can subscribe to this bug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1566302
>
> Title:
> Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
> 4.4.0-16
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions
>

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Done,

Thank you Ismail!

Revision history for this message
Om Prakash (iamprakashom) wrote :

Kernal 4.4.9 worked for lenovo Z51-70.

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

I just managed to get the 4.4.0-24-generic kernel to a proper suspend and resume for several times. As mentioned in the several bugs reported here, it seems to affect users with Intel/ATI hybrid graphics.

I disabled the ATI part by editing /etc/default/grub line to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=0"

and a "sudo update-grub".

After this my laptop (Samsung Ativ Book 730U3E) suspends with the official Kernel. Finally!

Revision history for this message
Christof Buchbender (ascurion) wrote :

I am affected by this bug as well. I have a Samsung Ativ book 8 with Ati/Intel hybrid graphics.
The workaround by peterriesde works for me (Thanks for that!). Thus turning off the ATI part allows to suspend with the official kernel.

In my opinion this should be fixed urgently. My laptop got very hot in it sleeve in my backpack several times, when I forgot to that suspend did not work and did not shut it down normally.

Revision history for this message
Francisco R. Santos (frsantos) wrote :

I to can confirm this workaround too (thanks!). I have a Dell Inspiron 15 7548 with ATI/Intel hybrid graphics.

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

That workaround really works, I also have tested, and can confirm for the Inspiron 15R 5537.

However this completely disables the Radeon video card and the vgaswitcheroo... "/sys/kernel/debug/vgaswitcheroo/switch: File or directory not found." So you can not use the dgpu for 3D applications and/or games.

I now have two options:
1. Use the Mainline Kernels and be able to use the radeon video card or,
2. Use the Ubuntu Kernels, disable it completely and use only the Intel video card.

For now, I will keep the first one.

Revision history for this message
Geraldo Luiz (geraldolmr) wrote :

Ok, the workaround worked for me, too. Sony Vaio with ATI/Intel hybrid gpu's.

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Testing longer I also noticed that using "radeon.modeset = 0" as an option to the kernel does not disable the radeon video card, but only disables access to it, which remains energized, consuming more battery, warming over the computer and activating the fan.

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Finally after upgrading today to Ubuntu Kernel 4.4.0-28.47, equivalent to Mainline Kernel 4.4.13, suspend/resume works out of the box, no special kernel parameters nor rc.local commands needed.

ATI discrete graphics starts DinOff but can be used when desired.

DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Gallium 0.4 on AMD HAINAN (DRM 2.43.0, LLVM 3.8.0)

glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile

Dell Inspiron 15R 5537.

Revision history for this message
Phil Hord (phil-phord) wrote :

Fixed in 4.4.0-28?

I had this same problem when I updated to 16.4 last month on 4.4.0-24. It worked fine when I booted from any of the 4.2 revisions I had previously (4.2.0-16, 4.2.0-36, 4.2.0-38). Today I was about to try the 4.4.9 kernels and noticed that Ubuntu had 4.4.0-28 available. I installed it and it seems to have fixed the problem. I've only tried pm-suspend once, but it worked right away which hasn't happened in several weeks for me.

Revision history for this message
henning (henning-sunrise) wrote :

Fixed with 4.4.0-28 for me as well

I had the same problem until yesterday. It got fixed by upgrading today from 4.4.0-21 to 4.4.0-28 (on lenovo x1 carbon 4th gen)

Revision history for this message
ianholing (ianholing) wrote :

Same here.. finally fixed, but now my hibernate option into power setup when battery is down is disabled :( Is it some workaround for past updates?

no longer affects: linux
Revision history for this message
Steve Rovsky (steverovsky) wrote :

Not fixed in 4.4.0-31 : - (
Acer V5-573G

Revision history for this message
Kenneth Bingham (qrkourier) wrote :

Still have this problem with kernel 4.4.0-28.47 on a Dell Precision Mobile Workstation 3510 - 15.6" - Core i7 6820HQ - 16 GB RAM, but it's fixed on this machine by 4.4.0-31.50.

Revision history for this message
deb2014 (edouard-debry) wrote :

Hello,

On a T440s (intel graphic + nvidia) with ubuntu 16.04, I experience random freezes when waking up from hibernation.

Suspend to ram works fine.

But when waking up from suspend to disk, it happens that either the screen go black and the system becomes totally unresponsive, or the system actually wakes up but freezes soon after, in this latter case, I can see in the log a "general protection fault" followed by what seems to be a kernel crash (can post it if you want).

But sometimes, it runs just well, it is quite random. I suspect some kind of race conditions, but it always happens if I hibernate/wakes up more than 3/4 times one after the other.

From the logs, I cannot infer what is going on. It also happened with ubuntu 14.04 but much more rarely. When installing ubuntu 16.04, I had to put the wifi module in the SUSPEND_MODULE list for the hibernation to work (crashes every time otherwise). Putting more modules (bluetooth, bbswitch) did not solve the issue.

Could you help me in solving this bug ? What should I do ?

Thanks in advance for your attention.

Regards

T440s (intel graphics + nvidia) + ubuntu 16.04 (latest kernel) + latest bios (2.39)

Revision history for this message
João Carlos Martins Teixeira (jcmt87) wrote :

Exactly the same here (as described by deb2014) with an ASUS UX31A

Revision history for this message
deb2014 (edouard-debry) wrote :

Upgrading to newer kernel did not solve the issue, I experience similar crashes with linux 4.6 from kernel-ppa.

Revision history for this message
deb2014 (edouard-debry) wrote :

Here is in attachment the kernel logs with general protection fault on resumes.

Revision history for this message
deb2014 (edouard-debry) wrote :

I installed ubuntu 16.04 on an entirely encrypted disk, including swap.

Could these wakeup crashes be due to this fact ? I will test hibernation/wakeup from a simple swap partiton.

Meanwhile, if you have any hints, whether what to debug or test, it would be very much appreciated.

Regards

Revision history for this message
Cristiano Gavião (cvgaviao) wrote :

I'm using kernel 4.4.0-31 and have the same problem.

Revision history for this message
deb2014 (edouard-debry) wrote :

Hi again,

Still same problem, wakeup from hibernation freezes at some time, with latest kernel (4.4.0-31),
that is to say the system becomes totally unresponsive, the screen may go black or not.

It seems that the system is not always able to write something in logs when this occurs :
in /var/log/kern.log there is sometimes nothing, sometimes a general protection fault, sometimes one line with only @@@@@@@@@@@@@ symbols (??).

In the meantime, suspend to ram is absolutely stable.

Nevertheless, I noticed that if I switch ON the nvidia card (*) just before hibernating, freezes seem to occur less often.

Again, if anyone has some hints about how to debug.

Regards

(*) The T440s has got two graphic cards, integrated intel and nvidia G730M, the nvidia card is switched OFF by default at boot with bbswitch module, I can switch it ON with "echo ON > /proc/acpi/bbswitch"

Revision history for this message
Dragor (gregory-brancq) wrote :

Hi,

I have the Lenovo T440p with integrated intel and nvidia, and I encounter the same symptoms than deb2014.
The log is also with @@@@ symbols.
It's ramdomly crashed with a black screen or works after hibernating no more than 2-3 times.
Moreover, it crashs every time I plug in to the dockstation.
I tried unsuccessfully several kernels.

@deb2014, you says that it's stable with suspend to ram. Could you tell me the procedure to test?

Regards,
Greg

Revision history for this message
Dragor (gregory-brancq) wrote :

I just tested the suspend to ram (sorry I misunderstood this option in my own language), it works.
The tip is that if the laptop is on the dockstation and I suspend it to ram, after wakeup I have to unplug and replug it, to bypass the black screen.

Revision history for this message
BretAB (bret-g) wrote :

Hi,

I also had the "hang after suspend problem" immediately after I upgraded my Dell Inspiron 1501 from Ubuntu 14.04, to 15.1, then to 16.01 (all 32bit versions). I found an easy workaround (for now) that eliminates my "blank screen" hang after suspend: Just got into "System | Brightness and Lock", and set "Turn screen off when inactive for" to "Never".

Btw, I see above that users are uploading a txt file with their system details. I would gladly do that if someone wants to show me how or point me to a how-to url.

Regards,
BretAB
WinITPro & Certified Ubuntu Newb

Revision history for this message
J A Brown (inisfad) wrote :

Same here. Dell Inspiron 1501, I get the hang after suspend problem after my upgrade today to 16.04. Kernel 4.4.0.31. Thanks to BretAB above-hopefully at least changing my settings to Never, under turn screen off when inactive, will 'solve' this issue until it's actually solved.

Revision history for this message
deb2014 (edouard-debry) wrote :

Hi,

For T440s or T440p owners, I tried the latest stabke kernel (4.7) directly from kernel.org.

I still get random freezes on resuming from hibernate (suspend to ram is not impacted).

Most of the time, the only trace remaining in logs is one line full of "@^@^@^@^@^@^@".

Considering thus that there is no fix upstream, I went downstream and installed the longterm kernel 3.16.36 (still from kernel.org). I think it is the kernel version currently used by ubuntu 14.04

It seems to solve this bug. I say "it seems" because as the freezes occurs randomly, I could just have luck. Nevertheless, I was able to hibernate/resume 4 times, one after the other, without any freezes or kernel faults, which did never happen before.

I will confirm later if freezes do not happen anymore. You can try also, possibly with a higher kernel version, so that we could identify which version change is responsible for this bug.

Regards.

Revision history for this message
deb2014 (edouard-debry) wrote :

Hi again,

I finally found out the cause of these random hibernate/resume freezes.

My swap partition is a logical volume which itself lies on a luks encrypted partition, togother with the root and /home logicla volumes.

I switched to a normal swap partition, based on a real primary partition. I was then able to hibernate/resume 10 times like this :

for i in $(seq 1 10)
do
    sleep 3
    rtcwake -m disk -s 30
done

without the least kernel fault or any freezes, whatever the kernel version I use.

I am surprised that a swap partition based on an encrypted partition causes such problems, on several sites advocating full encryption (swap included) it seemed stable enough.

Hopes this helps.

Revision history for this message
Adam Thiede (adamthiede) wrote :

I'm having the same issue on an Asus X550LA - Haswell i5 with Intel HD graphics.
I've tried using both 4.4 and 4.6, but this issue still persists. I've been able to get hibernate working via default instructions (pm-hibernate worked by default) but the computer just reboots after resuming from sleep. There are a few settings in the BIOS to look at - power consumption while asleep and resume when opening lid will be worth tinkering with, but I've tried many fixes and none seem to work.

Revision history for this message
Igor (4eppelin) wrote :

I think I have the same issue. If so, I know some sort of workaround - to switch to an another console with Ctrl+Alt+F6 and go back with Ctrl+Alt+F7. It frees a keyboard and lets to enter a password. But after that I have a little mess with windows - they move to other desktops and shifted a little.

Revision history for this message
Mark Alan (malan) wrote :

I am also having the "blank screen" hang after suspend (screen shows a "no HDMI signal").
My systems is a Xubuntu 16.04.1, Kernel 4.4.0-31-generic, motherboard MSI B85M-E45 (Intel chipset B85 Express, ACPI: Video Device [GFX0]).

Revision history for this message
mint-one (d-zschokke) wrote :

Same here on Dell Inspiron 3351 using ubuntu 16.04.1 with the latest kernel (currently 4.4.0-34). System won't wake up after suspend and the screen remains dark. Restart and shutdown won't finish and hang on the shutdown screen. I have to switch it off manually.

The installation of the latest bios (A05) didn't improve the situation. I also tried various mainline kernels (4.4.8, 4.8rc, 3.19). The issue still persists. Ok, the laptop works, but this bug is quite annoying.

Revision history for this message
mint-one (d-zschokke) wrote :

Ok, I was able to fix this on my Dell Inspiron 3551. The solution was a superclean fresh installation of ubuntu16.04 with the latest bios installed and secure boot off. Everything (suspend/wake/restart) works now with the latest ubuntu default kernel (XX-34). But don't aks me why or what went wrong before.

cu, dom

Revision history for this message
Trueman (d-artyukh) wrote :

I've the same issue with wakeup after suspen to ram on laptop fujitsu A555 with Intel+ATI graphics. It started after updating to kernel 4.4.0.11 and lasts even with kernel 4.4.0.34. Usually, first wakeup works fine, but 2nd freezes the laptop - screen is not black but shows the Desktop and opened applications, keyboard does not responce (switching to console is not possible, reisub does not work also), system fun works and temperature grows. I have to press and hold power button until laptop turns off.
Workaround with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=0" does not work for me.
Swap is located on separate primary not encrypted partition.

The latest kernel which works OK with resume from suspend is 4.4.0.10. So, I'm using it. But still wait for a fix.

Revision history for this message
Motosauro (motosauro) wrote :

Same issue for me. I moved to 16.04 from 14.04 only recently and I always had this weird suspension issue on 16.04
On 14.04 everything worked just fine
I'm currently on 4.4.0-34-generic

I haven't tested 4.5 or 4.6 kernels since the station suffering from the issue is my work one and I need it to be reliable. If I wanted to mess with kernels I would have stayed on Gentoo :)

Revision history for this message
Ilya G. Ryabinkin (ileyka) wrote :

Sorry for being grumpy, but something has be done with kernel quality assurance. 4.4 kernel apparently has multiple issues---in my case I have troubles on both 16.04 & 14.04 Ubuntus. They are:

1. blank virtual consoles after some time on 14.04.5@Asus Zenbook UX301 CA
2. Random Xorg lockups on 16.04.1@Lenovo thinkpad x220. Interestingly, the laptop is not completely frozen---after pressing Ctrl-Alt-F1 I'm able to get to tty1, but after 30-40s. But going back to X results in still unresponsive graphics, so the only thing I can do is to issue a "shutdown -r now" command from the console... Kernel is complaining in dmesg about 'lost vblank'.

All these things, I believe, are due to multiple bugs in 4.4 kernel, presumably in intel video driver and/or a DRM subsystem---seems like it's badly broken in 4.4.

Ubuntu kernel team should really consider to drop 4.4 support and move on to the next major kernel release.

Revision history for this message
Martin Dybdal (dybber) wrote :

Just upgraded to version 4.7.2, but still not solved for me. I'm using Ubuntu GNOME Remix 16.04 LTS on a Lenovo Yoga 2 Pro. Suspend worked perfectly on Ubuntu GNOME Remix 14.04 LTS.

Revision history for this message
Mingyang Li (li2150) wrote :

Using ASUS E200HA, same issue happened on kernel 4.4.0-35, 4.4.14-xenial, and 4.7.2, none of them have fixed the issue. For a quick reference, this notebook's CPU is Intel Atom x5-Z8300, and it contains Graphics Intel HD Graphics (Cherryview).

Revision history for this message
ash (sersorrel) wrote :

This also affected me, on Lenovo G580, kernel 4.4.0-34-generic. However, I think I fixed it by appending "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then running sudo update-grub as per http://askubuntu.com/a/722653/478436.

@ileyka/#112 - I was experiencing similar problems with blank TTYs; you could try the solution I mentioned above.

Revision history for this message
Alessandro Zucca (alessandro-zucca01) wrote :

I solved it on my dell 7537 by following this guide
https://www.youtube.com/watch?v=l8xa-PkDhhk

so I basically just added acpi_osi='!Windows 2013' acpi_osi='!Windows 2012' to my grub configuration.

I skipped the acpi_backlight=vendor part because it breaks my backlight shortcut.

Revision history for this message
Trueman (d-artyukh) wrote :

It still reproduces in kernel 4.4.0-36

Revision history for this message
Wolf (drechsel) wrote :

the same here with 4.4.0-36-generic, nvidia video.
"nomodset" does not solve it

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Same problem here. Lenovo G510 with I5 and integrated graphics. Just installed elementary OS Loki Beta. Currently running 4.4.0-36-generic. Randomly freezes on resuming from suspend. Screen does not blank out, windows are visible but everything is unresponsive including mouse/touchpad. Happens about 1 in 4 resumes.

Thinking this might be a video driver issue I just added the oibaf and x-org/edgers ppas to update my graphics drivers to the latest by doing:

sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get dist-upgrade

I'm not certain this will have any effect at all or even if it is a good or bad idea to add both. One is likely enough. Did it this morning, and so far no more freezing, but that might be luck. I will report later in the week.

Jay

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Followup to my last comment. Checked which packages were installed, they were all from oibaf ppa so removee xorg-edgers ppa for the time being. So far no further freezes, but will report back later.

Jay

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

My system hung this morning, so no improvement with updated drivers. Trying the 4.4.8 mainline kernel next as some have suggested.

Jay

Revision history for this message
rewound (rewound) wrote :

Bug 1620733 may be of interest, it uses kernel 4.8.0-040800rc5-generic

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

So far have tried kernels:
4.8-rc5 - breaks Wi-Fi
4.6.7 - breaks Wi-Fi
4.4.9 - still random freezes on resume from suspend
4.2.8 ckt13 - still random freezes on resume from suspend

The only other thing I can think of is that I installed TLP shortly after installing this version of elementary. Not sure if that is causing a problem. Will remove and keep trying.

Revision history for this message
Wolf (drechsel) wrote :

Does anybody know, when kernel 4.6 will be released within an "official" system update? -

Tried to install 4.8, or older versions still available on my computer, but each of them made the X server (nvidia graphics) unusable.

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Still freezing after removing tlp. Added "acpi_osi='!Windows 2013' acpi_osi='!Windows 2012'" to grub configuration.

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Still freezes with the grub modification. Tried kernel 4.5.2, same problem. For me it seems to happen most frequently with changing power sources while suspended (ie. plugging in or unplugging while suspended) At least I can avoid this. Not sure what to do at this point.

Revision history for this message
Tim (0rca-l3lacksail) wrote :

The issue for me was not due to resuming from hibernate or suspend. The issue persisted after disabling both.

Monitor would go black in ten minutes but power the light was not blinking (steady) yet upon resume I get the same graphical freeze.

Purging xautolock->reboot solved the issue for me. Screen still goes black in 10 minutes but I've resumed successfully several times in the last 24 hours with no repeat occurrence.

I know this isn't a fix but thought it would be worth posting the possibility of an alt root cause.

Revision history for this message
Mark Alan (malan) wrote :

@Tim: I have purged xautolock a long time ago (due to other reason) but I am still having the freezes ( from which I recover by a keyboard key combination that I mapped to: xrandr --auto )

Revision history for this message
Tim (0rca-l3lacksail) wrote :

Did you nuke xscreensaver and or light lock. If you disabled all else (for testing) the last option should apply prior to resuming.

Blinking Green power = Suspend
No light on power = Hibernate
Solid green power = xautolock, screensaver, or equivalent

Prior - I could make hibernate and suspend work consistently (inside 10 minutes). If the last option is causing the issue the screen will go black at exactly 10 minutes. The only way I could resume properly every time was to remove them.

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Tried reinstalling elementary OS Loki stable. No change. Caps lock doesn't change the light on my keyboard so I'm thinking it is definitely a kernel issue.

Revision history for this message
Jason Gambrel (jaygambrel) wrote :

Turned out to be a hardware issue. My bluetooth would give errors on startup and only work intermittently. Edited /etc/modprobe.d/blacklist.conf and blacklisted bluetooth and btusb. Also disabled it via: sudo systemctl mask dbus-org.bluez.service. Now works suspending works like a charm.

Revision history for this message
Glen (glentupling-hotmail) wrote :

This is a serious issue for me, I don't want to restart my computer every 10 minutes!

Revision history for this message
Glen (glentupling-hotmail) wrote :

Upgraded to 16.04 this morning, issue did not exist before today. kernel 4.4.0-38-generic, pc is no-name Intel core 2 duo cpu e7300 s.66GHz x 2, graphics Gallium 0.4 on ATI RV370, no bluetooth, no wireless. System will not recover from sleep or hibernate.

Revision history for this message
tombiggar (tombiggar) wrote :

I did an install of 16.04 kernel 4.4.0-38-generic and also had the freeze after waking from sleep. The screen was visible but non responsive. I had a lot of hard drive activity on boot when I did a power down restart and a brief message about cleaning up orphaned inodes. After reading the posts above, I tried replacing the X-Org video driver that was installed by default with the Nvidia driver listed under System Settings and the problem seems to be gone. It was pretty consistent before I replaced the driver and has not happened in the last 2 days since I replaced the driver. Also, the orphaned inode message has not appeared and the hard drive behaves normally on boot. I'll post if it occurs again. Hope this helps someone.

Revision history for this message
Andrzej Mazur (coopman) wrote :

the same problem for me:

When I start fresh system, the suspend to RAM and resume works properly.
But after certain amount of time when OS works, suspending and resuming ends with no response (blank screen).

Ubuntu 16.04 64bit, Toshiba A200-1N8, 4.4.0-38-generic, Intel(R) Core(TM)2 Duo CPU T7250

Revision history for this message
Milo (mloa727) wrote :

I have this issue with 4.4.0-43. I did notice that there were no problems when I was running 4.4.0-36.

Revision history for this message
jaka (jaka-barkarby) wrote : SV: [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
Download full text (3.2 KiB)

Resolved for me with kernel 4.8.2
/jaaka

Skickat från min Samsung-enhet

-------- Originalmeddelande --------
Från: Mark Loatman <email address hidden>
Datum: 2016-10-20 00:45 (GMT+01:00)
Till: <email address hidden>
Rubrik: [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

I have this issue with 4.4.0-43. I did notice that there were no
problems when I was running 4.4.0-36.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1566302

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: macias 1770 F.... pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr 5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic N/A
   linux-firmware 1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.ne...

Read more...

Revision history for this message
Wolf (drechsel) wrote :

The problem persisted with Kernel 4.8 - but I found it was a hardware issue:
My power supply was faulty - installing a new one resolved the problem.

In addition I found that the BIOS battery was down to 1,3V; inserting a new one re-enabled the "resume on power off" feature. Multi-factor problems really are great joy.

Revision history for this message
Utz (utz-recke) wrote :

I experience the same problem on Ubuntu 16.10. Kernel 4.8.0-26-generic and Intel graphics

Revision history for this message
Hamzeh Ahmad (hamzeh-ahmad) wrote :

I had the same problem and I solved this way, a work around:

am not sure but I think in that case swap memory should be equal to your ram size or more, I resized to to 8gb which is equal to my ram.

open terminal and do the following:

sudo gedit /etc/default/grub

replace the line

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash'"

With

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor acpi_osi='!Windows 2013' acpi_osi='!Windows 2012'"

save and close then also in terminal

uncomment the line #HandleLidSwitch and make sure value equal suspend (or hibernate,depend on wha you want) to look like this

HandleLidSwitch=suspend

you have to restart fully twice , then try.

in case it didnt work out try uninstall acpi-support y typing
sudo apt-get remove acpi

I found the first step of the solution from this guy
https://www.youtube.com/watch?v=l8xa-PkDhhk

now both hibernate and suspend works !!

Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :
Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

OOps! Sorry! Now, I see that the workaround is described at #140 (just before my post).

Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

@hamzeh-ahmad, I think that

uncomment the line #HandleLidSwitch and make sure value equal suspend

is not necessary.

I'm guessing that commented parameters at /etc/systemd/logind.conf are the defaults.

So, the line:

#HandleLidSwitch=suspend

is equivalent to:

HandleLidSwitch=suspend

In fact, I didn't need to modify it.

Revision history for this message
Hamzeh Ahmad (hamzeh-ahmad) wrote :

@jpujades you are right maybe, it was equal hibernate for me not suspend.

I cant remember if it was like that or I changed it while I was trying other solutions.

let say it's a make sure step.

Revision history for this message
Hamzeh Ahmad (hamzeh-ahmad) wrote :

And Yes #HandleLidSwitch=suspend is in the file

/etc/systemd/logind.conf

Revision history for this message
Arne (old-man999-r) wrote :

We experienced this on a HP-Probook 6450B with kernel 4.4 running the provided tests:

echo platform > /sys/power/disk

[ 533.556002] perf interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 1830.133850] perf interrupt took too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[ 2537.897989] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[ 2537.898048] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[ 3313.942173] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[ 3313.942273] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[ 3313.977472] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun

echo disk > /sys/power/state

[18786.704686] sd 0:0:0:0: [sda] Starting disk
[18786.708197] ERROR @wl_wowl_ind_wake_reason : Unable to get wake reason, err = -95

Revision history for this message
Hamzeh Ahmad (hamzeh-ahmad) wrote :

@arne the solution i proposed has been applied on kernal version 4.8
i have updated to from 4.5 to 4.8 and no problems occured , then i tried the steps above

Revision history for this message
acar burak (acarbura) wrote :

@Hamzeh, does your solution only work with the 4.8 kernel?

Revision history for this message
Hamzeh Ahmad (hamzeh-ahmad) wrote :

@acarbura yes it does

Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

Acer TM (TravelMate) B117M N3150 processor using SSD (manufactured on Jully-2016)

Lubuntu 14.04 LTS + LTSEnablementStack
(https://wiki.ubuntu.com/Kernel/LTSEnablementStack)

We have about 110 units of this model. Some of them are freezing using them and after suspend.

We migrated some machines to latest stable kernel (4.8.10). Computers are more stable.
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/comments/142)

but... they continue to freeze after suspend.

Modifing /etc/default/grub as suggested at comment #140 seems to solve the freezing after suspend.

@old-man999-r, thanks for your test at #146. I didn't know them.
(https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt)

Revision history for this message
Janne Heikkinen (janne-m-heikkinen) wrote :

I tried the workaround on Asus E502SA but lost touchpad with it applied.

Revision history for this message
Andrew (coder27) wrote :

I encoutered the same issue with my Lenovo IdeaPad S205.

I've tried several kernels, including latest mainline 4.10 rc2, but no lack - just black screen on wake up.

But I have noticed that the laptop resumes sucessfully from sleep when the power plug has been removed just before pressing a key to wake it up (i.e. It resumes succesfully when powered from battery only).

Hope it helps to fix that annoyance.

If someone needs my log files or hardware reports, please let me know.

Revision history for this message
Andrew (coder27) wrote :

Hello.

I've tried Linix Mint 18, Ubuntu Mate 16.04 - the problem appeared right after booting live image from USB stick. Ubuntu Mate 16.10 does not have the issue. So I've installed 16.10.

The kernel from 16.10 does not fix Mint 18 and Ubuntu 16.04, so I think it is not a kernel code regression.

Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

Please, copy/paste the output of the command:

uname -a

Like this others (than Mint flavor) can know which kernel version you're using.

Thanks in advance!

Revision history for this message
Oleg (kwazaro) wrote :

I tried different kernels, settings, even instructions from #140 post of this thread... Nothing could help. But some distros worked fine on this laptop - for example Manjaro and CentOS (waking up from suspend without issues). On my Lenovo s205 the only installing "tlp" and "tlp-rdw" (Linux Advanced Power Management) solved problem with freezing after suspend. The Kernel I'm using is 4.4.0-62-generic (Linux Mint 18.1). More about "tpl" here: http://linrunner.de/en/tlp/docs/tlp-linux-advanced-power-management.html

Revision history for this message
Trueman (d-artyukh) wrote :

Nothing helped: not grub editing from comment #140 neiter instalalling and starting "tlp"...
Fujitsu A555 laptop freezes after 2nd wake up from suspend.
Ubuntu 16.04 with any kernel in range 4.4.0-11 - 4.4.0-59.
I've to use 4.4.0-10 kernel where the issue is not replicated.
Very frustrating...

Revision history for this message
Manuel (deco3051) wrote :

Solved by disabling the xCHI usb 3.0 on the bios. adding parameters to Grub didn´t.

Now Freezes does not happen after suspend, hibernate, close the lip or turning off.

It takes a decent amount of time to turn off and the screen flash in different shades of black when booting though. would be nice to see this solved.

Hope it helps and that this is the proper place to share this.

I had the same problem here on Acer Aspire E15.

Revision history for this message
Draven Grey (draven.grey) wrote :

Running into the same thing on an old Macbook with Ubuntu. So far, nothing's worked to fix it. Sadly, there is no USB3 to turn off in order to try the last "fix" posted.

Revision history for this message
Jeff Cragg (jeffcragg) wrote :

Getting this on 16.04.1 on live try from a usb key, also on 16.10. Black screen on resume. Motherboard is Asus extreme 3 gen 3. Get it when using intel on-board graphics or nvidia card. Have a soundcard if that makes any difference. This bug was introduced at some point before these versions. So suspend/hibernate bug is not -just- suspend/hibernate. Without being able to suspend, it requires repeatedly power cycling the machine. If you have the ram with suspend that going to be better the longer the use the machine, not if you have to power cycle. Also loading up all the apps again, pita. I am going to try Debian and see if the Jessie release fixes this. 16.04+ is plain buggy. I don't think you should have released as a LTS. Check it out this is a common issue.

https://www.google.co.jp/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=ubuntu+suspend+resume+bugs+16.04&*

Andrew (drewandrew)
no longer affects: linux
Revision history for this message
Maxim (maximca) wrote :

Hi, I have same problem and probably my bug report will help to find the problem.

Currently I'm using Lenovo Thinkpad Carbon 4th gen and ubuntu 16.04.2:
Linux carbon 4.8.0-54-generic #57~16.04.1-Ubuntu SMP Wed May 24 16:22:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I have problems with suspend only after I plug external screen to my computer. It happens no matter if the screens are connected via the dock station or directly to DP port(s). Also it doesn't matter if suspend was triggered by closing the laptop lid or by the timer.

There are 2 ways I can avoid freezing after suspend:
1) Call "xrandr --auto" after I unplug external screens
2) Execute "sudo pm-suspend" manually

If I do one of the steps above suspend works perfectly and the laptop wakes up with no problems.

One thing to notice: while I was debugging this issue I put a script to the /etc/pm/sleep.d/ which simply logging the fact of its execution. When I'm using pm-suspend this script is being executed but if I simply close the lid then this script is not being executed. I believe when I'm closing the lid some other suspend mechanism is triggered not the pm-suspend.

I can confirm that this bug appeared in 16.04 LTS. I tried all kernels and all workarounds suggested in this post and none of them worked. Also I had same issue on previous Lenovo Carbon x1 rev (3).

Revision history for this message
Anthony Naddeo (anthony-naddeo) wrote :

For anyone dealing with this issue on a Dell XPS 13 with a touchscreen on Ubuntu 16.04, it seems to re-enabling the touch screen in the laptop bios resolved it for me. I usually keep the touch screen disabled but there must have been a regression in one of the kernel updates that I got that made it suddenly an issue.

I'll update this comment if it turns out I was just lucky for the last few days and that isn't really the solution.

Revision history for this message
ArTaX (marco-zannoni) wrote :

Same problem. However, I noticed that the issue disappears when you modify the Dell firmware settings, e.g. updating the firmware, changing settings, ...
I reproduced this solution a couple of times. Then, the problem re-appears periodically (perhaps after a kernel upgrade?).

Moreover, I suspect that this can be related to the "fastboot" feature in the firmware. In my case it is activated. Maybe, after changing the firmware, the system performs a full boot procedure, correcting any system issue related to suspension. In the normal boot, however, these checks are not performed, so the issue appears again and again.

Can you confirm if this option is activated also for you?
Maybe you can try to disable it and see if the suspension issue disappears.

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

Other bug subscribers

Remote bug watches

  • auto-steverovsky Edit

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