suspend/resume brooken on macbook pro hardware 11.2

[kenjo]

On ubuntu 15.04 with kernel 3.19.0-16 its not possible to out of the box do a suspend.

if I disable XHC1 as wakeup source in /proc/acpi/wakeup it is now possible to suspend.

echo XHC1 >/proc/acpi/wakeup

But now resume is problematic. When resuming its possible to get just a black screen. Resume is actually working but the backlightis not turned on. but since ubuntu now has turned on the screenlock it is not possible to use the buttons that controls the backlight to get the screen readable again.

If I type my password in blindly (dont always work) I get back in the desktop and then I can use the keys that control the backlight and tus get a picture again.

This is not very user friendly.

1. we need some way to control the backlight also when the screen is locked, this is very important turning on tha lock manualy also prevent the backlight key from working.

2. when resuming something needs to turn on the backlight 100% . (it is done often, but sometimes it's black.)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-16-generic 3.19.0-16.16
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kenjo 1855 F.... pulseaudio
 /dev/snd/controlC1: kenjo 1855 F.... pulseaudio
Date: Wed May 6 13:28:23 2015
HibernationDevice: RESUME=UUID=761572ed-0a1f-4ea0-9e80-1b6ef6034e6e
InstallationDate: Installed on 2015-04-09 (26 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
 Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
 Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard / Trackpad (MacBook Retina)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro11,2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-16-generic N/A
 linux-backports-modules-3.19.0-16-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
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.

[Brad Figg (brad-figg)]

This change was made by a bot.

[kenjo (ken-kenjo)]

Turns out that even with the fix to turn off USB (XHC1) as a wakeup source the system can enter a state where suspend is not happening (we get woken directly ).

I only seen this once so far and I have no idea why. I did not have time to do any experiments at the time to try to figure out what was waking the system up.

[penalvch (penalvch)]

kenjo, 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

[penalvch (penalvch)]

Tony Houghton, if you are having an issue in Ubuntu, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Tony Houghton (h-realh)]

I use Ubuntu on some of my PCs, but at the moment I only have Debian (apart from OS X) on the Mac affected by this bug. I found this report by searching for the symptoms and thought it would help you to know that Debian is also affected so it's probably an upstream bug.