MacBook Pro: very slow resume from S3 suspend-to-ram

Bug #490742 reported by Alexey Spiridonov
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
Mactel Support
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

I tried:
  User switching menu -> Suspend
  sudo /etc/acpi/sleep.sh force
  echo mem | sudo tee -a /sys/power/state
In all of these cases, it takes over 20 seconds to wake up the devices. I tried removing a couple of modules that seemed to be possible culprits, but that did not help. At this point I don't know how to debug this further.

This is a regression, since resume was quite zippy in 9.04.

Help?

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lesha 1751 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xdf480000 irq 21'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,106b4000,00100103'
   Controls : 36
   Simple ctrls : 20
Date: Tue Dec 1 01:08:44 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=7fc14978-2608-4a11-8dc9-dbda0c94df9c
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Apple Inc. MacBookPro5,1
NonfreeKernelModules: wl nvidia
Package: linux-image (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=cbb3b5a0-7470-40a4-977b-fc110c9d4919 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-15-generic N/A
 linux-firmware 1.25
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux-meta
Uname: Linux 2.6.31-15-generic x86_64
dmi.bios.date: 02/03/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP51.88Z.007E.B00.0902031928
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F42D86A9
dmi.board.vendor: Apple Inc.
dmi.board.version: Proto
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42D86A9
dmi.modalias: dmi:bvnAppleInc.:bvrMBP51.88Z.007E.B00.0902031928:bd02/03/09:svnAppleInc.:pnMacBookPro5,1:pvr1.0:rvnAppleInc.:rnMac-F42D86A9:rvrProto:cvnAppleInc.:ct8:cvrMac-F42D86A9:
dmi.product.name: MacBookPro5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Alexey Spiridonov (snarkmaster) wrote :
Revision history for this message
Alexey Spiridonov (snarkmaster) wrote :

This may or may not be a duplicate of this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/484183
It's unclear to me if it's an issue with the same driver, or a different driver, or how to track down the culprit.

Revision history for this message
Andy Whitcroft (apw) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and tag it kj-linux-meta, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
tags: added: kernel-karmic
Revision history for this message
Luke Symes (allsymes) wrote :

I have this problem with my MacBook 5,1. I am attaching dmesg output from a suspend/resume cycle.

Revision history for this message
Dawning (dawning) wrote :

Indeed, I have had this same issue too for quite some time on Macbook 4,1.

I find sometimes, I'll tell the machine to resume and it'll take up to 20seconds before the screen backlight even comes on. Then, I often start entering my password to unlock and the machine suspends again. I have to press the power button then to resume, finish entering my password and I'm back - the whole process taking in the neighborhood of 40 - 60 seconds.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Alexey,
    Have you tested this against Lucid? I'd be interested in the results.

Thanks!

-JFo

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Alexey Spiridonov (snarkmaster) wrote : Re: [Bug 490742] Re: MacBook Pro: very slow resume from S3 suspend-to-ram

Jeremy, would it be enough to try it in Alpha 2?

http://www.ubuntu.com/testing/lucid/alpha2#Download%20Alpha%202

I can do that next week.

On Wed, Feb 10, 2010 at 2:31 PM, Jeremy Foshee
<email address hidden> wrote:
> Alexey,
>    Have you tested this against Lucid? I'd be interested in the results.
>
> Thanks!
>
> -JFo
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Incomplete
>
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => Low
>
> --
> MacBook Pro: very slow resume from S3 suspend-to-ram
> https://bugs.launchpad.net/bugs/490742
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote : Re: [Bug 490742] Re: MacBook Pro: very slow resume from S3 suspend-to-ram

On Wed, 2010-02-10 at 23:52 +0000, Alexey Spiridonov wrote:
> Jeremy, would it be enough to try it in Alpha 2?
>
> http://www.ubuntu.com/testing/lucid/alpha2#Download%20Alpha%202
>
> I can do that next week.

That would be fine.

Thanks!

-JFo
>
> On Wed, Feb 10, 2010 at 2:31 PM, Jeremy Foshee
> <email address hidden> wrote:
> > Alexey,
> > Have you tested this against Lucid? I'd be interested in the results.
> >
> > Thanks!
> >
> > -JFo
> >
> > ** Changed in: linux (Ubuntu)
> > Status: New => Incomplete
> >
> > ** Changed in: linux (Ubuntu)
> > Importance: Undecided => Low
> >
> > --
> > MacBook Pro: very slow resume from S3 suspend-to-ram
> > https://bugs.launchpad.net/bugs/490742
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>

Revision history for this message
Luke Symes (allsymes) wrote :

I have Alpha 3, and have slow resume which then freezes. Since I have Ctrl-Alt-Backspace set to restart X I am able to eventually login again.

Revision history for this message
Chase Douglas (chasedouglas) wrote :

We have a new patch slated for Lucid that will time how long each device takes to resume (for example, nvidia binary graphics can take 5 s to resume, while other devices may take milliseconds). Unfortunately, the patch is not yet available in any lucid kernel (it will be in the next lucid kernel though). In the meantime, we have a test kernel ppa that we've been using to try out the .33 drm stack, which will also be included in lucid. The test kernels have the timing patch as well. Please test with the kernel and attach your dmesg after resuming. The kernel ppa can be found at: https://launchpad.net/~apw/+archive/red.

Thanks

Revision history for this message
Luke Symes (allsymes) wrote :

I tested the kernel from https://launchpad.net/~apw/+archive/red but on resume from suspend the screen went black and I heard the login window 'ready' sound. Nothing I did had any effect from then on, so I had to do a hard shutdown.

Revision history for this message
Chase Douglas (chasedouglas) wrote :

@Luke Symes:

There seems to be a bug with the latest nvidia drivers and that kernel. I am investigating it in bug 488720.

Revision history for this message
Luke Symes (allsymes) wrote :

I was looking through my logs after resume, and found this section of my kern.log - it has a call trace.

Revision history for this message
Dawning (dawning) wrote :

Presently on Ubuntu 10.04 x64 Beta 2 (fully updated as of April 20th 2010), I find it takes my Macbook approximately 10 seconds to resume. While OSX remains a fair bit faster, I consider this to be fast enough.

Are others still having an issue with this?

Revision history for this message
parren (peter-arrenbrecht) wrote : Re: [Bug 490742] Re: MacBook Pro: very slow resume from S3 suspend-to-ram

> Presently on Ubuntu 10.04 x64 Beta 2 (fully updated as of April 20th
> 2010), I find it takes my Macbook approximately 10 seconds to resume.
> While OSX remains a fair bit faster, I consider this to be fast enough.

Same here.

Revision history for this message
Alexey Spiridonov (snarkmaster) wrote :

When I tried a Lucid alpha on my MacBook, it didn't even boot out of
the box, so I could not actually test this. Moreover, I'm getting rid
of the MacBook this week (not that Apple cares... :), so I won't get a
chance to test it again. However, it sounds kind-of-fixed.

~a

On Wed, Apr 21, 2010 at 9:09 AM, parren <email address hidden> wrote:
>> Presently on Ubuntu 10.04 x64 Beta 2 (fully updated as of April 20th
>> 2010), I find it takes my Macbook approximately 10 seconds to resume.
>> While OSX remains a fair bit faster, I consider this to be fast enough.
>
> Same here.
>
> --
> MacBook Pro: very slow resume from S3 suspend-to-ram
> https://bugs.launchpad.net/bugs/490742
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Crazor (crazor) wrote :

For me, it still takes about 20+ seconds to resume, i.e. before the backlight comes on again. Attached is a snippet of my dmesg, showing one sleep cycle. I'm on kernel 2.6.32-24...

Revision history for this message
Dawning (dawning) wrote :

Yeah, I find that the resume time varies. Some times I find myself toying with the screen brightness keys in order to get my backlight going again from a suspend.

I'd still say my resume times average about 10s though. It feels kinda long compared to OSX, but I think it's tolerable. But, if someone hates it enough, they can always figure out a great fix. I'm sure many people out there would give props for that.

Revision history for this message
Crazor (crazor) wrote :

This is fixed in Maverick. Resume takes about 10 seconds again on my MB5,1.

Revision history for this message
Luke Symes (allsymes) wrote :

I had 10 second resume on Maverick with my MacBook 5,1 as well. However, I have gotten ~5 second resume as well as instant wireless connection by editing this file: gksu gedit /usr/lib/pm-utils/sleep.d/55NetworkManager
and changing the bottom section thus (commenting out suspend and resume of NetworkManager):

case "$1" in
 hibernate|suspend)
  #suspend_nm
  ;;
 thaw|resume)
  #resume_nm
  ;;
 *) exit $NA
  ;;
esac

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
Damien Buhl (damien-buhl) wrote :
Download full text (3.3 KiB)

I've the issue also on a MacBookPro 11,1. It takes exactly 34,2 seconds for the system to wakeup.

Strangely dmesg says the wakeup started on second 1864 and ended on 1869 :

[ 1864.618554] smpboot: CPU 7 is now offline
[ 1864.636283] ACPI: Low-level resume complete
[ 1864.636333] PM: Restoring platform NVS memory
[ 1864.636769] Enabling non-boot CPUs ...
[ 1864.636816] x86: Booting SMP configuration:
[ 1864.636817] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 1864.656612] kvm: enabling virtualization on CPU1
[ 1864.659865] CPU1 is up
[ 1864.659887] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 1864.679312] kvm: enabling virtualization on CPU2
[ 1864.682465] CPU2 is up
[ 1864.682487] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 1864.701491] kvm: enabling virtualization on CPU3
[ 1864.704665] CPU3 is up
[ 1864.704688] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 1864.721098] kvm: enabling virtualization on CPU4
[ 1864.723347] CPU4 is up
[ 1864.723358] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 1864.739362] kvm: enabling virtualization on CPU5
[ 1864.741830] CPU5 is up
[ 1864.741843] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 1864.757884] kvm: enabling virtualization on CPU6
[ 1864.760320] CPU6 is up
[ 1864.760332] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 1864.776361] kvm: enabling virtualization on CPU7
[ 1864.778802] CPU7 is up
[ 1864.858736] ACPI: Waking up from system sleep state S3
[ 1866.949677] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 1866.989763] PM: noirq resume of devices complete after 75.824 msecs
[ 1866.989821] [drm] Found 128MB of eLLC
[ 1866.989873] PM: early resume of devices complete after 0.090 msecs
[ 1866.989935] mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
[ 1866.990017] snd_hda_intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[ 1866.990127] snd_hda_intel 0000:00:03.0: irq 51 for MSI/MSI-X
[ 1867.062100] bcm5974: bad trackpad package, length: 8
[ 1867.092123] bcm5974: bad trackpad package, length: 8
[ 1867.094129] bcm5974: bad trackpad package, length: 8
[ 1867.096131] bcm5974: bad trackpad package, length: 8
[ 1867.098131] bcm5974: bad trackpad package, length: 8
[ 1867.100136] bcm5974: bad trackpad package, length: 8
[ 1867.102123] bcm5974: bad trackpad package, length: 8
[ 1867.104125] bcm5974: bad trackpad package, length: 8
[ 1867.134150] bcm5974: bad trackpad package, length: 8
[ 1867.136155] bcm5974: bad trackpad package, length: 8
[ 1867.333884] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1867.334115] ata1.00: unexpected _GTF length (8)
[ 1867.334490] ata1.00: unexpected _GTF length (8)
[ 1867.334574] ata1.00: configured for UDMA/133
[ 1867.334644] sd 1:0:0:0: [sda] Starting disk
[ 1868.230507] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 1869.959232] pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
[ 1869.959233] pciehp 0000:00:1c.0:pcie04: Failed to check link status
[ 1869.959619] PM: resume of devices complete after 2968.252 msecs
[ 1869.959784] PM: Finishing wakeup.
[ 1869.959785] Restarting tasks ... done.

So I've the impression that the bug may be before. I'm developer but never interested myself in the process of wakeup from RAM, is it something invol...

Read more...

Revision history for this message
Damien Buhl (damien-buhl) wrote :

I forgot to notice that this happens for me on :
Linux daminetreg-laptop 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

for Ubuntu 14.04.1 LTS

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.