[HP Compaq dc7800 Small Form Factor PC] suspend/resume failure

[Urs Fleisch]

Suspend to RAM fails on HP Compaq dc7800p, the PC will not wake up again. It only works if I suspend to disk before, then I can suspend to RAM afterwards (as many time as needed) until the PC is rebooted again.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-18-generic 3.16.0-18.25
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: urs 1849 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Sep 30 20:44:46 2014
DuplicateSignature: suspend/resume:Hewlett-Packard HP Compaq dc7800p Small Form Factor:786F1 v01.32
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=c338e9df-bc69-4692-b108-88cfd64982a7
InstallationDate: Installed on 2014-09-28 (2 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic root=UUID=6475de33-f0cf-4e4a-b155-bac5d4c61b27 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-18-generic N/A
 linux-backports-modules-3.16.0-18-generic N/A
 linux-firmware 1.134
RfKill:

SourcePackage: linux
Title: [Hewlett-Packard HP Compaq dc7800p Small Form Factor] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/21/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F1 v01.32
dmi.board.asset.tag: CZC81885DS
dmi.board.name: 0AA8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC81885DS
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786F1v01.32:bd07/21/2011:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq dc7800p Small Form Factor
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.17-rc7-utopic/

[Urs Fleisch (ufleisch)]

Thanks for catching up, the bug exists also with the upstream kernel (and also with the kernels of prior Ubuntu versions). I have set the tags and status accordingly.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[penalvch (penalvch)]

Urs Fleisch, upstream would want to know a few things first before you send an e-mail out to a mailing list. For example, did this problem not occur in a release prior to 14.10?

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

[Urs Fleisch (ufleisch)]

I have this problem since I have this PC (2011-12-03), i.e. I always have to hibernate before I can suspend to RAM with all Ubuntu releases since 11.10. I also tried the procedure described in DebuggingKernelSuspend in the past and tried to remove various kernel modules but without success.

I have now followed the procedure described in DebuggingKernelSuspend and attached the wakeup and dmesg.txt files. After trying to resume from suspend, the LEDs and the noise from the DVD-RW are the same as with a successful resume. However, the display stays dark and I cannot connect to the system over the network (ping or SSH).

The magic number in dmesg is

[ 2.088671] Magic number: 2:310:476

but there is no "hash matches" line.

[Urs Fleisch (ufleisch)]

I have the same behavior with all Ubuntu releases since I have this PC, i.e. with 11.10 to 14.10. I can only suspend to RAM after a suspend to disk.

[Matt Taylor (dingus)]

Hi,
Did an upstream bug get filed for this? I have the same pc model (HP Compaq dc7800p) and have always seen the same odd behaviour where the pc must first be put into hibernate before it will be able to resume from suspend to RAM. I have seen this behaviour in both Ubuntu and Arch linux (every version I have tried going back several years).

I currently don't use Ubuntu on this pc and came across this report looking for something else (updating kernel from 3.16.2 to 3.17.3 on Arch also broke my ability to hibernate so I couldn't access suspend of any kind without downgrading again). But I thought an additional confirmation of this bug (and as an upstream issue) could be helpful.

[penalvch (penalvch)]

Matt Taylor, while "Me too!" comments are largely unhelpful, what would be helpful is if you filed a new report, and so your hardware and problem may be tracked, with Ubuntu (live environment is fine) 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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

[Urs Fleisch (ufleisch)]

@Matt Taylor
I have not filed an upstream bug for this. Until now I was not sure if I am the only one having this bug, so this information is helpful for me at least. As you can see in the activity log, I followed the procedure suggested in the Ubuntu Wiki, however, this did not result in more information. I also tried to remove as many kernel modules as possible, but I was still not able to resume. I even connected a serial console to my PC to see if some information is printed while supending/resuming, but the console is switched off before the freeze. Maybe there is more debug instrumentation in the kernel which could be activated or we have to modify the kernel with printk statements or use kgdb to find the place where it is freezing or the difference between the states after hibernation and power-up.

[Urs Fleisch (ufleisch)]

Since Ubuntu 15.10, we have a regression: Suspend to RAM never works, the workaround with first suspending to disk no longer works. I have tested this with both the current Ubuntu kernel (4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) and the latest kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc5-wily/ (4.4.0-040400rc5.201512140221).

With Arch Linux on the same machine, suspend to RAM works after hibernate, so this looks like a regression introduced with Ubuntu Wily. What has changed with suspend-resume from 15.04 to 15.10?

[penalvch (penalvch)]

Urs Fleisch, to advise, the scope of this report is only suspend not working when one attempts to use it the first time.

Despite this, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list? Given the root cause driver hasn't been identified, it wouldn't hurt to report this to linux-pm to see if they can provide additional suggestions.

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

[Urs Fleisch (ufleisch)]

I have reported the bug upstream, see https://bugzilla.kernel.org/show_bug.cgi?id=109811

[penalvch (penalvch)]

Urs Fleisch, to advise, posting to bugzilla isn't a mailing list, nor is it the appropriate venue, given the root cause isn't necessarily suspend itself, but likely a buggy driver instead. This is why it was requested of you to post to the linux-pm mailing list.

[Russ Bond (warlockzone)]

I think this is not a bug of Ubuntu or any OS. This is bug of HP BIOS, they should disable and delete ACPI S3 Hard Disk Reset in OS Power Management because if is enabled, it causing problem of wake from sleep/suspend. I disable this option and sleep/suspend works good in all my OSes. http://ipic.su/arBCs.jpg

[Urs Fleisch (ufleisch)]

Thanks for the hint. I disabled "ACPI S3 Hard Disk Reset" in the BIOS, but it did not improve the situation. I also tried disabling all the other power related settings in the BIOS, but this did not help either. I still have to suspend to disk first in order to have suspend to RAM working.

[Russ Bond (warlockzone)]

Strange it's should works. I searched it hand by hand. I forget to say what i have Convertible Minitower, and latest v1.35 bios + ME v3.2.20.1049.