Slow wake up after installing lion (Macbook Pro 2010)

I also had wake from sleep exceeding 10sec, I restarted into the recovery screen (hold option during restart) I then ran utilities>repair disk, then exited and restarted and now my wake from sleep is 2secs.

Hope this helps others.

Unfortunately none of the suggestions helped me, all three of my disks are fine and come back with no errors according to Disk Utility. Yet, for some reason, it's still doing the same thing. This morning, for instance, I woke my computer and immediately tried to open my normal three apps (Safari, Mail, and iCal). Even thought the Finder was responsive, the apps bounced for a good 30 seconds before opening and it was about a minute before my AirPort connected. Previously it took about 5 seconds to do all of those tasks. I'm not sure if it's waiting for my hard drives to spin up and everything or what, but I have no idea why my AP should take a minute to connect when it never has in the past.

Oh, and I did a fresh install of 10.7 so there shouldn't be any issues there.

I am having the same issue with an early 2009 17" MacBook Pro with Lion. I was starting to think it's related to my logic board but it seems software related based on everyones post. Apple please fix this!!

Experiencing same issue on Late 2009 MacBook. Snow Leopard would wake and apps would be launch-ready within 5 seconds. Lion consistently takes 30 seconds (or more) before apps (and even Wi-Fi) function properly. First noticed this when DVD Player kept crashing when I tried launching it immediately after flipping the lid.

i just want to put in my 2 cents and say I'm having the same issue. I have to wait at least 20seconds to wake each time from sleep with lion compared to the 3seconds i had to wait with SL.

I own a 13" macbook pro

I think it might have something todo with the time machine backup possibly...

please fix this apple!!

I think I just found a fix that might help others too (read below).

I've also been having slow and erratic wake up from sleep on my Lion-powered brand new Mid 2011 MB Air 13" (core i7 model) that I purchased less than a month ago. I've had the frozen mouse issue described earlier in this thread, with wake up times oscillating between 5 and 20 seconds. I've never experienced the need to force reboot the machine though like others report, so I am feeling a bit lucky.

However, this is definitely far from the sweet "instant wake up" that I saw on MB Airs using SL when I tested this behavior at the apple store earlier this year. But curiously the wake up is as slow and erratic as the "not so instant wake up" on the early 2011 MBP (also running SL). Apple had this big marketing argument that the MB Air would wake up instantly and I noticed how noticeably slower the early 2011 MBP were at waking up. I found that very suspicious since both previous generation MBP and my wife's MBP from a couple years ago wakes up as instantly as the MB Air did even though it's old, uses a regular HD and runs SL or Leopard. For me that killed any credibility to the argument that "SSD drives would make your MB Air wake up instantly". I was more left wondering "*** is Apple playing at ?!?!"

Anyways, I tried the disk repair route like others described, but to no avail...

However: While testing the wake-up behavior on various machines earlier this year, I looked a bit closer at the power management options hidden under the hood and only accessible via a Terminal console, using the command "pmset -g". I had looked at the configuration for the "hibernate mode" of the early 2011 MB Air and MB Pro. The air had its hibernatemode set to "0" (fast but unsafe sleep/wake) and the pro to "3" (which means potentially slower wake and sleep as the memory is being dumped onto a disk image for a safe sleep in case of power loss; see "man pmset" for details). The big surprise though is my brand new MB Air had its hibernatemode set to "3"… and guess what ? switching it to "0" seems to help with the wake up times a lot! It doesn't feel as slick as on SL, but it is much improved. To try it for yourself, all you need to do is open a terminal window and type:

sudo pmset -a hibernatemode 0

(then type your password to authorize the change)

After that, make sure to save your work often when you get close to very low battery levels. I would be very curious to hear if this works for other people too.

To me, this seems to indicate that half of the "hibernate mode 3" behavior is not working right, and the system is trying to dump memory onto disk right away, instead of waiting for very low battery level.

sudo pmset -a hibernatemode 0

Worked for me! Thanks so much for the suggestion. Now I can get back to work without the dredded wait.

I don't think your solution of changing hibernatemode to 0 is the answer.

There must be a bug in Lion making it resume from the disk image regardless of power being maintained during sleep.

For those that don't know, hibernatemode 3 means that the system will copy the contents of the RAM to your hard disk and keep power to the RAM.

If you maintain power to the RAM (ie. keep sufficient battery level), it should wake up more or less instantly.

If power is cut (drained battery, swapped battery, etc), the contents of the RAM disappear so prior to resuming, the system must copy the contents back there before resuming.

This is the several second process we're all complaining about (copying the several GB of data from your disk to RAM takes time, even with an SSD). I think Lion does this even though power was maintained.

hibernatemode 0 simply disables writing the RAM to the hard disk. If you lose power, too bad.

In this mode, as long as power is maintained, you will always wake up more or less instantly.

I agree that changing the hibernate mode is not a great idea - remember when 'safe sleep' was first introduced and how much better it was than sleep? I don't know about other machines and their default settings but checking my 2011 MBA I noticed that the 'standbydelay' value for pmset was configured for 4200 seconds (70 mins). This setting controls how long power is maintained to the RAM after sleep starts. If non-zero and if the hibernate mode is set to something other than 0 then after the specified time the RAM power is turned off and the content of RAM is lost. This does wonders for the 'standby' time because power to the RAM is the vast majority of the power used in 'sleep' mode (with detection of bluetooth devices, wake on lan/wlan, lid opening sensor etc. taking a small amout each). Remember Apple's "30 days of standby" advertising? However, it basically means if you leave the machine for more than 70 mins then when you wake it up you will be coming out of hibernate, not traditional sleep.

Having understood this was likely the reason for the slow wake times then I'm actually ok with the setting - it's just a shame there is no indication that this is what is happening (esp. as the MBA has no noises or lights to tell you it is waking up!) but those of you willing to sacrifice standby time for speed of waking might want to check their value and set it to something like 8 hours - then you will only come out of hibernate first thing in the morning after being asleep overnight and any shorter period of sleep during the day will not trigger hibernation mode 🙂

You can see all your current pm settings using: sudo pmset -g

You can see details of the settings and their meanings by: man pmset

Hi Robert I did the command as you indicated at got this;

Last login: Tue Sep 6 18:39:30 on ttys000

Mordechais-MacBook:~ mordechai$ sudo pmset -g

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

womp 1

halfdim 1

sms 1

panicrestart 157680000

hibernatefile /var/vm/sleepimage

networkoversleep 0

disksleep 10

sleep 60

hibernatemode 3

ttyskeepawake 1

displaysleep 60

acwake 0

lidwake 1

Mordechais-MacBook:~ mordechai$

I can't see the standbydelay setting ?

Am I doing something wrong....

It is most likely that if standbydelay doesn't show up in the output that it is not active (or not supported by the power management chip in your machine) which would suggest this is not the problem you are having. As I said above, I have a MBA so the settings on your macbook may very well be different 🙂 A friend of mine with a MBP tried deleting the /var/vm/sleepimage file and found that there was an improvement in wake-up times for him so give that a go and see what happens 🙂

Well, I went straight from a late 2010 MBA with SL to a 2011 MBA with Lion and found the whole "instant-on" thing was just raped.

Does anyone know the standbydelay value that was defaulted on the late 2010 SL MBA?

My year-old Macbook Pro 13 takes several seconds to reconnect to my network; before Lion it was instant. Very annoying. Any fix? Programs also slower to load.

The slow wakeup behavior on my MacBook Pro (2011) with Lion SEEMS to be tied to the Time Machine activity.

If, when I wake the machine from sleep, it wakes up promptly and everything works more or less as it should.

IF, however, when I wake up the machine and the Time Machine icon is cranking, THEN, the airport will not connect and everything else either won't work or is very sluggish. I then order Time Machine to stop backing up, and wait until it does (takes quite some time!). As soon as it stops, the airport signal pops in and everything is back to normal.

Does this give anyone any clues to a solution for this problem?

Problem also happens with all time machine features disabled.

For me, it is simply waking from disk (hibernation), not sleep. I've set the timeout longer and now it's almost back as it was.