System does not resume after suspend

[Jim Pivarski]

In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid is closed, but does not resume when the lid is opened. It's probably hardware specific (MacBook Pro running Trusty/14.04), but I saw that my hardware data was sent with this report.

I noticed the problem in 3.13.0-43 and installed linux-images backward until I found one that does not suffer from this problem. Suspend/resume works in 3.13.0-40 and previous versions and does not work in 3.13.0-41 and later versions, reproducibly (I rebooted with different kernel versions several times to be sure). Something was introduced in this version that breaks suspend/resume.

For now, I'm using 3.13.0-40, but I'm hoping this gets resolved so that I can keep up to date with kernel versions again. (Thanks!)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-41-generic 3.13.0-41.70
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pivarski 2310 F.... pulseaudio
 /dev/snd/controlC0: pivarski 2310 F.... pulseaudio
Date: Fri Dec 19 19:43:31 2014
HibernationDevice: RESUME=UUID=c3b7c7b4-008d-4753-b205-63ab65db36e7
InstallationDate: Installed on 2014-09-27 (83 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Apple Inc. MacBookPro6,2
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=e4ed6837-c7cd-42bf-8e63-e213f9b4681c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-40-generic N/A
 linux-backports-modules-3.13.0-40-generic N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/11
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Jim Pivarski, 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 (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 exactly shown as:
kernel-fixed-upstream-3.19-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.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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