[System76, Inc. Gazelle Professional] suspend/resume failure

[Robert Bruce Park]

Just closed the lid, when I reopened it I found that it had booted to a fresh lightdm login screen rather than having woken from suspend properly. Also 10,000 apport dialogs opened when I first logged in.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-2-generic 3.10.0-2.10
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: robru 2148 F.... pulseaudio
 /dev/snd/pcmC0D0p: robru 2148 F...m pulseaudio
Date: Tue Jul 9 18:29:34 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=a52a296f-88da-4d7f-8dda-83364796345c
InstallationDate: Installed on 2012-09-14 (298 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
InterpreterPath: /usr/bin/python3.3
MachineType: System76, Inc. Gazelle Professional
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=d2cf421f-df2e-4256-98d6-3fc77444bbde ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-2-generic N/A
 linux-backports-modules-3.10.0-2-generic N/A
 linux-firmware 1.110
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [System76, Inc. Gazelle Professional] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-05-08 (62 days ago)
UserGroups:

dmi.bios.date: 05/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp7
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp7
dmi.sys.vendor: System76, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this just start happening after a recent update? Do you know if there was an earlier Saucy kernel that did not exhibit this bug?

[Robert Bruce Park (robru)]

Tough call. This is definitely the first time I've experienced it, but I don't suspend very often at all so it's hard to say which is the last known good kernel.

Also, I recall having 16 days uptime when this happened, although I routinely update my system. I don't suppose this issue could be caused by having updated the kernel on disk but still having an older version running in memory?

[Robert Bruce Park (robru)]

Forgot to mention, the last time that I can distinctly remember suspending this machine was when I had it with me at UDS Copenhagen, but of course I would have been running Quantal at the time. No issues then, for sure.

More recently I was at the Oakland sprint last May, and while I distinctly remember *NOT* experiencing any problems there, I cannot clearly remember whether or not I ever actually suspended or not. That would have been on with the most updated Saucy kernel for sure.

[Robert Bruce Park (robru)]

Just did a couple suspend/resume cycles and can't seem to reproduce this...

[Joseph Salisbury (jsalisbury)]

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 are approaching release and would like to confirm if this bug is still present. Please test again with the latest development 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.

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

[Launchpad Janitor (janitor)]

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