[Apple Inc. MacBookPro11,2] suspend/resume failure [non-free: wl]

Bug #1420129 reported by Morten F. Rasmussen
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I closed the lid of the laptop, put the laptop in its case/sleeve and went for an appointment. 2 hours later I took it out again and it was burning hot to the touch! The fans were also running on full speed, but that doesn't help much in the sleeve (luckily the laptop didn't die).
When I close the lid, it looks like the laptop hipernates, but apparently it doesn't.
Also it will not wake up again. I just get a black screen. It will very shortly (<0.5sec) show the log in screen and then show a black screen again.
If there is anything I can do, just let me know -I'm trying out 15.04 to help.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-12-generic 3.18.0-12.13
ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
Uname: Linux 3.18.0-12-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mf 2205 F.... pulseaudio
 /dev/snd/controlC0: mf 2205 F.... pulseaudio
Date: Mon Feb 9 22:01:34 2015
DuplicateSignature: suspend/resume:Apple Inc. MacBookPro11,2:MBP112.88Z.0138.B14.1501071031
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2015-02-02 (7 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150119)
InterpreterPath: /usr/bin/python3.4
MachineType: Apple Inc. MacBookPro11,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed root=UUID=2e543fc7-3cde-472f-a2ba-529d7e91ac90 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.18.0-12-generic N/A
 linux-backports-modules-3.18.0-12-generic N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [Apple Inc. MacBookPro11,2] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/07/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B14.1501071031
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-3CBD00234E554E41
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-3CBD00234E554E41
dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41:
dmi.product.name: MacBookPro11,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Morten F. Rasmussen (mofi) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0].

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.19-vivid/

Changed in linux (Ubuntu):
importance: Critical → Medium
status: Confirmed → Incomplete
Revision history for this message
Morten F. Rasmussen (mofi) wrote :

Sorry for the delay..
I just tested a bit more. Closing the lid actually doesn't turn of the light in the screen/monitor and the fans are still runing.

The next test was with open lid and then waiting 5min until it should suspend (as set via System Settings -> Power).
I was streaming music to make it easier to tell when it would start to suspend.
Result:
After 1min the screen turns black as it should.
After 5min the music stops for 2-5sec and then both the screen turns on and the music starts again
After 6min the screen turns black again.
After 10min the music stops for 2-5sec and then both the screen turns on and the music starts again
Then I stopped the test.

Clicking "Suspend" in the top-left menu works perfectly. Both Suspending and waking up again. On an earlier kernel it didn't want wake up again, but now that part works :)

I will test the 3.19.0 kernel now and see if it makes any difference..

Revision history for this message
Morten F. Rasmussen (mofi) wrote :

The upstream kernel didn't solve the problem.

The 5min time out had exactly the same behavior.
I was this time playing music while closing the lid. The music was never interrupted and the light never went out of the screen. The kernel knows the lid has been closed:
[ 51.675694] systemd-logind[1376]: Lid closed.
[ 91.193062] systemd-logind[1376]: Lid opened.

I noticed now, that clicking on "Suspend" doesn't work perfect (as I mistakenly wrote in the last post):
it immediately wakes up / resumes (I will boot the ubuntu-kernel and test if it has the same behavior).
This is also seen from the dmesg output:
[ 238.968218] PM: Preparing system for mem sleep
[ 238.968347] Freezing user space processes ... (elapsed 0.001 seconds) done.
[...]
[ 239.456134] smpboot: CPU 6 is now offline
[ 239.456413] intel_pstate CPU 7 exiting
[ 239.456490] Broke affinity for irq 31
[ 239.456492] Broke affinity for irq 34
[ 239.457497] kvm: disabling virtualization on CPU7
[ 239.457499] smpboot: CPU 7 is now offline
[ 239.474888] ACPI: Low-level resume complete
[ 239.474936] PM: Restoring platform NVS memory
[ 239.475324] Enabling non-boot CPUs ...
[ 239.475381] x86: Booting SMP configuration:
[ 239.475382] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 239.495644] kvm: enabling virtualization on CPU1
[ 239.536172] CPU1 is up
[ 239.547781] smpboot: Booting Node 0 Processor 2 APIC 0x4

Revision history for this message
Morten F. Rasmussen (mofi) wrote :

I can now confirm there is no difference in behavior between the two kernels.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.