Display remains fully dimmed after resume from suspend

[Michael Steffens]

After resuming from suspend the display returns fully dimmed, and display brightness can't be adjusted, neither using FN keys, nor using KDE power management control. The issue occurs regardless whether the suspend state was activated by low battery, by closing the display, or by explicitly selecting sleep mode in KDE. Killing and restarting X does not solve the problem. A reboot does.

---
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: michael 2554 F.... pulseaudio michael 2784 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=8dc81a6f-65e9-443d-b850-0f62a1ca52c4 InstallationDate: Installed on 2012-05-13 (909 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424)
MachineType: Hewlett-Packard HP EliteBook 8530w
Package: linux (not installed)
PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic root=/dev/mapper/vg00-lv_root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.7
Tags: trusty
Uname: Linux 3.13.0-39-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-10 (181 days ago)
UserGroups: _MarkForUpload: True
dmi.bios.date: 06/24/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.0C
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.0C:bd06/24/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.0C:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.0C
dmi.sys.vendor: Hewlett-Packard

[Michael Steffens (michael-steffens-b)]

Additional information: Unlike described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282 the problem does not disappear with subsequents suspen/resume cycles.

So far a reboot is the only way for me to get display brightness back.

[Brad Figg (brad-figg)]

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

apport-collect 1390764

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.

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

apport information

[Michael Steffens (michael-steffens-b)]

Done.

[Michael Steffens (michael-steffens-b)]

Christopher, the BIOS update package you are referring me to contains only Windows runnable files, and doesn't contain the README file your BIOSUpdate link is referring to:

Extracting cabinet: Downloads/sp55640.exe
  extracting bios/HPQFlash.exe
  extracting bios/Rom.CAB
  extracting bios/WSSP55640.rtf

WSSP55640.rtf is giving directions only for Windows, too. No mention of how to create an ISO image to perform the update, or alike. On the other hand, there is no Windows or DOS of any kind on my PC, and no space left to create one ...

How sure are you that the outdated BIOS is causing the issue, and if so, do you have any hint how to get the bios flashed anyway?

[Michael Steffens (michael-steffens-b)]

Managed to upgrade from F.0C to

# dmidecode -s bios-version && dmidecode -s bios-release-date
68PDV Ver. F.12
06/08/2010

using the Rom.ISO from

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=3781683&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D%257CswItem%253Dob_85083_3%257CswEnvOID%253D4060%257CitemLocale%253D%257CswLang%253D%257Cmode%253D%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

[Michael Steffens (michael-steffens-b)]

No success to get any more recent version than F.12 flashed without a natively running Windows -- which my Laptop doesn't have. And F.12 doesn't fix the dimming issue when resuming from suspend.

[Michael Steffens (michael-steffens-b)]

Managed to upgrade to latest BIOS release by temporarily mounting a Windows HD. Result:

# dmidecode -s bios-version && dmidecode -s bios-release-date
68PDV Ver. F.20
12/08/2011

The dimming issue when resuming from suspend remains.

[penalvch (penalvch)]

Michael Steffens, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Michael Steffens (michael-steffens-b)]

Kernel 3.19.0-031900-generic boots fine, but doesn fix the issue, either.

[penalvch (penalvch)]

Michael Steffens, did this issue not occur in a release prior to Trusty?

[Michael Steffens (michael-steffens-b)]

IIRC it did also occur in Precise. I don't remember how earlier releases behaved.

[penalvch (penalvch)]

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

[Michael Steffens (michael-steffens-b)]

Exceuted the tracing steps suggested in https://wiki.ubuntu.com/DebuggingKernelSuspend using the latest mainline kernel

# uname -r
3.19.0-031900-generic

and everything worked as expected. The suspend state was entered seconds after running

# sync && echo 1 > /sys/power/pm_trace && pm-suspend

and the notebook resumed within seconds after pushing the power button. As usual the display returned fully dimmed and all controls to alter display brightness have no effect any more.

/proc/acpi/wakeup has not changed between suspend and resume. The RTC is skewed by nearly 21 years

# hwclock --show
Thu 19 Apr 1984 06:00:15 PM CEST -0.485252 seconds

indicating that some tracing information were put there. However, I can find only find one pair of

[ 1.981094] Magic number: 3:558:892
[ 1.981174] bdi default: hash matches

which was already included in dmesg before suspend, and doesn't quite match the pattern of what to watch out for. I am attaching dmesg output both gathered before and after suspend/resume.

[penalvch (penalvch)]

Michael Steffens, could you please provide item 2. uncompressed/untarred?

[penalvch (penalvch)]

Michael Steffens, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-acpi) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.