HP ProBook 450 G1, resume from hibernate does not work unless acpi_osi=Linux boot parameter is used

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

Bug Description

Tested on HP ProBook 450 G1 notebook with Linux Mint 17 (based on Ubuntu 14.04) on a lot of kernel versions up to 4.4.0-47-generic #68~14.04.1.

While resuming from stand-by works perfectly, resuming from hibernation does not work out-of-the-box (after unlocking the hard disk with dm-crypt, the screen remains black).

To make resume from hibernate work, the "acpi_osi=Linux" kernel boot parameter must be used.

Using it successfully right now with kernel version "Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24".
---
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mauro 4136 F.... pulseaudio
 /dev/snd/controlC0: mauro 4136 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=624e1b41-1347-45e8-aa4b-f6e2dc9c87a2
InstallationDate: Installed on 2014-09-30 (1004 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140619
MachineType: Hewlett-Packard HP ProBook 450 G1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/mint--vg-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 acpi_osi=Linux vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.127.23
Tags: rosa
Uname: Linux 4.4.0-47-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse libvirtd lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 05/03/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L74 Ver. 01.40
dmi.board.name: 1942
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 89.12
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.40:bd05/03/2016:svnHewlett-Packard:pnHPProBook450G1:pvrA3009DD10303:rvnHewlett-Packard:rn1942:rvrKBCVersion89.12:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 450 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Mauro (mauromol) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1701081

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
tags: added: xenial
Revision history for this message
Mauro (mauromol) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected rosa
description: updated
Revision history for this message
Mauro (mauromol) wrote : BootDmesg.txt

apport information

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

apport information

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

apport information

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

apport information

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

apport information

Revision history for this message
Mauro (mauromol) wrote : Lsusb.txt

apport information

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

apport information

Revision history for this message
Mauro (mauromol) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Mauro (mauromol) wrote : ProcEnviron.txt

apport information

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

apport information

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

apport information

Revision history for this message
Mauro (mauromol) wrote : PulseList.txt

apport information

Revision history for this message
Mauro (mauromol) wrote : RfKill.txt

apport information

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

apport information

Revision history for this message
Mauro (mauromol) wrote : UdevLog.txt

apport information

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

apport information

Changed in linux (Ubuntu):
status: Incomplete → 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.12 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.12

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Mauro (mauromol)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-fixed-upstream
Revision history for this message
Mauro (mauromol) wrote :

I tested this for a while to be sure of the results. It appears that with the mainline kernel 4.13.0-041300rc1-generic resuming from hibernate works perfectly without the need to add the "acpi_osi=Linux" kernel boot parameter. It worked correctly and reliably 100% of the times I tried it (even repeatedly without a full shutdown).

Instead, even with the (almost) latest 4.2.0-83 Ubuntu kernel, more often than not resuming from hibernate produces a blank screen after unlocking the hard disk (for dm-crypt), unless the "acpi_osi=Linux" kernel boot parameter is used. I must also say that, in any case (even with such added parameter), sometimes resuming is not 100% reliable because some devices seems not to wake up correctly (it happened with keyboard or touchpad in my case, a couple of times).

Revision history for this message
Mauro (mauromol) wrote :

Sorry, in my previous comment I meant 4.4.0-83 Ubuntu kernel.

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.