HP Compaq 6720s does not suspend

[Timur Elzhov]

When trying to suspend laptop, either by choosing "Suspend" from menu or from the keyboard, laptop get suspended by about 1 sec, then it spontaneously resumes up again. It probably depends on the HardDrive with NTFS which is mounted with fuse. When HD is not mounted, the problem occurs less frequently. Using s2ram from uswsusp package works a bit better, but sometimes has the same issue, too.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: elzhov 1902 F.... pulseaudio
 /dev/snd/pcmC0D0p: elzhov 1902 F...m pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe4324000 irq 47'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,103c30d8,00100200 HDA:11c11040,103c1378,00100200'
   Controls : 11
   Simple ctrls : 9
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=/dev/sda6
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Hewlett-Packard HP Compaq 6720s
Package: linux 3.2.0.18.20
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-18-generic root=UUID=98be4b6f-2b99-42f0-a771-80344b272e37 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-18-generic N/A
 linux-backports-modules-3.2.0-18-generic N/A
 linux-firmware 1.71
Tags: precise
Uname: Linux 3.2.0-18-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-01-18 (51 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/10/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MDU Ver. F.09
dmi.board.name: 30D8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 83.0E
dmi.chassis.asset.tag: CNU81901SP
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MDUVer.F.09:bd01/10/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.09:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6720s
dmi.product.version: F.09
dmi.sys.vendor: Hewlett-Packard

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/949727/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[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 949727

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.

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[Timur Elzhov (indexless)]

apport information

[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.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/

[Timur Elzhov (indexless)]

Dear Joseph.

2012/3/12 Joseph Salisbury <email address hidden>

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".
>

I followed your instructions and found that unfortunately it is not yet
fixed in linux-image-3.3.0-030300rc7-generic package, so I confirmed this.
However it's not quite clear, should I re-run apport-collect to send the
environment information when kernel 3.3.0 is running?

Thank you for your work.

Timur.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get 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.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

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

[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 at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

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

[penalvch (penalvch)]

Timur Elzhov, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) 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.12

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.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]