[HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

[Arto Makkonen]

My HP notebook won't wake from suspend with 16.04 LTS, waited for the latest 4.4.0-36 kernel update before reporting this bug. Computer goes to suspend, but attempts to wake it up just start the fan (and HDD) while the display remains black.

Also tested this with the mainline upstream kernel 4.8.0-040800rc3-generic. With this version there was different behaviour but still a bug: the display woke up but Ubuntu was very unstable, did not connect to Wifi and the GUI froze very soon after resume.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: arto 3449 F.... pulseaudio
 /dev/snd/controlC1: arto 3449 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 30 19:42:38 2016
HibernationDevice: RESUME=UUID=8b70a4a1-df29-4f51-9b65-c2a17b4361a2
InstallationDate: Installed on 2015-09-18 (347 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=c1e1c032-887a-44c8-b4d2-0850b57082e8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-08-15 (15 days ago)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2212
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0976100000405F00000620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 0976100000405F00000620180
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

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

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

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

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

[Arto Makkonen (arto-o-makkonen)]

This issue did not appear after an update/upgrade - I recall having it also with 14.04 LTS where I ended up never suspending the laptop (never reported a bug myself before, though). Now my usage profile has changed and suspend/resume is important.

To the upstream question - unfortunately this issue is not fixed by the mainline kernel 4.8.0-040800rc3-generic. Added the kernel-bug-exists-upstream tag.

[penalvch (penalvch)]

Arto Makkonen, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc4) as it is released.

Could you please advise?

[Arto Makkonen (arto-o-makkonen)]

Suspend / resume issue still exists in 4.8-rc4. After resume, display goes to login screen that looks normal except for missing wireless status indicators. I was able to type in my password but the GUI froze shortly after.

Please check that my bug tag and status changes are correct.

[Arto Makkonen (arto-o-makkonen)]

Thanks for letting me know that a new bios version is available (oddly the HP support site did not show any available bios versions for my laptop with 'Windows 10' setting, but F39 and F18 were available by setting OS to 'Windows 8.1').

Unfortunately the bios update does not solve the problem (tested both with 4.0.0-36 and 4.8-rc4).

Here is the requested output:

arto@Kotikone:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
F.39
05/26/2015

With the new bios, my notebook does go to suspend. When attempting to resume, the fan turns on for a few seconds, wireless LAN led on F12 function key turns on and remains lit but the display stays black.

I'd be happy to provide additional logs or other information if needed.

[penalvch (penalvch)]

Arto Makkonen, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Arto Makkonen (arto-o-makkonen)]

Here is the output of the sudo cat /sys/kernel/debug/suspend_stats command after taking the steps from https://wiki.ubuntu.com/DebuggingKernelSuspend

success: 0
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
  last_failed_dev:

  last_failed_errno: 0
   0
  last_failed_step:

SSH connection was not possible during the blank screen after resume. Tried both WLAN and fixed. Apparently networking is down after resume.

I'm nevertheless attaching /var/log/Xorg.0.log.old in the hope that this would give additional information (not from SSH, this is from normal boot and login with 4.8-rc4)

[Arto Makkonen (arto-o-makkonen)]

Here's /var/log/Xorg.0.log file - not from SSH but from normal boot after resume, using 4.8-rc4

[penalvch (penalvch)]

Arto Makkonen, could you please provide the rest of the missing information?

[Arto Makkonen (arto-o-makkonen)]

If you are referring to the '"resume-trace" debugging procedure for finding buggy drivers', I'm still evaluating if this is beyond my skills.

In particular I don't understand this paragraph:

"Caveat Emptor: Using the following debug suggestions will radically change the values in your RTC chip, so much so that your file system will think it has been eons since the last fsck. You can avoid a long fsck delay by using 'tune2fs'. For example, 'tune2fs -i 0 /dev/sda1' disables fsck on boot. But first you'll want to use 'tune2fs -l <partition>' to find your current settings - look at the "Check interval" setting."

Do I need to disable something in boot before or after the resume-tracing proceduce? What is the consequence of file system thinking it has been eons since the last fsck?

Sicne I don't wish to mess my computer, it would be great if someone could provide fool proof instructions for this part, including suggested terminal commands in the right order.

[Arto Makkonen (arto-o-makkonen)]

Here is a summary of the information that I can provide:

1. Which part of the process does the issue occur with, the suspend to ram, or resuming from?
Please advise how you suspended specifically. For example:

  Issue occurs when resuming.
  I have suspended using the following methods: i) Click GUI menu item "Suspend" and
  ii) Briefly press the power button

2. Please advise how you resumed specifically.

  I have resumed by pressing space or the power button. The commands below were run after
  attempting to resume by pressing the power button.

3.-10. [various commands] + Please attach to your report the resume trace mentioned below.

  Commands run but I'm getting an error running the resume trace following the "resume-trace
  debugging procedure for finding buggy drivers" method:

  sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
  sh: 1: cannot create /sys/power/pm_trace: Permission denied

Please advice.

11. Please provide the output of the following terminal command:

  cat /sys/kernel/debug/suspend_stats

  Done. Please see my reply #10 above.

12. If you have a graphics related issue after resume (corruption, display blank, etc.) please SSH into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. Please attach each separately.

  I have this issue but SSH connection was not possible during the blank screen after resume.
  Tried both WLAN and fixed connection. Apparently networking is down after resume. Attached
  both log files nevertheless. See the attachments in replies #10 and #11 below

Please help me solve the "Permission denied" error to enable tracing in steps 3.-10. Also, please clarify if you need a separate resume trace from every step or just one trace after completing all of the steps 3-10.

[penalvch (penalvch)]

Arto Makkonen, not sure on why all of a sudden one gets a permission denied. The article may need to be updated.

Despite this, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc5) as it is released.

Could you please advise?

[Arto Makkonen (arto-o-makkonen)]

Tested with 4.8-rc8. It was possible to login after the resume and use the GUI in offline mode for several minutes. Two observations: 1) Wifi and networking are not available after resume, 2) Ubuntu hangs when selecting "Shut down" from the menu.

Could this issue be related to the RT3290 wireless interface of this HP model?

[penalvch (penalvch)]

Arto Makkonen, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Arto Makkonen (arto-o-makkonen)]

Like discussed on Sep 9 in this same thread, creating the kernel resume trace file fails

$ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
sh: 1: cannot create /sys/power/pm_trace: Permission denied

Please help me solve the "Permission denied" error to enable tracing in steps 3.-10. Also, please clarify if you need a separate resume trace from every step or just one trace after completing all of the steps 3-10.

[Arto Makkonen (arto-o-makkonen)]

Tested with mainline kernel 4.9-rc3 and the bug still exists.

Like discussed on Sep 9 in this same thread, creating the kernel resume trace file fails

$ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
sh: 1: cannot create /sys/power/pm_trace: Permission denied

Please help me solve the "Permission denied" error to enable tracing in steps 3.-10.

[Arto Makkonen (arto-o-makkonen)]

Still there in upstream 4.9-rc8

[Arto Makkonen (arto-o-makkonen)]

Still there, 4.10-rc5

[Arto Makkonen (arto-o-makkonen)]

Repeatable in 4.11-rc6, and I'm yet to receive guidance to the tracing problem discussed above. Have also asked for support in different forums with no results.

[Kai-Heng Feng (kaihengfeng)]

Two questions:
1. Comment #16 is the issue now?
2. What release do you use now? Do you still use Trusty?

[Arto Makkonen (arto-o-makkonen)]

Please find my replies below:

1. I'm seeing various issues after suspend / resume. With the latest kernel builds, typical is that the GUI freezes shortly after resume. Often resume does not complete at all and I only see black screen with a cursor / underscore in the top left corner. I would be happy to do tracing but unfortunately this has not been possible due to a strange permission denied error (see comment #19).

2. Using 16.04 LTS currently

[Kai-Heng Feng (kaihengfeng)]

Please enable journald persistent logging via the following commands:

$ sudo mkdir -p /var/log/journal
$ sudo systemd-tmpfiles --create --prefix /var/log/journal

Suspend your machine, reboot, and attach the output of `journalctl -b -1 -k`.