HP 470g3 - not resume from standby

Bug #1649945 reported by federico
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When the power button is pressed for resume from standby, screen remain black. I'm unable to do anything, and I have to power off the laptop using power button.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fede 1889 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Wed Dec 14 17:16:27 2016
HibernationDevice: RESUME=UUID=816f3e30-e513-4954-a9ff-ec6b3bdb1d31
InstallationDate: Installed on 2016-12-09 (5 days ago)
InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 04ca:7053 Lite-On Technology Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProBook 470 G3
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=fde6b822-66d8-454a-b3f1-fd5eb2c4d7ba ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-53-generic N/A
 linux-backports-modules-4.4.0-53-generic N/A
 linux-firmware 1.157.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: HP
dmi.bios.version: N78 Ver. 01.12
dmi.board.name: 8102
dmi.board.vendor: HP
dmi.board.version: KBC Version 40.60
dmi.chassis.asset.tag: 5CD641304R
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrN78Ver.01.12:bd06/14/2016:svnHP:pnHPProBook470G3:pvr:rvnHP:rn8102:rvrKBCVersion40.60:cvnHP:ct10:cvr:
dmi.product.name: HP ProBook 470 G3
dmi.sys.vendor: HP

Revision history for this message
federico (speedfede55) 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
federico (speedfede55) wrote :

First post was incomplete, more informations:

Precitations
This issue is present shutting the lid of my laptop, which is set to suspend on close and also clicking the word Suspend in the GUI.
Shutting the lid of my laptop + power button to resume: black screen.
Standby clicking the word Suspend in the GUI + power button to resume: appear the login screen but all is freeze, also the pointer.
In both cases I have to power off the laptop with long pressing the power button.

More tests
Here there are more logs. Operation that I did before make these logs:
- disabled auto suspend after lid close
- suspend using Suspend button in the GUI
- resuming using the power button (appears freezed login screen)
- power off long pressing power button
- start and create logs attached in this post

cat /proc/acpi/wakeup > wakeup [output in wakeup.txt]
sudo su
echo freezer > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((nothing happens for more than 30 seconds so I suspend using GUI button, resume using power button (black screen), long press power button to power off, boot the system))

dmesg > dmesg-freezer.txt [output in dmesg-freezer.txt]
sudo su
echo devices > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((few seconds, then black screen for 2-3 seconds, re-appear the screen when I run the "sudo...pm-suspend" command but all is freezed, long press power button to power off, boot the system))

dmesg > dmesg-devices.txt [output in dmesg-devices.txt]
sudo su
echo platform > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((SAME SEQUENCE in previous parenthesis))

dmesg > dmesg-platform.txt [output in dmesg-platform.txt]
sudo su
echo processors > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((SAME SEQUENCE in previous parenthesis))

dmesg > dmesg-processors.txt [output in dmesg-processors.txt]
sudo su
echo core > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((SAME SEQUENCE in previous parenthesis))

dmesg > dmesg-core.txt [output in dmesg-core.txt]
sudo su
echo none > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
((after some seconds system is suspended, I press power butto to resume, appear the screen when I run the "sudo...pm-suspend" command but all is freezed, long press power button to power off, boot the system))
dmesg > dmesg-none.txt [output in dmesg-none.txt]
cat /proc/acpi/wakeup > wakeup [output in wakeup-none.txt]

In dsmeg-freeze.txt i found
[...]
[ 4.130534] Magic number: 12:508:188
[ 4.130595] thermal LNXTHERM:04: hash matches
[ 4.130603] acpi device:47: hash matches
[ 4.130608] acpi device:1a: hash matches
[...]
In all other dsmeg-*.txt logs there is this two lines
[ 4.******] Magic number: 15:0:0
[ 4.******] memory memory48: hash matches

I don't know if my sequence is bad or not, I've try to follow the https://wiki.ubuntu.com/DebuggingKernelSuspend guide but whitout (I'm sorry) modify the RTC clock. So I don't know if my logs are useful or not.

Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
Revision history for this message
federico (speedfede55) wrote :
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.9 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.9

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

No, this is a new computer and this is a fresh install. I'm really sorry but at this time I'm unable to try the latest upstream kernel.
But I confirm that this issue is also present in these kernels (they are the latest kernels present in the official Mint Update Manager):
4.8.0-30
4.8.0-32
4.8.0-34

Revision history for this message
federico (speedfede55) wrote :

Ok, now I test the upstream kernel from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5/

kernel tested is:
4.10.0-041000rc5-generic

Now with this kernel, going to standby using suspend button in the GUI, and resuming from standby using the power button, the bug is still NOT present, ubuntu seems to resume from standby correctly.

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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.