[HP Compaq nx6325 Notebook PC] suspend/resume failure

[Tobiasz Jarczyk]

Last tested with kernel 3.13-rc6.

Laptop fails to suspend to RAM after being waken up from such a suspend (always hangs during second suspend).

To reproduce on my laptop HP Compaq nx6325 EY349EA#AKD:
1. Suspend to RAM.
2. Wake up from suspend.
3. Suspend to RAM again.
4. During this suspend computer hangs - monitor is blank, power light is on, processor becomes very hot so the cooler is on full speed. At this point I have to hard reset it.

Upstream mailing list post: http://article.gmane.org/gmane.linux.power-management.general/41715

WORKAROUND: Hibernate.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dotnokato 1756 F.... pulseaudio
Date: Thu May 2 10:11:29 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=ce4acd9b-ecba-4931-baa2-0c2d6409dbf6
InstallationDate: Installed on 2012-10-06 (207 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
InterpreterPath: /usr/bin/python3.3
Lsusb:
 Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
 Bus 003 Device 003: ID 04b4:0033 Cypress Semiconductor Corp. Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP Compaq nx6325 (EY349EA#AKD)
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=4f0c1391-e243-4e37-aaab-52625df3e3bd ro quiet splash vt.handoff=7
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.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
SourcePackage: linux
Title: [Hewlett-Packard HP Compaq nx6325 (EY349EA#AKD)] suspend/resume failure
UpgradeStatus: Upgraded to raring on 2013-03-09 (53 days ago)
UserGroups:

dmi.bios.date: 05/08/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68TT2 Ver. F.07
dmi.board.name: 30B0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 40.15
dmi.chassis.asset.tag: CNU7110B09
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nx6325 (EY349EA#AKD)
dmi.product.version: F.07
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Brad Figg (brad-figg)]

There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.

You can update to the latest kernel by simply running the following commands in a terminal window:
    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the
bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Tobiasz Jarczyk (dotnokato-q)]

The issue is still reproducible.
System failed to suspend while playing some youtube video.

$ uname -a
Linux none 3.8.0-26-generic #38-Ubuntu SMP Mon Jun 17 21:43:33 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Tobiasz Jarczyk, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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.11-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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Tobiasz Jarczyk (dotnokato-q)]

Hi, I've tested this issue against v3.11rc2 available at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

The issue exists in the newest upstream kernel (v3.11rc2).

$ uname -a
Linux none 3.11.0-031100rc2-generic #201307211535 SMP Sun Jul 21 19:36:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Tobiasz Jarczyk, thank you for testing the newest mainline kernel. Did this issue not occur in a release prior to Raring?

[Tobiasz Jarczyk (dotnokato-q)]

Christopher M. Penalver,
As far as I remember this did occur in earlier releases prior to Raring.

[penalvch (penalvch)]

Tobiasz Jarczyk, ok. Which releases specifically?

[Tobiasz Jarczyk (dotnokato-q)]

Quantal for sure. Earlier I believe also, but am not sure. It was a long time ago.

[penalvch (penalvch)]

Tobiasz Jarczyk, for regression testing purposes could you please test Precise via http://releases.ubuntu.com/precise/ ?

[Tobiasz Jarczyk (dotnokato-q)]

I have tested both Precise and Quantal using live-images. The issue is reproducible on both.

Here is the uname -a from those systems:
Precise:
Linux ubuntu 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Quantal:
Linux ubuntu 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Tobiasz Jarczyk, thank you for testing Precise. For regression testing purposes, could you please test for this in Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[Tobiasz Jarczyk (dotnokato-q)]

In Lucid, the issue is also reproducible.

$uname -a
Linux ubuntu 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC 2012 x86_64 GNU/Linux

[penalvch (penalvch)]

Tobiasz Jarczyk, thank you for testing for this in Lucid. Could you please boot into the newest mainline kernel available, and gather the information noted in https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Tobiasz Jarczyk (dotnokato-q)]

$ uname -r
3.11.0-031100rc4-generic

1. Product: Compaq nx6325
s/n: CNU7110B09
p/n: EY349EA#AKD
2. I've got the newest BIOS.
3. attached

4. Now, here I have some problems:
$ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
sh: 1: cannot create /sys/power/pm_trace: Directory nonexistent

Is there something I am missing?

Thanks in advance,
Tobiasz

[Tobiasz Jarczyk (dotnokato-q)]

Christopher M. Penalver, could I ask for your assistance with this report? This is my first upstream kernel bug.
I've prepared a draft of a report in the kernel.org format, but I am not sure what to put in the following paragraphs:
[5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt)
[X.] Other notes, patches, fixes, workarounds

I'm attaching this report in .txt format. If possible, please take a look at it and let me know if I should change anything before sending it to the maintainers.

Thanks in advance,
Tobiasz

[Tobiasz Jarczyk (dotnokato-q)]

Hi,
I have tested it with the most recent kernel (3.11.rc5) and I am still
experiencing this issue.

$ uname -a
Linux none 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12
01:35:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Pozdrawiam / Regards
Tobiasz "dotnokato" Jarczyk

W dniu 13.08.2013 15:32, Rafael J. Wysocki pisze:
> On Tuesday, August 13, 2013 02:15:20 PM Tobiasz 'dotnokato' Jarczyk wrote:
>> [1.] One line summary of the problem:
>> [Hewlett-Packard HP Compaq nx6325 (EY349EA#AKD)] suspend/resume failure
> As it happens I have that machine and suspend/resume works on it for me
> with 3.10.y at least.
>
> Care to test a more recent kernel?
>
> Rafael
>
>
>> [2.] Full description of the problem/report:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175504
>>
>> Laptop fails to suspend to RAM after being waken up from such a suspend
>> (always hangs during second suspend).
>>
>> To reproduce on my laptop HP Compaq nx6325 EY349EA#AKD:
>> 1. Suspend to RAM.
>> 2. Wake up from suspend.
>> 3. Suspend to RAM again.
>> 4. During this suspend computer hangs - monitor is blank, power light is
>> on, processor becomes very hot so the cooler is on full speed. At this
>> point I have to hard reset it.
>>
>>
>> ProblemType: KernelOops
>> DistroRelease: Ubuntu 13.04
>> Package: linux-image-3.8.0-19-generic 3.8.0-19.29
>> ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
>> Uname: Linux 3.8.0-19-generic x86_64
>> Annotation: This occured during a previous suspend and prevented it from
>> resuming properly.
>> ApportVersion: 2.9.2-0ubuntu8
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: dotnokato 1756 F.... pulseaudio
>> Date: Thu May 2 10:11:29 2013
>> ExecutablePath: /usr/share/apport/apportcheckresume
>> Failure: suspend/resume
>> HibernationDevice: RESUME=UUID=ce4acd9b-ecba-4931-baa2-0c2d6409dbf6
>> InstallationDate: Installed on 2012-10-06 (207 days ago)
>> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
>> InterpreterPath: /usr/bin/python3.3
>> Lsusb:
>> Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint
>> Sensor
>> Bus 003 Device 003: ID 04b4:0033 Cypress Semiconductor Corp. Mouse
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>> MachineType: Hewlett-Packard HP Compaq nx6325 (EY349EA#AKD)
>> MarkForUpload: True
>> PccardctlIdent:
>> Socket 0:
>> no product info available
>> PccardctlStatus:
>> Socket 0:
>> no card
>> ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
>> ProcEnviron:
>> TERM=linux
>> PATH=(custom, no user)
>> ProcFB: 0 radeondrmfb
>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic
>> root=UUID=4f0c1391-e243-4e37-aaab-52625df3e3bd ro quiet splash vt.handoff=7
>> 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.8.0-19-generic N/A
>> linux-backports-modules-3...

[Tobiasz Jarczyk (dotnokato-q)]

Christopher M. Penalver, I have followed the instructions.
I have CCd also launchpad bug via <email address hidden>, but launchpad didn't include my report as a comment (maybe a bug in launchpad?).
Comment #20 is part of that thread (not the first one).
The whole conversation is available here: http://marc.info/?t=137639667200008&r=1&w=2

[Tobiasz Jarczyk (dotnokato-q)]

W dniu 14.08.2013 00:42, Rafael J. Wysocki pisze:
> On Tuesday, August 13, 2013 03:29:47 PM Tobiasz 'dotnokato' Jarczyk wrote:
>> Hi,
>> I have tested it with the most recent kernel (3.11.rc5) and I am still
>> experiencing this issue.
> Well, for me suspend with 3.11-rc5 breaks on that box too, but with 3.10.6 it
> actually works up to a VT switch that doesn't (it resumes to a black screen,
> but switching to VT1 and back to X helps). A couple of other things don't
> work on it with 3.10.6, sadly.
>
> I have openSUSE 12.3 installed on it.
>
> Thanks,
> Rafael
>
I get the same behavior when using 3.10.6 and 3.11.rc5. The system fails
to suspend for the second time (first time always works fine).
When waking from the first suspend I get screen flickering and just like
you wrote, switching to VT1 and back to X helps.

I have Ubuntu Gnome 13.10.

Pozdrawiam / Regards
Tobiasz "dotnokato" Jarczyk

[Tobiasz Jarczyk (dotnokato-q)]

Hi,
Yep, issue still exists in daily ISO and in http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/
In both cases, suspend seems to work fine, but then computer doesn't wake up - have to do hard reboot.

[Tobiasz Jarczyk (dotnokato-q)]

Hi Christopher M. Penalver,
I've just created an upstream report for kernel version 3.13-rc6. I will provide the URL as soon as I will be able to find it ;-)

Regarding hibernate: I am on Ubuntu Gnome and cannot hibernate.

[Tobiasz Jarczyk (dotnokato-q)]

OK, I found it: http://article.gmane.org/gmane.linux.power-management.general/41715

[penalvch (penalvch)]

Tobiasz Jarczyk, thank you for providing the requested information. As a potential WORKAROUND, are you able to hibernate following https://help.ubuntu.com/community/PowerManagement/Hibernate ?

[Tobiasz Jarczyk (dotnokato-q)]

Using the above method (swsusp) for hibernate is working fine for me.