[HP EliteBook 8740w] suspend/resume failure

This change was made by a bot.

Tested with 3.12.0-031200-generic #201311031935, same issue exists. No difference.

Also attached cat /proc/acpi/wakeup > wakeup

Michiel Janssens, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

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.

Tested with upstream kernel 3.13.0-031300rc1.201311221535.
Same results for this particular issue.

But with this upstream kernel the system doesn't shutdown properly.
It begins shutting down, screen goes blank. After that it's non-responsive, power/fan/leds ar still on.
I then have to long-press the power button to force shutdown.
This only appears with upstream kernel, not with current kernel 3.11.0-13.20

Another thing I noticed:
The reported issue appears when suspending for the first time since booting the system.
However, when waiting a minute after first suspend to wake it up, the issue seems almost gone. Resuming from suspend within 2 seconds is possible, multiple times.

Michiel Janssens, did this problem not occur in a release prior to Saucy?

Hi Christopher,
This also occurred in raring, but I did not report it then, all main kernel versions.
Decided after a while to go experimenting with raring with UEFI Bios options enabled, in the hope that it would respond better, but came to conclusion that it's a very experimental option in my systems BIOS.
So when Saucy came out I turned UEFI off and using the default BIOS settings since saucy fresh install

Before saucy I was running WIndows 7, but cannot recall if this issue happened there.
Running encrypted disk at the moment so installing windows dualboot must be done on an external esata disk.
If this is an option worth investigating please let me know.

Michiel Janssens, one may test suspend via a live environment, so no need to install on esata at this point.

Despite this, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ and advise to the results?

Hi Christopher,

Did some testing as you requested via live usb.
In 12.04 and 12.04.3 the issue is the same.

Also saw that mainline kernel v3.13-rc2 was available, so tested with that also.
No difference, and like v3.13-rc1 shutdown doesn't work.

Changed the tag from kernel-bug-exists-upstream-v3.13-rc1 to kernel-bug-exists-upstream-v3.13-rc2, if thats ok.

Michiel Janssens, quick follow up question, when you wake it via the sleep button on the keyboard within 3-5 seconds, has the system finished suspending?

Hi Christopher,
Every time I test resume, the system is finshed suspending, so screen is off, disks are of, only power led is fading in and out, indicating that its in suspend mode.
Waking the laptop via sleep button is not possible. Only the power button short-press wakes the system.

Michiel Janssens, for regression testing purposes, could you please test for this in live Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

Tested from live usb:
10.04.4 has same issues as reported, going into suspend takes a few seconds longer then saucy.
10.04 won't suspend. When suspending, screen goes black, leds stay on. Then after 10-15 seconds the screen turns back on again. Shutdown works however.

Michiel Janssens, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel (may want to start with linux-pm) by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Please provide a direct URL to your post once you have made it so that it may be tracked.

Thank you for your understanding.

Hi Chirstopher,

The direct url to my post to linux-pm mailinglist:
http://marc.info/?l=linux-pm&m=138617691100712&w=2

It has been a while.
Tested again. Bios still the same.
Now with v4.3-wily kernel. Still the same result.
Now tested with Windows 10 also. Got the same result there too.
I think this really is a bios issue, probably wont be fixed if I ask HP, because its an older model.
And I've learned to live with it.

Better to close the bug report.

Sorry, you are correct that in the posted log, the outdated bios was used.

Output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:
68CAD Ver. F.50
07/07/2014

Comment #16 testing was done with this latest bios installed.

Michiel Janssens, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

Did a suspend resume test, with 15.10, kernel v4.3.
No external monitors connected.

Executed:
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
several seconds after suspend (system is really suspended, blue suspend light is glowing), put it in resume with power button.
As before, other lights go on very shortly, system crashes (all lights off, sound of hdd shutting down not normally, same as long-pressing power button while system running), few seconds after that, system boots by itself, so not resumed.
Did same test with an extra udev rule so that resume with external mouse or keyboard works, same behaviour.

Added dmesg_crash.txt and cat /proc/acpi/wakeup output

Michiel Janssens, if you remove the parameter radeon.dpm=1 does this change anything?

In the initial report the parameter radeon.dpm=1 was used.
However in newer kernels this setting is default, so dpm is enabled by default.

Nevertheless tested latest kernel v4.3 with parameter radeon.dpm=0, no effect

Also tested with parameter pcie_aspm=force and pcie_aspm=off, no effect
pm-suspend with several combinations of quircks --quirk-s3-bios --quirk-vbe-post --quirk-vbemode-restore, no effect.