[System76, Inc. Galago UltraPro] suspend/resume failure

[zach parton]

Happens at start-up almost every time I log on.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.15.0-6-generic 3.15.0-6.11
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.3-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: phoenix4 3089 F.... pulseaudio
 /dev/snd/controlC0: phoenix4 3089 F.... pulseaudio
CurrentDmesg:
 [ 1087.497888] init: anacron main process (1642) killed by TERM signal
 [ 3120.013677] [UFW BLOCK] IN=wlan0 OUT= MAC=80:56:f2:ad:a7:c1:ac:5d:10:13:95:99:08:00 SRC=74.125.21.84 DST=192.168.1.65 LEN=40 TOS=0x00 PREC=0x00 TTL=40 ID=31004 PROTO=TCP SPT=443 DPT=60870 WINDOW=0 RES=0x00 RST URGP=0
 [ 3121.016154] [UFW BLOCK] IN=wlan0 OUT= MAC=80:56:f2:ad:a7:c1:ac:5d:10:13:95:99:08:00 SRC=173.194.37.66 DST=192.168.1.65 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=26367 PROTO=TCP SPT=443 DPT=34703 WINDOW=0 RES=0x00 RST URGP=0
 [ 5176.220467] [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:28:e0:2c:dd:04:da:08:00 SRC=192.168.1.72 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=36042 PROTO=2
Date: Thu Jun 19 20:52:47 2014
DuplicateSignature: suspend/resume:System76, Inc. Galago UltraPro:4.6.5
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2014-06-08 (11 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140522)
InterpreterPath: /usr/bin/python3.4
MachineType: System76, Inc. Galago UltraPro
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.15.0-6-generic N/A
 linux-backports-modules-3.15.0-6-generic N/A
 linux-firmware 1.131
SourcePackage: linux
Title: [System76, Inc. Galago UltraPro] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago UltraPro
dmi.board.vendor: System76, Inc.
dmi.board.version: galu1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc,
dmi.chassis.version: galu1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
dmi.product.name: Galago UltraPro
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

dkz, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) 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-3.16-rc1

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

[Jason Gerard DeRose (jderose)]

Is this still happening with the 3.16.0-18-generic kernel (current Utopic kernel)?

[Colan Schwartz (colan)]

Not sure. I'm still on Trusty. Zach?

[zach parton (partonzm)]

I ended up back on the LTS as well. I haven't seen the message recently.

I checked my logs and everything is fine on 14.04. I plan to update to the latest kernel by the end of the week to test.

Will inform.

[Jason Gerard DeRose (jderose)]

Thanks for the feedback!

System76 has been doing extensive testing internally on Utopic since the 3.16 kernel landed. Thus far we haven't encountered this resume from suspend issue, but we'll keep a eye out for it!

[penalvch (penalvch)]

zach parton, please reopen if this is still reproducible for you in 14.10.

Colan Schwartz, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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