[Apple Inc. MacBookPro10,1] suspend/resume failure [non-free: wl]

Bug #1193661 reported by Roland Fritz
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Saucy
Expired
Medium
Unassigned

Bug Description

as many have noted... runnimg ubuntu on a retina macbook has many issues... this specific bug prevents the mac from waking back up from suspended state after closing the lid. Also the screen brightness is not controllable.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.9.0-6-generic 3.9.0-6.14
ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: roland 1434 F.... pulseaudio
 /dev/snd/controlC0: roland 1434 F.... pulseaudio
Date: Sat Jun 22 12:46:28 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=90f54f23-810f-4c22-8b5b-015897e7bc6e
InstallationDate: Installed on 2013-06-21 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac (20130621)
InterpreterPath: /usr/bin/python3.3
MachineType: Apple Inc. MacBookPro10,1
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=59486b17-48bc-4fd8-a452-57a1fb6f2f08 ro acpi_backlight=vendor quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.9.0-6-generic N/A
 linux-backports-modules-3.9.0-6-generic N/A
 linux-firmware 1.109
SourcePackage: linux
Title: [Apple Inc. MacBookPro10,1] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B02.1208081132
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B02.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Roland Fritz (roland-fritz) wrote :
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
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 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.10-rc7-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Roland Fritz (roland-fritz) wrote :

I was able to test the upstream mainline kernel 3.10 as per the instructions... It did not resolve the bug.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Revision history for this message
Roland Fritz (roland-fritz) wrote :

This was a clean install. I was trying to successfully get any version of linux to be installed on my mac. I was able to install Ubuntu 12.04 but had issues with having to try and manually configure wifi (though I was successful). I read that 13.04 improved support for the rMBP and so I figured I would try to follow the upgrade path. I upgraded to 12.10 only to find that the graphics card wasn't supported by the driver (I couldn't boot properly). I then decided to try some instructions I found. I found a copy of 13.10 amd64+mac.iso and was able to build a live usb to install it. I decided to do a clean install to see if many of the issues had been fixed (as was reported by the guide I was reading). A lot of little things were fixed (wifi, sound, and graphics work out of the box). While I have seen 13.10 improve support for the rMBP 10,1 (especially more so than many of the other distros), it still has issues to be worked out. I do not believe there has been any regression to have taken place since as I understand it most people give up upon trying to install linux to dual boot with the mac operating system due to EFI and driver support. I am happy to see the progress that has been made though and will gladly assist with testing and reporting back to try and iron out and bugs.

tags: added: amd64+mac
Revision history for this message
Roland Fritz (roland-fritz) wrote :

found another bug report that seems related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1084960

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.10-rc7 needs-upstream-testing
removed: kernel-bug-exists-upstream
penalvch (penalvch)
tags: added: regression-potential
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Please test latest development kernel (3.11.0-7.14)

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.11.0-7.14
Revision history for this message
Brian L. Troutwine (l-brian) wrote :

I continue to experience something similar on a Macbook 9,1 Retina. I'm unsure if this should be a separate bug but the symptoms are exactly the same.

Kernel version: Ubuntu 3.11.0-8.15-generic 3.11.1

Revision history for this message
Brian L. Troutwine (l-brian) wrote :

Ah, apologies. I see this is a more correct version of the bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1186818

My apologies. I'm new at reporting issues to this project.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu Saucy):
status: Incomplete → Expired
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.