[MacBookAir5,1] After suspend, the screen gets corrupted

[Saverio Miroddi]

After I resume from suspend, the screen gets corrupted, specifically, area of the screen don't refresh, for example, the cursor doesn't blink, or some tabs of my editor don't dis/appear.

I can reproduce it almost always; I can work the problem around by switching to another terminal and back.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: saverio 2043 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Jun 18 17:15:09 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-10 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
MachineType: Apple Inc. MacBookAir5,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=28e3abb7-be92-4b4d-89ee-80413ed880eb ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-66F35F19FE2A0D05
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir5,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-66F35F19FE2A0D05
dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
dmi.product.name: MacBookAir5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

[Saverio Miroddi (64kramsystem)]

I will try it again in a couple of weeks; after what I believe is a recent kernel update, it stopped happening.

[Saverio Miroddi (64kramsystem)]

I'm not able to reproduce it anymore. It used to happen very frequently, then it stopped. It may be related to a kernel update.