[MacBookPro11,1] Suspend delayed because of some timeout issue

[Jussi Pakkanen]

As requested by apw, here is the bug report for suspend problem on Macbook retina. The issue is when activating suspend, the monitor turns off but the machine gets fully suspended only some time later. The actual start of suspend can be detected by they keyboard backlight going off. The attached logs were gathered in the following way:

- power cycle machine
- suspend
- wake up

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.15.0-2-generic 3.15.0-2.6
ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6
Uname: Linux 3.15.0-2-generic x86_64
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jpakkane 2097 F.... pulseaudio
 /dev/snd/controlC1: jpakkane 2097 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue May 27 15:54:53 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-22 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
MachineType: Apple Inc. MacBookPro11,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-2-generic root=UUID=aec3f04d-865c-4f0f-9872-d8953e94278d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.15.0-2-generic N/A
 linux-backports-modules-3.15.0-2-generic N/A
 linux-firmware 1.129
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-05-27 (0 days ago)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B07.1402121134
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,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)]

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

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

[Ate Douma (ate)]

I updated to mainline kernel v3.15-rc7 last week and still have the exact same issue.

[penalvch (penalvch)]

Ate Douma, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Jussi Pakkanen (jpakkane)]

I can't confirm if this is a regression as this machine is brand new and I only had trusty on it for a little while before upgrading. This issue may be related to uefi booting, as suspend seemed to work when booting in legacy bios mode (but that had a bug that made the system unbootable after a while).

Tested the upstream kernel specified and the bug seems to be in that one, too.

[penalvch (penalvch)]

Jussi Pakkanen, just to clarify, does the machine ultimately suspend with the default kernel? As well, how long would it take for it to suspend fully?

[Ate Douma (ate)]

Christopher,

I've created a separate bug report as you asked: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326365
and subscribed you to it as you indicated.

[Jussi Pakkanen (jpakkane)]

It does suspend after a minute or so.

[Jussi Pakkanen (jpakkane)]

Christopher, please don't override Joseph's importance evaluations. He is on the kernel team and knows better how to prioritise this bug.

[penalvch (penalvch)]

Jussi Pakkanen, given the new information you provided, this wouldn't even be considered a bug at all by many. Despite this, if you would be strongly desiring some sort of speed improvement, this is at best a Low as defined in https://wiki.ubuntu.com/Bugs/Importance .

[Reuben Thomas (rrt)]

This bug affects me. While the only problem I can directly trace to it is the delay in suspend, the system logs show a kernel oops, which may well indicate more serious underlying problems. (About ⅓ of the time when resuming, the system does not restart properly, e.g. the screen does not come back).

[Reuben Thomas (rrt)]

After experiencing a variety of nasty crashes, I stopped using suspend altogether (I tried upgrading to the utopic kernel, without benefit).

I've just tried using hibernate instead (note, this is disabled by default in Trusty, at least, but can easily be reenabled, e.g. see

http://ubuntuhandbook.org/index.php/2014/04/enable-hibernate-ubuntu-14-04/

) and it seems to work better: no pause before hibernate, and no kernel oops messages when I resume. Of course it's a bit slower, but it's an acceptable workaround until the bug is fixed.

[Reuben Thomas (rrt)]

Belay that, hibernate doesn't work reliably either. Back to looking for a fix for this bug…

[Erlenmayr (erlenmayr)]

Mid2014 Macbook Pro Retina here. Same issue, but the effect is even worse. It literally takes half a minute until suspend happens (you can see it by using pm-suspend instead of closing the lid, because you can watch keyboard backlight then). Problem is: Suspend sometimes fails and then the Mac wakes up again, even if lid is closed. And it does not make any efforts to go to sleep again.

This is CRITICAL, because if you close your laptop, put it in your back, then you will find out hours later that it was running all the time, with high risk to overheat damage. Of course nowadays the CPU will switch off before it burns, but it still was much too hot and may do damage to other parts of the computer like batteries and SSD.

I run 14.10 since October, and suspend worked fine for the first weeks, but for a few days now it wakes up very often when lid is closed.

[penalvch (penalvch)]

Erlenmayr, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs