[HP Compaq 6005 Pro] Suspend does not resume

Bug #759213 reported by Marc Legris
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Canonical Kernel Team
Lucid
Invalid
Medium
Unassigned
Natty
Invalid
Medium
Unassigned
Oneiric
Invalid
Medium
Canonical Kernel Team

Bug Description

Resuming this system from suspend only shows a blank screen, rather then returning to the desktop.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1432 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf0300000 irq 11'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,103c3047,00100101'
   Controls : 19
   Simple ctrls : 11
Date: Tue Apr 12 17:27:43 2011
HibernationDevice: RESUME=UUID=938ca224-d6b8-44c0-82ed-0c15d5af6e3c
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110329)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=069df1e8-a920-4d04-84bd-911cfaad7eee ro quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.11
dmi.board.asset.tag: WML3020081
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: WML3020081
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Ara Pulido (ara) wrote :

Can you guys take a look at this one, please?

tags: added: blocks-hwcert
Changed in linux (Ubuntu):
assignee: nobody → Canonical Platform QA Team (canonical-platform-qa)
importance: Undecided → Medium
tags: removed: regression-potiental
Revision history for this message
Brian Murray (brian-murray) wrote :

Assigning to the kernel team to look at - the CurrentDmesg attachment seems to have a lot of good debug information in it.

[ 0.034085] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20110112/dsfield-143)
[ 0.034090] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node ee025630), AE_ALREADY_EXISTS (20110112/psparse-536)
[ 0.034096] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
[ 0.034100] ACPI Warning: For \_SB_.PCI0._OSC: Parameter count mismatch - ASL declared 5, ACPI requires 4 (20110112/nspredef-352)
[ 0.034104] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])

[ 0.949229] calling late_resume_init+0x0/0x190 @ 1
[ 0.949231] Magic number: 7:491:449

Changed in linux (Ubuntu):
assignee: Canonical Platform QA Team (canonical-platform-qa) → Canonical Kernel Team (canonical-kernel-team)
tags: removed: needs-upstream-testing
Revision history for this message
Ara Pulido (ara) wrote :

This should be tried to be fixed in a SRU

Brad Figg (brad-figg)
Changed in linux (Ubuntu Natty):
status: New → Confirmed
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Seth Forshee (sforshee) wrote :

Marc, it looks like the CurrentDmesg.txt shows a suspend/resume cycle. I take it then that the system is still responsive after resume, it's just that the display isn't working? If so, can you capture dmesg again after resume when booted with the kernel parameter drm.debug=0xe?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Seth, booted the system with the added kernel parameter, suspended the system, and then rebooted (with kernel param) to desktop.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Seth Forshee (sforshee) wrote :

I don't see a suspend in the dmesg you attached. So the machine was really rebooted after suspend, not resumed?

Hrm, I looked at CurrentDmesg.txt again and what's actually in there is a failed suspend, not a successful suspend/resume. So is the system locked hard when you try to resume it, or is it still responsive (i.e. you can still log into the system over ssh)? If you can get in via ssh, please use this to capture dmesg after resume, before rebooting.

If it's completely unresponsive after resume, try the pm_trace steps from https://wiki.ubuntu.com/DebuggingKernelSuspend. If that doesn't work there's something new we can try, it just takes a little bit of effort to get set up.

Changed in linux (Ubuntu Natty):
status: Confirmed → Incomplete
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Reinstalled 11.04 and now I'm not seeing this issue. Instead it simply doesn't suspend, just seems to logout the user.

Revision history for this message
Ara Pulido (ara) wrote :

Marc, can you try to install all the updates, try to suspend, and attach the dmesg, please?

Chris Van Hoof (vanhoof)
Changed in linux (Ubuntu Natty):
assignee: nobody → Marc Legris (maaarc)
importance: Undecided → Medium
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Ara, reinstalled 11.04 and now suspend will actually suspend and not log off the user with -updates. Trying to use '"sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"' to retrieve more debugging info does not result in the machine actually suspending.

Changed in linux (Ubuntu Natty):
status: Incomplete → Confirmed
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Issue is also present in the A3 image of oneiric

Revision history for this message
Seth Forshee (sforshee) wrote :

Marc, do you still see this message after a failed suspend?

  legacy_suspend(): pnp_bus_suspend+0x0/0x90 returns 28

If so we can probably add a little more debugging to help narrow down which device is failing to suspend.

Ara Pulido (ara)
tags: added: oneiric
Revision history for this message
Marc Legris (maaarc-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

Seth, I do not see that message on the screen or in any of the logs.

Revision history for this message
Zack Evans (zevans23) wrote :

I have had this issue since karmic; still here in oneiric. I think there's some sort of race condition, because SOMETIMES it will come back and allow me to unlock the X session and THEN lock; other times it comes back to a blank screen.

Attached my kern.log from just after filesystems were mounted this morning until the point I power cycled now.

Revision history for this message
Jonathan Allard (joallard) wrote :

This bug affects me too on a Lenovo ThinkPad W520. Sometimes the unlock screen comes back, sometimes it doesn't. I just had to reboot. What would be a temporary fix to bring it back?

Changed in linux (Ubuntu Natty):
assignee: Marc Legris (maaarc) → nobody
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Fails for 11.10

Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Attempting an unbind for device ID pnp/00:09 help system go to suspend state, but never resumes.

Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Fails for 10.0.4.1 onward.

Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Issue is still present with 12.04 precise.

Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Failure is present with quantal, kernel version 3.4.0-3 #8

Jeff Lane  (bladernr)
tags: added: precise quantal
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernels, as well as the latest Quantal kernel?

The latest upstream kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/

The latest Quantal kernel can be downloaded from(Arch specific links are under "Builds"):
https://launchpad.net/ubuntu/+source/linux/3.4.0-3.8

Please install both the linux-image and linux-image-extra .deb packages.

Thanks in advance

tags: added: kernel-da-key qa-kernel-lts-testing
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Issue is still present in quantal rc2 kerneL: 3.5

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Suspend error from 12.04:

00020 summary
00021 summary 0 passed, 0 failed, 0 warnings, 1 aborted, 0 skipped, 0 info only.
00022 summary
00023 summary Test Failure Summary
00024 summary ====================
00025 summary
00026 summary Critical failures: NONE
00027 summary
00028 summary High failures: NONE
00029 summary
00030 summary Medium failures: NONE
00031 summary
00032 summary Low failures: NONE
00033 summary
00034 summary Other failures: NONE
00035 summary
00036 summary Test |Pass |Fail |Abort|Warn |Skip |Info |
00037 summary ---------------+-----+-----+-----+-----+-----+-----+
00038 summary s3 | | | 1| | | |
00039 summary ---------------+-----+-----+-----+-----+-----+-----+
00040 summary Total: | 0| 0| 1| 0| 0| 0|
00041 summary ---------------+-----+-----+-----+-----+-----+-----+
00001 fwts Results generated by fwts: Version V0.24.21 (Fri Mar 9 15:10:20 CST 2012).
00002 fwts
00003 fwts Some of this work - Copyright (c) 1999 - 2010, Intel Corp. All rights
00004 fwts reserved.
00005 fwts Some of this work - Copyright (c) 2010 - 2011, Canonical.
00006 fwts
00007 fwts This test run on 21/06/12 at 11:23:52 on host Linux 201011-6697
00008 fwts 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64.
00009 fwts
00010 fwts Running tests: s3.

Revision history for this message
Jeff Marcom (jeffmarcom) wrote :

Pressing the power button does not resume suspend. Machine must be completely dc power cycled.

Changed in linux (Ubuntu Lucid):
importance: Undecided → Medium
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
status: New → Triaged
Changed in linux (Ubuntu Lucid):
status: New → Confirmed
dino99 (9d9)
Changed in linux (Ubuntu Natty):
status: Confirmed → Invalid
Changed in linux (Ubuntu Oneiric):
status: Confirmed → Invalid
tags: removed: natty oneiric
Revision history for this message
Jonathan Allard (joallard) wrote :

Haven't seen that problem in a while since Raring (& Quantal?)

Changed in linux (Ubuntu Precise):
status: Triaged → Invalid
Changed in linux (Ubuntu Quantal):
status: Triaged → Invalid
Changed in linux (Ubuntu Precise):
status: Invalid → Incomplete
Changed in linux (Ubuntu Quantal):
status: Invalid → Incomplete
Jeff Marcom (jeffmarcom)
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Quantal):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Lucid Desktop EOL.

Changed in linux (Ubuntu Lucid):
status: Confirmed → Invalid
no longer affects: linux (Ubuntu Quantal)
no longer affects: linux (Ubuntu Precise)
Revision history for this message
penalvch (penalvch) wrote :
Changed in linux (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.