[HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does not turn back on after resuming from suspend

[Markus Ilmola]

On HP Pavilion dv6 the laptop display does not turn back on when resuming from suspend.
External monitor wakes up just fine and the computer works normally except for the build in display which remains black. It should be noted that this is a dual graphics laptop (lspci | grep VGA):
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)

WORKAROUND: Suspending with "sudo pm-suspend --quirk-test --quirk-s3-bios" makes the computer resume normally with fully working display.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: markus 1907 F.... pulseaudio
 /dev/snd/controlC0: markus 1907 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 28 18:53:18 2014
HibernationDevice: RESUME=UUID=ab1af41b-a639-463f-b406-431c8778f79d
InstallationDate: Installed on 2014-04-27 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8b0f125d-261b-4d22-939f-546340147d79 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 358D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 33.18
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F110000244610000620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 058F110000244610000620100
dmi.sys.vendor: Hewlett-Packard

===
break-fix: - 66c2b84ba6256bc5399eed45582af9ebb3ba2c15

[Brad Figg (brad-figg)]

This change was made by a bot.

[Markus Ilmola (markus-ilmola)]

Model is: HP Pavilion dv6-6145eo
Product is: QC641EA

[Christopher M. Penalver (penalvch)]

Markus Ilmola, as per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=5153075#N1270 an update to your BIOS is available (F.21). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[jose (o1485726)]

Is this the same bug? https://bugs.freedesktop.org/show_bug.cgi?id=42960
This is the workaround: https://bugs.freedesktop.org/show_bug.cgi?id=42960#c15

[Markus Ilmola (markus-ilmola)]

I can confirm that the workaround works.

Suspending with "sudo pm-suspend --quirk-test --quirk-s3-bios" makes the computer resume normally with fully working display.

[Yaron Artzi (yaron160)]

I have the same or a similar problem on my hp pavilion dv6-6150ej.
Problem description:
On some occasions, when asking Ubuntu to suspend and closing the lid, the computer stays on and does not suspend. When opening the lid the screen is black and the computer doesn't seem to respond.
I have Ubuntu 14.04 Linux version 3.13.0-32-generic.
I don't know what other info you may require.

[Christopher M. Penalver (penalvch)]

Yaron Artzi, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

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

[jose (o1485726)]

The fix has been commited: https://bugs.freedesktop.org/show_bug.cgi?id=42960#c57 , but apparently the patch hasn't been merged in any kernel in ubuntu.
Could you guys please merge it?

[jose (o1485726)]

I can confirm that the fix from fd.o (comment #10 ) works for me. I'm running kernel v4.0-rc3 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc3-vivid/ (not recommended for unexperienced users...), and after removing the quirks from pm-suspend, the machine recovers from suspend without issues.
I was told in IRC (#ubuntu-kernel @ freenode) that the patch will be included in the next batch of kernel releases.

[jose (o1485726)]

I'm now using the linux-generic-lts-utopic package (version 3.16.0.34.27, from proposed) and can now confirm that the fix works. I had to remove the quirks, though.
@apw: thank you!

[Adam Conrad (adconrad)]

Adding a trusty task, as this seems like a trivial cherrypick for an SRU. The kernel team, of course, may decide to override me on this. :P