Fails to suspend on latest precise kernel

[Joe Barnett]

On latest few precise kernels, my HP envy 15 laptop fails to suspend. Screen goes black, volume is muted, and then hangs there.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-19-generic 3.2.0-19.30
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: jbarnett 2500 F.... pulseaudio
 /dev/snd/controlC1: jbarnett 2500 F.... pulseaudio
 /dev/snd/controlC0: jbarnett 2500 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4200000 irq 55'
   Mixer name : 'IDT 92HD75B2X5'
   Components : 'HDA:111d7608,103c1522,00100202'
   Controls : 16
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd4120000 irq 56'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card2.Amixer.info:
 Card hw:2 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-0000:00:1d.0-1.2.2,'
   Mixer name : 'USB Mixer'
   Components : 'USB0d8c:0105'
   Controls : 9
   Simple ctrls : 6
Date: Tue Mar 20 08:29:46 2012
HibernationDevice: RESUME=UUID=6a792c43-ea80-4425-961e-ccde894552ed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
MachineType: Hewlett-Packard HP ENVY 15 Notebook PC
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic root=UUID=639dc488-e095-42a4-8c1f-ffb1a9299e1c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-19-generic N/A
 linux-backports-modules-3.2.0-19-generic N/A
 linux-firmware 1.71
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-03-06 (14 days ago)
WifiSyslog:
 Mar 20 08:29:35 taplop NetworkManager[1384]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
 Mar 20 08:29:35 taplop NetworkManager[1384]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
 Mar 20 08:29:52 taplop kernel: [ 3110.747418] type=1400 audit(1332257392.774:36): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/telepathy-*" name="/usr/local/share/glib-2.0/schemas/gschemas.compiled" pid=6919 comm="telepathy-idle" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
 Mar 20 08:29:52 taplop kernel: [ 3110.780998] type=1400 audit(1332257392.806:37): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/telepathy-*" name="/usr/local/share/glib-2.0/schemas/gschemas.compiled" pid=6917 comm="telepathy-gabbl" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
dmi.bios.date: 04/23/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1522
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 36.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd04/23/2010:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr048F110000241920001530000:rvnHewlett-Packard:rn1522:rvr36.34:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP ENVY 15 Notebook PC
dmi.product.version: 048F110000241920001530000
dmi.sys.vendor: Hewlett-Packard

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Joe Barnett (thejoe)]

Yes, was definitely working sometime last week with one of the 3.2.0-18 kernels, but not sure of exact kernel where it broke (broken now with latest 3.2.0-18 as well as with 3.2.0-19). Not sure where older kernel packages are hosted to try to find one that works?

[Joseph Salisbury (jsalisbury)]

All of the precise kernels are available in Launchpad[0]. Can you test the 3.2.0-18.28[1] and the 3.2.0-18.29[2] kernels? It would be great to know what kernel introduced this bug, so we can bisect to find the offending commit.

[0] https://launchpad.net/ubuntu/precise/+source/linux
[1] https://launchpad.net/ubuntu/+source/linux/3.2.0-18.28/+build/3254748
[2] https://launchpad.net/ubuntu/+source/linux/3.2.0-18.29/+build/3272978

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

[Joe Barnett (thejoe)]

confirmed broken in 3.2.0-19.31, but working in 3.2.0-18.28

[Joseph Salisbury (jsalisbury)]

It would be great if we could run a kernel bisect, to identify the commit that caused this bug. Would you be able to test a few test kernels?

[Joe Barnett (thejoe)]

Yeah, I'll definitely test (for both this and bug 960315, which could potentially be related?). should be able to test at least one kernel a day.

[Joseph Salisbury (jsalisbury)]

It would be good to first identify which mainline kernel introduce the regression. The 3.2.0-18.28 kernel was based off of upstream 3.2.9. The 3.2.0-19.31 kernel was rebased to 3.2.10, 3.2.11 and 3.2.12.

Could you test the mainline 3.2.11[0] kernel and see if the bug was introduce in that version? If it was not, please test the 3.2.12[1] kernel. There was a build issue with the mainline 3.2.10 kernel, so there is not a prebuilt kernel to test that version.

Once we know what version introduced the bug, we can bisect to find the exact commit.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.11-precise/
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.12-precise/

[Joe Barnett (thejoe)]

just ran the following set of tests:

3.2.11: usb3 did not work, suspend worked
3.2.12: usb3 and suspend worked
3.2.0-18.28: usb3 and suspend worked
3.2.0-19.31: usb3 and suspend worked, but definitely did not work in previous tests!?

... so not sure if its related to a specific change, or if there's some somewhat random behavior in code shared by all these kernels?

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

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)]

It looks like you reported the bug in 3.2.0-19.30, but you are now running 3.2.0-19.31? This bug may have been fixed in 3.2.0-19.31.

Can you install the latest kernel, which is: 3.2.0-20.31? If the bug is fixed in that kernel, please mark the bug as "Fix Released".

Thanks in advance

[Joe Barnett (thejoe)]

confirmed working on 3.2.0-20-generic #33-Ubuntu

[Joost Van Durme (joostvandurme)]

I can add that this bug is back in 3.2.0-34. When I revert to 3.2.0-33, it works.
I have a Lenovo Thinkpad with ATI HD radeon card running latest Precise.

[Jason Kern (jaskerx)]

https://bugs.launchpad.net/ubuntu/+source/v86d/+bug/1080530