Suspension does not work, freezes the pc

Bug #1566828 reported by hesediel84
104
This bug affects 22 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I have this notebook
HP 15 ac 191 nl

Intel® Core™ i5-5200U with integrated Intel HD 5500
RAM 8 gb
DEdicated GPU AMD Radeon R5 M330

I am running kubuntu 16.04 beta2.

When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot.
It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec.

The problem is present every time i try to suspend the pc.
---
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ale 1315 F.... pulseaudio
 /dev/snd/pcmC1D0c: ale 1315 F...m pulseaudio
 /dev/snd/pcmC1D0p: ale 1315 F...m pulseaudio
 /dev/snd/controlC1: ale 1315 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
InstallationDate: Installed on 2016-03-31 (5 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/18/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.1F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80C2
dmi.board.vendor: HP
dmi.board.version: 96.45
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
---
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ale 1315 F.... pulseaudio
 /dev/snd/pcmC1D0c: ale 1315 F...m pulseaudio
 /dev/snd/pcmC1D0p: ale 1315 F...m pulseaudio
 /dev/snd/controlC1: ale 1315 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388
InstallationDate: Installed on 2016-03-31 (5 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-16-generic N/A
 linux-backports-modules-4.4.0-16-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/18/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.1F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80C2
dmi.board.vendor: HP
dmi.board.version: 96.45
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

hesediel84 (hesediel84)
description: updated
description: updated
Martin Pitt (pitti)
affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1566828

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
hesediel84 (hesediel84) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
hesediel84 (hesediel84) wrote : CRDA.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : CurrentDmesg.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : IwConfig.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : JournalErrors.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : Lspci.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcInterrupts.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcModules.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : UdevDb.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
hesediel84 (hesediel84) wrote : AlsaInfo.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : CRDA.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : CurrentDmesg.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : IwConfig.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : JournalErrors.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : Lspci.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcInterrupts.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : ProcModules.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : UdevDb.txt

apport information

Revision history for this message
hesediel84 (hesediel84) wrote : WifiSyslog.txt

apport information

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

I tried the ubuntu 15.10 live and in this version the suspend works.
In the 16.04 beta 2 the suspend does not work, same stuff of the post

Revision history for this message
Bartosz Boryn (bartosz-boryn) wrote :

Have the same problem on Dell Insprion 7520. Similarly, suspend worked in 15.10 but stopped in 16.04.

Revision history for this message
Teo (mzoia26) wrote :

Have the same problem on Dell Insprion 7548. Similarly, suspend worked in 15.10 but stopped in 16.04.

Revision history for this message
Ryan (yyan) wrote :

Same problem, also on a Dell 7520. Suspend worked every ubuntu release up through 15.10, now the fan spins and never fully sleeps and can't be woken up.

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bartosz Boryn (bartosz-boryn) wrote :

kernel-fixed-upstream

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

To complete the information so i tried the others kernel:

Kernel 4.5 the problem still present.

Kernel 4.5.1 the problem seems to be resolved from this kernel.

Revision history for this message
hesediel84 (hesediel84) wrote :

@update

I reinstalled the 16.04 from zero and i downloaded
The image, the header and headers_all
in installed them with the command:
sudo dpkg -i linux*.deb

and now...the new kernels 4.5.1 and also 4.6rc4 does NOT solve the problem. Still present.

I dont know..

hesediel84 (hesediel84)
tags: added: kernel-bug-exists-upstream
removed: kernel-fixed-upstream xenial
Revision history for this message
hesediel84 (hesediel84) wrote :

So i made all day of tests with the 4.6 rc4 kernel:

- difference to 4.4 kernel, suspending does not freeze totally the pc, some times the screen stays black sometimes it show the wallpaper. It's blocked but pressing the power button couple of times the pc returns withiut forcing a shutdown.

-Confirm that kernel 4.4 freezes the pc

-The suspend system works some times, rarely, but some time works. I wasnt unable to recognize a causing factor like battery or not, wifi on or off...dont know.

Revision history for this message
Ryan (yyan) wrote :

Noticing everyone in this bug report has Intel + Radeon graphics, I tried disabling the Radeon. Simply running 'sudo rmmod radeon' after the laptop boots up with the stock 4.4 kernel allows it to properly sleep. Removing the kernel module causes kernel oops, but otherwise everything seems fine after unloading it. I've attached a dmesg showing the kernel module removal with the oops, and the successful sleep/wake that follows it. I've tried it several times and sleep/wake is working every time after removing radeon, and fails every time while radeon is loaded.

Revision history for this message
hesediel84 (hesediel84) wrote :

i was thinking problems with the radeon graphics, i would like to make test @Ryan, can you tell me how to do? Because if i run "sudo rmmod radeon" in the terminal i got the message
"rmmod: ERROR: Module radeon is in use"

Revision history for this message
Ryan (yyan) wrote :

hesediel84, module radeon is in use means that's the graphics card you're using in X. See if you can disable it in your BIOS (I can't on my Dell laptop). If not, blacklist the radeon module so it doesn't load on boot. Add "blacklist radeon" to the bottom of /etc/modprobe.d/blacklist.conf

Revision history for this message
hesediel84 (hesediel84) wrote :

i addedo the blacklist tadeon to the file you told in upper post.
Unfortunately it didn't work for me :(

Revision history for this message
Loris Zinsou (nepenthes) wrote :

@hesediel84 : You need to run `sudo update-initramfs -u` for the blacklist to actually update and take effect.

Revision history for this message
yuce (tklx) wrote :

Blacklisting the radeon module resolves this issue on Dell Inspiron 15R (which has Intel + Radeon graphics).

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Same here on Vostro 3350, blacklisting radeon fixes the issue.

Revision history for this message
hesediel84 (hesediel84) wrote :

Loris I gave the sudo update-initramfs -u
I am using the new 4.4 kernel. In effect it seems working now.
Just sometimes the PC resumes but the Wi-Fi doesn't

Revision history for this message
Robert (rgiyf) wrote :

Ubuntu 16.04 64-bit final on HP Envy 6 with Intel Core i5-3337U and Intel HD4000 + AMD Radeon HD8750m. System not suspending just screen goes black and then you can't do anything.

Revision history for this message
Piotr Kaczmarek (piokac) wrote :

Blacklisting the radeon module resolves this issue on Dell Latitude 3540, i5 4210U, Radeon HD 8850M.
Wifi (AR9565) does not resume properly but it can be fixed by calling: 'sudo service network-manager restart'

Revision history for this message
Vojtech Kusy (wojtha) wrote :

I can confirm that blacklisting radeon solves the issue at Lenovo Thinkpad S440 touch!

Revision history for this message
Teo (mzoia26) wrote :

Ubuntu 16.04 64-bit on Dell Inspirion 7548 with Intel i7 and and Intel HD5500 + AMD Radeon R7. System not suspending just screen goes black and then you can't do anything. In previous version there wasn't this problem. One question. If i disable the "radeon module", this mean that I will use only the Intel card? Thanks a lot

Revision history for this message
Mike Slinn (mslinn) wrote :

 Before I upgraded from 15.10 yesterday, suspend worked perfectly on my HP Pavilion dv6t-6c00 CTO Quad laptop (Product number A1U57AV) with AMD Radeon video.
After upgrading to the released version of XUbuntu 16.04 yesterday, my laptop now has these exact symptoms.

Revision history for this message
Mike Slinn (mslinn) wrote :

... continuing my post: blacklisting the Radeon made no difference

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Might be a better idea, to use an old kernel instead of blacklisting. At least for me, blacklisting the radeon driver leads to high temperatures and battery drain, beause the ATI card runs in high performance mode.
I'm currently doing a bisect to nail down the commit which introduced this bug - this will take pretty long however.

4.2. works perfectly fine.

Revision history for this message
Mike Slinn (mslinn) wrote :

Rolling back to 4.2 worked fine for me. Here are two quick commands to make that easy:
http://unix.stackexchange.com/questions/198003/set-default-kernel-in-grub/278575#278575

Revision history for this message
hesediel84 (hesediel84) wrote :

mike did you give the command sudo update-initramfs -u
because the blacklist to me worked only after i gave that

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Finished my bisect:

7bb4014e065abf88c1698bc5fde7a91caf907265 is the first bad commit
commit 7bb4014e065abf88c1698bc5fde7a91caf907265
Author: Rob Clark <email address hidden>
Date: Mon Jan 25 18:06:48 2016 -0500

    drm/radeon: only init fbdev if we have connectors

    BugLink: http://bugs.launchpad.net/bugs/1546572

    This fixes an issue that was noticed on an optimus/prime laptop with
    a kernel that was old enough to not support the integrated intel gfx
    (which was driving all the outputs), but did have support for the
    discrete radeon gpu. The end result was not falling back to VESA and
    leaving the user with a black screen.

    (Plus it is kind of silly to create an framebuffer device if there
    are no outputs hooked up to the gpu.)

    Signed-off-by: Rob Clark <email address hidden>
    Signed-off-by: Alex Deucher <email address hidden>
    (cherry picked from commit f95429eccc570dc45d589c327bfcfddcdc3e8228)
    Signed-off-by: Alberto Milone <email address hidden>

    Signed-off-by: Tim Gardner <email address hidden>

:040000 040000 e8135e481d51ce133b7c3e5ee97f0916fb731bb5 230277112d1123be03dbec1be4f597057e91e546 M drivers

Which matches this commit in the upstream git: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f95429eccc570dc45d589c327bfcfddcdc3e8228

Turns out I have not been the first one, doing this: https://bugzilla.kernel.org/show_bug.cgi?id=112781

...
Which has been fixed here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e5f243bd2edd95c6cc1d90c1878f821068e83fba.

I picket the patch and check if the problem is gone.

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Verified: Cerry-picking the fix (upstream commit e5f243bd2edd95c6cc1d90c1878f821068e83fba) onto the Xenial Kernel git master fixes the issue for me.

Revision history for this message
Thomas Mortagne (thomas-mortagne) wrote :

I reproduce the same bug (suspend shut the screen by computer is still running) but its not related to radeon in my case since I have a nvidia card with optimimus. Was working well on 15.10.

* i7 6700HQ
* NVIDIA GeForce GTX 950M

Revision history for this message
Sameera Wijayasiri (sameermw) wrote :

Same issue on HP 15-AC003TX Notebook. i5, 8GB RAM, Intel HD5500 + AMD Radeon R5 M330 Graphics (2 GB DDR3 dedicated). Ubuntu 16.04 Fresh Installation and Kernel 4.0-21-generic.

Revision history for this message
Benny (benny-lutati) wrote :

Same issue on Dell Latitude 3650, i7, 16GB RAM, AMD Radeon.
Ubuntu 16.04 Fresh install with kernel 4.4.0-21-generic. Suspend worked well on 14.04.

Revision history for this message
clapsus (clapsus) wrote :

Same here, Dell Inspiron 3537. AMD Radeon.
Ubuntu GNOME 16.04 clean install with kernel 4.4.0-21-generic.
Suspend worked on Ubuntu vanilla 14.04.

Revision history for this message
Tim (timpipp) wrote :

PavilionDV7 HP, AMD Radeom,

Same problem after upgrade from 15.10. to 16.4

Worked fine on 15.10

Revision history for this message
Robert (rgiyf) wrote :

Suspend working again on 4.6rc5 and also radeon card. Radeon card was not functioning properly with kernel 4.5.
Ubuntu 16.04 64-bit final on HP Envy 6 with Intel Core i5-3337U and Intel HD4000 + AMD Radeon HD8750m.

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

Can confirm latest mainline kernel (4.6) works.

Revision history for this message
Harish (harish-myemails) wrote :

I am see this log after ubuntu startup
[ 27.444518] amdgpu 0000:03:00.0: couldn't schedule ib
[ 27.444540] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22)
[ 27.444558] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job!

Revision history for this message
Jonas (jothro) wrote :

Same here after upgrade from 14.04.4 to 16.04, reverting to 4.2.0-35-generic fixed this.

CPU: Intel i7-2670QM with integrated Intel HD3000
dGPU: AMD Radeon HD6770M

Revision history for this message
yuce (tklx) wrote :

Installing kernel 4.4.11 fixes this issue. You can find the precompiled kernels here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.11-xenial/

Revision history for this message
hesediel84 (hesediel84) wrote :

For me new kernels still does not solve the problem

Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote :

I cna confirm that .11 works for me as well.
@hesediel84: Did you verify that you were running on .11, e.g. by running `uname -a`?

Revision history for this message
penalvch (penalvch) wrote :

hesediel84, could you please test the latest mainline kernel (4.7-rc1) and advise to the results?

tags: added: bios-outdated-f.1f
tags: added: latest-bios-f.1f
removed: bios-outdated-f.1f
tags: added: regression-release xenial
Changed in linux (Ubuntu):
importance: High → Medium
status: Confirmed → Incomplete
no longer affects: linux (Ubuntu)
affects: linux → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Unknown → Undecided
status: Unknown → New
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
hesediel84 (hesediel84) wrote :

Christopher

the actual 4.7 rc1 doesnt work on my pc, it gives a socket error and the PC dies not start at all.
I will check eventuals new version for trying

Revision history for this message
penalvch (penalvch) wrote :

hesediel84, what about the next most recent release (4.6.1)?

Revision history for this message
hesediel84 (hesediel84) wrote :

Sorry nothing also with the 4.6.1 i got the same error of the 4.7:

http://s33.postimg.org/u9u0pn4sv/20160606_142519.jpg

Revision history for this message
penalvch (penalvch) wrote :

hesediel84, any improvement with the recent 4.7-rc2?

Revision history for this message
hesediel84 (hesediel84) wrote :

the 4.7-rc2 starts the pc but, i dont know guys, maybe its my pc particular....same thing as the others kernels....the suspension does not work...some times the pc freezes with the wallpaper...pressing again the power button it return to work....but no suspension.

Revision history for this message
penalvch (penalvch) wrote :

hesediel84, the next step is to fully commit bisect from kernel 4.2 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: kernel-bug-exists-upstream-4.7-rc2 needs-bisect
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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