Go to Sleep!!! Macbook Pro won't sleep right away...

[JajoPGH]

Hi again folks.

A small new problem I have encountered is that my computer will take a very long time to fall asleep. This happens when I go Apple > Sleep.

It will take at least a minute to go to sleep. On the other hand, if I close the lid, it will take a few seconds to go to sleep.

Any idea what this could be? It's very annoying, because sometimes I like to put the computer to sleep with the lid open.

While I'm here, I have related question. Is it bad for your computer to be put to sleep and awaken often (say twice in 5 minutes)?

Thank you!

[whooleytoo]

It seems like it's going to 'deep sleep' when you select Sleep from the menu, but normal sleep when you close the lid.

(You can verify if this is true, by looking at the light on the front; if it's slowly throbbing, it's normal sleep; whereas if the light is off, it's in deep sleep).

The benefit of deep sleep is that it doesn't consume any power, but it does take a little longer to sleep (saving the contents of memory to disk, so it can resume on wake).

I use the Deep Sleep widget to control this.

[JajoPGH]

Originally Posted by whooleytoo

It seems like it's going to 'deep sleep' when you select Sleep from the menu, but normal sleep when you close the lid.

(You can verify if this is true, by looking at the light on the front; if it's slowly throbbing, it's normal sleep; whereas if the light is off, it's in deep sleep).

The benefit of deep sleep is that it doesn't consume any power, but it does take a little longer to sleep (saving the contents of memory to disk, so it can resume on wake).

I use the Deep Sleep widget to control this.

I tried verifying, but it turns out the light still throbs after I click "Sleep." This is strange, because I have never encountered this problem before.

[Makosuke]

They should both do the same thing--regardless of how you put the computer to sleep, an Apple laptop should pause for a moment while it saves contents of memory to disk (in case it loses power while asleep), then go to sleep and pulse the light. So far as I know the only way of getting into "deep" sleep--as in a state where it has completely powered down--is cutting power while it's asleep (correct me if they've added this to the new Unibodys).

To my knowledge, it does the same procedure regardless of how you've asked it to sleep. Are you sure you don't just THINK it's sleeping faster when you close the lid because the screen powers down immediately? Is the delay related to when the light actually starts pulsing (which is the point at which it has FINISHED going to sleep)?

My MBP, if I close the lid, will turn off the screen and turn the light on, but if I listen carefully I can hear the hard drive grinding away (and the fan running) until it has finished saving RAM contents to disk, at which point the light goes from steady on to throbbing and everything fully powers down. This takes probably 15 seconds or so with 2GB of RAM, though I've never timed it. I assume were I to select Sleep from the menu with the screen open it would take just as long but the screen would stay awake during the write-to-disk process. Never tried, admittedly, since I always just close the lid.

[JajoPGH]

Originally Posted by Makosuke

They should both do the same thing--regardless of how you put the computer to sleep, an Apple laptop should pause for a moment while it saves contents of memory to disk (in case it loses power while asleep), then go to sleep and pulse the light. So far as I know the only way of getting into "deep" sleep--as in a state where it has completely powered down--is cutting power while it's asleep (correct me if they've added this to the new Unibodys).

To my knowledge, it does the same procedure regardless of how you've asked it to sleep. Are you sure you don't just THINK it's sleeping faster when you close the lid because the screen powers down immediately? Is the delay related to when the light actually starts pulsing (which is the point at which it has FINISHED going to sleep)?

My MBP, if I close the lid, will turn off the screen and turn the light on, but if I listen carefully I can hear the hard drive grinding away (and the fan running) until it has finished saving RAM contents to disk, at which point the light goes from steady on to throbbing and everything fully powers down. This takes probably 15 seconds or so with 2GB of RAM, though I've never timed it. I assume were I to select Sleep from the menu with the screen open it would take just as long but the screen would stay awake during the write-to-disk process. Never tried, admittedly, since I always just close the lid.

Thank you for spending the time to write that response to me...

Well, I know it takes time for the computer to be put to sleep, but before yesterday, it took 10 seconds. Now it takes close to a minute. When I close the lid, it takes long too. The Apple logo will stop glowing, but the white LED in the front will be lit and won't throb. It will take a minute or so for it to start throbbing.

What are some things I could do about this? Do I have to reinstall OSX? I really hope this isn't the tip of the iceberg of a bigger problem.

[JajoPGH]

Does anyone have any other suggestions on what I may do to alleviate this problem?

I don't want to resort to calling Apple.

And I really hope this is not a sign of things to come. I'm worried the computer may have several problems down the road.

[appleaphid]

Hey, did anyone find the solution?

My late 2008 Macbook pro has been slow to go to sleep (close to 1min) and it used to take just a few seconds . This is using either sleep in the apple menu or closing the lid.

I have tried closing all programs, and it still takes a long time. Any help would be much appriciated.

Cheers,
Mick

Using a late 2008 Macbook pro 2.5GHz, 4RAM, 320HD, Leopard 10.6.2

[spinnerlys]

http://www.jinx.de/SmartSleep.html will put the Mac to sleep like in the old PowerBook/iBook times.

[majidmx]

hey guys,

I Just signed up to post the reply.
I found the solution for this, you have to search for the logs and see what is taking too much time. Use the following command :

pmset -g log

Look for "applicationresponse.slowresponse" and look for the "Signature" with the longest time."

In my case it was an old print job which I had sent my mistake to an offline printer and forgot to delete it from the queue.
I went to "print and fax" in system preferences and found the printer, checked the queue and deleted the job.
Now my lovey MBP sleeps in 2 seconds like an infant.

[onehoop]

Originally Posted by majidmx

I found the solution for this, you have to search for the logs and see what is taking too much time. Use the following command :

pmset -g log

In my case it was an old print job which I had sent my mistake to an offline printer and forgot to delete it from the queue.
I went to "print and fax" in system preferences and found the printer, checked the queue and deleted the job.
Now my lovey MBP sleeps in 2 seconds like an infant.

...very interesting...
I've got 2 com.apple.powermanagement.applicationresponse.slowresponse 's.
1 is a Kernel configd and the other a PMConnection mDNSResponder. The slowresponse varies, but the last instance the Kernel was 7763ms and the PMConnection was 536ms.

Are those normal values? Anything to be done for it?

-=-=-=-

As to the OP:
My computer is the original Intel Core Duo MBP and it has always had problems with sleeping. Lately the battery is so low that it became intolerable and I would have to turn it off to travel. From searching other forums, I found that the problem was with the loose latch which would shift from time to time awakening and sleeping the computer, which would confuse the Power Management and occasionally incite a kernel panic and overheating inside my travel bag. Or so it would seem. Anyway, the solution that I found was to write out the terminal line:

sudo pmset -a lidwake 0

Sudo commands are dangerous and require you to enter your (root) password (more accurately, sudo allows you to enter root commands which then require your password unless you just entered it in the last 5 minutes or so).
Before you follow this advice blindly, it would be wise to read the

man pmset

page to see what it does. Since I've already done so, you may want to change the "-a" flag to a "-b", since it only matters when on battery.

I just did this yesterday, but preliminary tests seem to show my computer holding a charge better while closed.

Hope that helps.


M@

[Heb1228]

I've also been noticing longer-than-expected sleep times when closing the lid. I ran the command that majidmx mentioned above and get two recurring errors. Anybody have an idea about fixing these?

Here's a sample of each:

- Message: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 2109 ms
 - Time: 2/2/10 4:47:21 PM EST 
 - Signature: IPConfiguration

 - Message: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 2109 ms
 - Time: 2/2/10 4:47:21 PM EST 
 - Signature: AirPort configd plug-in

Looks like it has something to do with Airport/Networking not closing down a connection like it should.