As of Ubuntu 16.04 display stays black after resume

[hobbes]

Computer: Macbook Pro Retina 2013 (core i5 with Intel HD Graphics)

Unexpected behavior: After resume, the display stays black. This behavior was not observed with Ubuntu versions up to 15.10, including 15.04 and 14.10.

Workaround: Switch to console (Ctrl-Alt-F1), then switch back to the graphical console (Crtl-Alt-F7). The login screen appears.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matthias 3133 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-09-25 (280 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Apple Inc. MacBookPro10,2
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed root=UUID=9ad64312-9c49-4271-ae5b-8307a12d617f ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
Tags: xenial
Uname: Linux 4.4.0-24-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-26 (66 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/13/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP102.88Z.0106.B0A.1509130955
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-AFD8A9D944EA4843
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-AFD8A9D944EA4843
dmi.modalias: dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B0A.1509130955:bd09/13/2015:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
dmi.product.name: MacBookPro10,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Paul White (paulw2u)]

According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate refiling against the kernel is best for now.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1596673

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[hobbes (hobbes-f)]

apport information

[penalvch (penalvch)]

hobbes, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel 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 issue 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 X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

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

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status 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.]