Entire desktop becomes unresponsive after suspend/resume

[Jeff Lane ]

Doing certification testing on the Lenovo W510. During testing, I closed the lid and re-opened. The system suspended. I pressed the power button to resume and once it was awake again, the desktop was present but not usable.

I can move the pointer around freely, but the pointer never changes from the Text pointer to the arrow as it moves over various areas of hte desktop. Clicks to windows or launcher icons or panel icons do not produce any results. Right clicks do not produce any context menus.

There is no way out of this. Because CTRL-ALT-BKSP was decided to be such a bad thing, a user in this position has only two options. Reboot, or drop to a console and kill X.

I reset X by dropping to a console and sending it a SIGHUP.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Sat Apr 28 11:29:41 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 NVIDIA Corporation GT216 [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2145]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: LENOVO 438924U
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=a425aa11-d0cc-4beb-8488-ef04d7860898 ro quiet splash initcall_debug vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET74WW (1.34 )
dmi.board.name: 438924U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn438924U:pvrThinkPadW510:rvnLENOVO:rn438924U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 438924U
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2
---
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012
 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
DistUpgraded: Fresh install
DistroCodename: precise
DistroRelease: Ubuntu 12.04
DistroVariant: ubuntu
DkmsStatus: nvidia-current, 295.40, 3.2.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 NVIDIA Corporation GT216 [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2145]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
MachineType: LENOVO 438924U
NonfreeKernelModules: nvidia
Package: xorg 1:7.6+12ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=a425aa11-d0cc-4beb-8488-ef04d7860898 ro quiet splash initcall_debug vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Tags: precise ubuntu compiz-0.9
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 10/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET74WW (1.34 )
dmi.board.name: 438924U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn438924U:pvrThinkPadW510:rvnLENOVO:rn438924U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 438924U
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Jeff Lane  (bladernr)]

tagging as regression because this was not noticed with testing of previous Ubuntu versions.

Also, attached is a short video showing the desktop behaviour after resuming from suspend using the procedure listed above

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

apport information

[Jeff Lane  (bladernr)]

Update... I installed nvidia_current via jockey and this problem went away. It appears this is specific to running Nouveau.

[Jeff Lane  (bladernr)]

moved this to the nouveau package and removed the blocker tags as I have a workaround

[Jeff Lane  (bladernr)]

I've also noticed this on other Lenovo machines like the Edge 13 (7450).

[Jeff Lane  (bladernr)]

Noticed this on multiple Lenovo systems and some Dells too. Steps to recreate:

Boot precise.
Do some work for a while (maybe 15 minutes maybe longer)
close the lid
open the lid
when system resumes, the desktop may be frozen...

This doesn't happen every time I close the lid, but seems to occur after the systems been running and working for a while. The desktop appears frozen. There is still mouse pointer movement, but you'll note that the cursor doesn't change as it moves across various types of windows, clicks do nothing to icons, buttons, or whatever. Right click produces no context menus, no tooltips appear on launcher icons.

[Jeff Lane  (bladernr)]

Also, it's not nVidia dependent as first thought, as this occurs on systems without nVidia cards installed. The only fix for this seems to be rebooting, since CTRL-Alt-Bksp is disabled by default now. (or sending a sighup to X, but who knows to do that?)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[tomsecret (tomsecret-msn)]

Hi, your description of the suspend/resume bug fits my experience exactly. This wasn't an issue until the last week, and I don't really know what has broken suspend/resume. As described here the bug is only encountered after some of the suspend/resumes, I'd say that it happens on less than 20% of resumes. During testing to find the cause of the bug I've also seen it straight after booting i.e. if I suspend the system before doing any other work. I have an asus ul30vt running ubuntu 12.04 lts (32-bit) and I use bumblebee to disable the nvidia card (G210m) on my system. The only ways to 'recover' after this happens is either to shutdown the system, or go to console (ctrl+alt+f1) and 'sudo killall Xorg' - but then of course my X session is lost.

[tomsecret (tomsecret-msn)]

I'm actually not sure the bug I experience is entirely the same, as the mouse pointer does change when I move around the screen, i.e. if I suspended from a session where my internet browser was the active application, I see the mouse pointer changing from the arrow into the text cursor over text boxes, or hand when over links. If I press a link the screen stays the same, but I think the computer responds, as there are sign of the cpu working, and the mouse pointer changes appereance when moving around the desktop, as if a new web page was opened.

Anyways, I've found a "fix" for the problem: If I enable the option to lock the desktop on resume from suspend, then it always works after I enter the password, whereas if I go straight to the desktop (lock disabled) my system sometimes becomes unresponsive.

[tomsecret (tomsecret-msn)]

Nevermind the "fix" I mentioned in the previous post, I've now experienced two crashes when enabling the desktop lock from resume.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[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.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc2-quantal/

[Joseph Salisbury (jsalisbury)]

@Jeff, do you happen to know when this regression was introduced? Was it always in Precise, or was it introduced in a specific update?

[Brendan Donegan (brendan-donegan)]

Greg or Jeff, can you test the mainline kernel as requested by Joseph?

[Jeff Marcom (jeffmarcom)]

@Joseph,

We do base LTS testing. You'll see Jeff Lane's original comment included the kernel version tested:
Ubuntu 3.2.0-23.36-generic 3.2.14

[Jeff Marcom (jeffmarcom)]

@Joseph
To answer the question, the regression would have been introduced with the release of precise.

[Jeff Marcom (jeffmarcom)]

I have not been able to reproduce this with 3.5 -quantal rc3. However this issue seems to be intermittent at best, as I have not been able to reproduce in precise 3.2.0.23 either.

[Brendan Donegan (brendan-donegan)]

@Jeff - have you looked at https://bugs.launchpad.net/bugs/1012740? You might need to do suspend several times to get this to reproduce.

[Jeff Marcom (jeffmarcom)]

I'm re-running this now to verify via:
sudo fwts s3 --s3-multiple=100 -r results.log

[Jeff Marcom (jeffmarcom)]

I managed to reproduce the bad suspend behaviour (on 3.2.0.23) with an overnight run. Run failed to properly suspend and resume after only 12 times.

Kernel message output was display on screen at time of failure, mouse + keyboard were unresponsive:
kernel: [ 88.556310] watchdog: only one watchdog can use /dev/watchdog.
kernel: [ 88.556316] watchdog: error registering /dev/watchdog (err=-16).

Suspend failure:

00012 s3 S3 suspend/resume test.
00013 s3 -----------------------------------------------------------------------------
00014 s3 Test 1 of 1: S3 suspend/resume test.
00015 s3 S3 cycle 1 of 100
00016 s3 pm-suspend returned 0 after 38 seconds.
00017 s3 S3 cycle 2 of 100
00018 s3 pm-suspend returned 0 after 37 seconds.
00019 s3 S3 cycle 3 of 100
00020 s3 pm-suspend returned 0 after 37 seconds.
00021 s3 S3 cycle 4 of 100
00022 s3 pm-suspend returned 0 after 38 seconds.
00023 s3 S3 cycle 5 of 100
00024 s3 pm-suspend returned 0 after 37 seconds.
00025 s3 S3 cycle 6 of 100
00026 s3 pm-suspend returned 0 after 37 seconds.
00027 s3 S3 cycle 7 of 100
00028 s3 pm-suspend returned 0 after 37 seconds.
00029 s3 S3 cycle 8 of 100
00030 s3 pm-suspend returned 0 after 38 seconds.
00031 s3 S3 cycle 9 of 100
00032 s3 pm-suspend returned 0 after 38 seconds.
00033 s3 S3 cycle 10 of 100
00034 s3 pm-suspend returned 0 after 37 seconds.
00035 s3 S3 cycle 11 of 100
00036 s3 pm-suspend returned 0 after 37 seconds.
00037 s3 S3 cycle 12 of 100

[Jeff Marcom (jeffmarcom)]

Trying to reproduce on kernel version 3.5 now.

[Jeff Marcom (jeffmarcom)]

3.5 suspends and desktop is still usable.

However usb key is no longer mounted, and video is very shaky.

Video issue is introduced after 1 suspend, and can be reproduced.

Actual suspend does run for 250 loops.

00509 s3 S3 cycle 247 of 250
00510 s3 pm-suspend returned 0 after 38 seconds.
00511 s3 S3 cycle 248 of 250
00512 s3 pm-suspend returned 0 after 38 seconds.
00513 s3 S3 cycle 249 of 250
00514 s3 pm-suspend returned 0 after 38 seconds.
00515 s3 S3 cycle 250 of 250
00516 s3 pm-suspend returned 0 after 38 seconds.
00517 s3 Completed 250 S3 cycle(s)
00518 s3 PASSED: Test 1, No kernel log errors detected.
00519 s3 Found 1 PM related suspend issues.
00520 s3 PASSED: Test 1, No device errors detected.
00521 s3 PASSED: Test 1, No kernel oopses detected.
00522 s3 Found 1 errors and 0 oopses doing 250 suspend/resume cycle(s).
00523 s3
00524 s3 =============================================================================
00525 s3 3 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.
00526 s3 =============================================================================

00528 summary
00529 summary 3 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.
00530 summary
00531 summary Test Failure Summary
00532 summary ====================
00533 summary
00534 summary Critical failures: NONE
00535 summary
00536 summary High failures: NONE
00537 summary
00538 summary Medium failures: 1
00539 summary s3 test, at 1 log line: 307
00540 summary "Unexpected: S3 slept for 24 seconds, less than the expected 30 seconds."
00541 summary
00542 summary Low failures: NONE
00543 summary
00544 summary Other failures: NONE
00545 summary
00546 summary Test |Pass |Fail |Abort|Warn |Skip |Info |
00547 summary ---------------+-----+-----+-----+-----+-----+-----+
00548 summary s3 | 3| 1| | | | |
00549 summary ---------------+-----+-----+-----+-----+-----+-----+
00550 summary Total: | 3| 1| 0| 0| 0| 0|
00551 summary ---------------+-----+-----+-----+-----+-----+-----+

[Jeff Marcom (jeffmarcom)]

Installing proprietary nvidia driver does not aid with suspend. Video is still a little distorted.

[Joseph Salisbury (jsalisbury)]

So it appears this bug has been fixed upstream. We can perform a "Reverse bisect" to find the commit that fixed this. First we need to identify which upstream kernel version fixes this. We know that the bug exists in v3.2 and does not exist in v3.5-rc2. Can you test out v3.4 final, which is available at:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/

[Ara Pulido (ara)]

Marking the bug as Incomplete, waiting on testing on 3.4

[Ara Pulido (ara)]

Joseph, it does not seem like the bug is properly fixed upstream. The desktop is responsive, but the video does not work properly and usb key is no longer mounted

[Joseph Salisbury (jsalisbury)]

@Jeff,

I noticed you added the kernel-fixed-upstream tag in comment #45. However, it sounds like this bug still exists in v3.5? If so, 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

[Jeff Marcom (jeffmarcom)]

@Joseph,

Unfortunately it's an entirely different set to systems from the original issue (probably not related). The desktop is responsive despite the new issues presented. Which is why I marked as fixed in the newer kernel.

I'll likely open a new bug (if that's okay) on the separate issue, to avoid "crossing the streams."

[Joseph Salisbury (jsalisbury)]

@Jeff,

Yes, it would be great if you could open a new bug for the new set of systems. Are the original set of systems that exhibited this bug still available?

[Jeff Marcom (jeffmarcom)]

I apologise for the grammar. That note was meant to say :

Unfortunately it's an entirely different set of symptoms from the original issue

[Joseph Salisbury (jsalisbury)]

Would you say this bug is fixed in the upstream kernel from your tests? If so, we can perform a reverse bisect.

[Jeff Marcom (jeffmarcom)]

I would the *original* problem is fixed. We may need to do what you suggest.

[Joseph Salisbury (jsalisbury)]

Can you test some additional upstream kernels, so we can identify the version that introduced this regression? It would be good to test the following:

v3.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-oneiric/
v3.2-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc2-oneiric/

Thanks

[Ara Pulido (ara)]

Marking it as High, as it is affecting several systems

[Jeff Marcom (jeffmarcom)]

System fails to resume from suspend after a couple of cycles with 3.1.1. Attempting with 3.2-rc2 now.

[Jeff Marcom (jeffmarcom)]

So 3.2-rc2 presents a couple of interesting symptoms.

After I closed and re-opened the lid on the 6th time the system was at the unity login screen. After logging in and attempting a suspend a again the system fails to try and suspend all together. Closing the laptop lid for more than 5 minutes does not prove useful.

[Jeff Marcom (jeffmarcom)]

System is now unresponsive after the 15th attempt at suspend.

[Joseph Salisbury (jsalisbury)]

@Jeff,

Sorry for the confusion. We should be performing a "Reverse bisect" since this bug is fixed in the upstream kernel. What we need to do is identify the first upstream kernel version that makes his bug goes away, then perform the reverse bisect to find the exact commit.

Can you test the following kernels and report back which have and don't have the bug?

v3.3 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
v3.4 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/

And if possible, the latest mainline which is -rc6, just to confirm the bug is in fact fixed in the latest release:
v3.5-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/

[Jeff Marcom (jeffmarcom)]

Running 250 cycle suspend tests with version 3.3 right now. Desktop is still responsive at the moment.

[Jeff Marcom (jeffmarcom)]

System is still responsive after 150 suspend cycles. Moving onto 3.5-rc6.

[Joseph Salisbury (jsalisbury)]

Actually v3.5-rc7 is now available, if you can test that:

v3.5-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc7-quantal/

[Jeff Marcom (jeffmarcom)]

running with .3.5 rc7 now, and looks okay after 30 cycles. I'll retrieve the results in the morning as it's set up for a 250.

[Jeff Marcom (jeffmarcom)]

Okay, so suspend test is finished with rc7.

Results:

1 passed, 9 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.

Many of the failures were due to the following:
00154 s3 Network - iwconfig configurations differ, before:
00155 s3 wlan0 IEEE 802.11abgn ESSID:"ubuntu-cert-n-wpa"
00156 s3 Mode:Managed Frequency:2.412 GHz Access Point: C0:C1:C0:38:6C:55
00157 s3 versus after:
00158 s3 wlan0 IEEE 802.11abgn ESSID:"ubuntu-cert-bg-wpa"
00159 s3 Mode:Managed Frequency:2.462 GHz Access Point: C0:C1:C0:38:6D:C7

Which is not important. However one was the following:
00374 s3 FAILED [CRITICAL] KlogDisablingIRQ: Test 1, CRITICAL Kernel message: [
00375 s3 8535.858286] Disabling IRQ #16
00376 s3
00377 s3 ADVICE: The kernel detected an irq storm. This is most probably an IRQ routing
00378 s3 bug.

Which is probably a cause for concern. However, with all this said, the desktop/mouse/keyboard/graphics are all working after 250 cycles.

[Joseph Salisbury (jsalisbury)]

So per comment #61, it sounds like this bug is fixed in 3.3. We should next test some of the v3.3 release candidates. Can you test the following kernels and report back:

v3.3-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc1-precise/
v3.3-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc4-precise/

[Launchpad Janitor (janitor)]

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

[Jeff Lane  (bladernr)]

Jeff or Greg, could you look at this and try to move it along?

[Joseph Salisbury (jsalisbury)]

The next step would be to test the latest 3.2 stable kernel, which is available from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.37-precise/

[Launchpad Janitor (janitor)]

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

[Jeff Lane  (bladernr)]

Over a year and I couldn't get anyone to look at this further on the cert team, so closing it to get it out of my list of open bugs.

[joncamfield (jon-camfield)]

Of note, I am experiencing this same problem in 14.04, running 3.16 rc4 (moving up to rc7 today). The only error mentioned in the pm-suspend resume process is "Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory" when wpa-supplicant is being dragged out of bed.

[Greg (cebif)]

I also have the same bug with KDE 4.13.3 Plasma and kernel 3.13.0-39-generic. It is the KDE in Linux Mint 17 repositories which is based on Ubuntu 14.04.