Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Snow Leopard takes too long to sleep - how to fix??

IMO setting "hibernatemode 0" is a poor solution and irresponsible advice to give to others without explaining the risk: disabling important feature (Deep Sleep) = potential for data loss
 
Mine took exactly 10 seconds to sleep when hibernatemode is set to 3. It's down to < 3 when hibernatemode is set to 0.

Now I need to figure out why my shutdown takes longer. I think it's because of CrossOver. Are there any logs to watch the shutdown process?
 
So it is a better idea not to set the "hibernationmode" to 0? I'm also getting 10-15 sec (sometimes even slightly more) time before my MBP goes to sleep.

I guess this one would be the culprit?

* Domain: hibernatestats
- Message: Hibernate Statistics
- Time: December 13, 2009 9:50:25AM GMT+01:00
- Signature: hibernatemode=3
- UUID: 3AAA1FC2-1C3B-4023-AB08-07B4D4B0B34F
- Time to write image (ms): 21769
 
jon08 said:
So it is a better idea not to set the "hibernationmode" to 0? I'm also getting 10-15 sec (sometimes even slightly more) time before my MBP goes to sleep.

I guess this one would be the culprit?

* Domain: hibernatestats
- Message: Hibernate Statistics
- Time: December 13, 2009 9:50:25AM GMT+01:00
- Signature: hibernatemode=3
- UUID: 3AAA1FC2-1C3B-4023-AB08-07B4D4B0B34F
- Time to write image (ms): 21769
Click to expand...

Well, it will definitely speed up sleep times (less than 3 seconds). It's just that, if your laptop loses power while in sleep mode, and when you turn it on, you'll have to start as if you just turned your computer on; you won't be able to continue where you left off.

Windows 7 sleeps in less than 1 (HDD + fans off) AND it makes an image of the memory like hibernatemode 3 does 😉.
 
My new Macbook Pro was having the same problem after the recent software update.

It was taking 20 to 30 seconds to sleep. When I first got the MBP, sleep took maybe 2 seconds.

It looks like I had a print job pending too, and deleting it solved the issue.


That's annoying. Apple should make it so that the print que stays open as long as it has a job to print.
 
Rampant.A.I. said:
My new Macbook Pro was having the same problem after the recent software update.

It was taking 20 to 30 seconds to sleep. When I first got the MBP, sleep took maybe 2 seconds.
Click to expand...
It depends on how much stuff you have open (in RAM) which needs to be saved to disk. That way in case you lose power during sleep, everything is safe & restored as if your machine never lost power.

hibernate=0 defeats this valuable feature to save a few seconds before sleep.
 
pezsma said:
I had the same problem, with 30-second sleeps caused by cupsd timing out. It turned out that back in August I accidentally sent a document to an old printer that I never turn on anymore, and ever since then the job has been patiently sitting in the printer queue. It looks like cupsd (the printer daemon) tries to prevent the system from sleeping while there are documents to print---which doesn't sound like an unreasonable policy in the usual case.

Deleting that silly print job fixed the issue: my 4 GiB MBP now goes to sleep in under 2 seconds!
Click to expand...


GENIUS! Found the culprits in the print queue from a printer used rarely at an office I visit periodically. Sleep time cut from 30sec+ -> 4sec. Thanks!!!
 
doug in albq said:
I had the same issue as the OP.

Got this tip on the Apple discussion forums from "Snoop Dog":


"You can figure out what's delaying sleep by running the following command in Terminal.

pmset -g log

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


For me that tip by "Snoop Dog" tracked down "efax" as timing out after a very slow "applicationresponse" of 30,000ms...

light bulb goes on in my head and I open up system preferences and go into "Printers and Fax"

deleted an old fax profile set up with my external apple fax/modem that is only hooked up in the rare occurrence of needing to send or receive a fax...

BAM!
Time for my macbook to sleep goes from 30 seconds to about 4 seconds!!
Click to expand...

is there a similar command for Leopard? pmset -g log doesn't work.
 
Yeah!!!

It worked!!!!! I deleted a printer that I wasn't using a BOOMMM!!!! In 2 seconds my iMac was on sleep!!!!

Thank you!! 😀
 
How do I check if a supposed "printing job" is affecting my MBP's sleep time as well? (It usually takes about 15-20 secs to go to sleep mode after I've closed the lid).
 
Solved my problem as well! Thanks!
jon08 said:
How do I check if a supposed "printing job" is affecting my MBP's sleep time as well?
Click to expand...

Go to System Prefs -> Print & Fax -> Highlight each printer in turn and click "Open Print Queue"
 
Does anyone know why would pmset -g log would only go up to specific date and not the latest entry ? Or how to clean the log ?
 
I cant figure out how to clean the log or see full log for pmset -g log, when I do that i get entries up to July this year and thats it. Please help
 
My computer takes quite a long time to sleep too.

I'm noticing a few things that have a response time of about 800, but then there's this..what is it?


* Domain: hibernatestats
- Message: Hibernate Statistics
- Time: 12/29/10 4:39:19 AM EST
- Signature: hibernatemode=3
- UUID: 4836004E-2DA5-414C-A681-7723BA52B059
- Time to write image (ms): 5477
 
Hi all,

Just got a 13" MBA a few days before Christmas. Have been using it, installed MS office 11, a few other things, but not much.

***Did install a Brother network printer, but have since uninstalled it, so I cant imagine its queue has anything to do with this - Ive positively verified that I have NO printers installed at this time.***

Anyway, I get this:

* Domain: applicationresponse.timedout
- Message: Kernel plugin-container com.apple.powermanagement.applicationresponse.timedout 30000 ms
- Time: 12/31/10 5:41:34 PM EST
- Signature: plugin-container
- UUID: 8481B2EE-D472-4E13-B580-0FBCFF5A84EC
- Result: Noop
- Response time (ms): 30000

Ive got this computer set up like our others, so nothing is really different. This one has the SSD which is ultra-quick to boot from completely shut down, instant to wake-up, etc., yet I have this 30 second latency on sleep command where nothing happens. Heck, it even allows me to open new programs, surf the web, etc. after Ive executed the sleep command.

My Hibernate mode is "3".

Any ideas/suggestions???

Thanks!
 
pezsma said:
It turned out that back in August I accidentally sent a document to an old printer that I never turn on anymore, and ever since then the job has been patiently sitting in the printer queue. It looks like cupsd (the printer daemon) tries to prevent the system from sleeping while there are documents to print
Click to expand...


Thanks, that solved the problem on my 2010 iMac! 😎
 
These are mine that take more time to response:
I'm running latest google chrome dev

* Domain: applicationresponse.slowresponse
- Message: Kernel powerd com.apple.powermanagement.applicationresponse.slowresponse 15928 ms
- Time: 7/23/11 4:20:41 PM GMT+
- Signature: powerd
- UUID: D1A5A219-ABDD-41D3-9F95-7098470C88E6
- Result: Noop
- Response time (ms): 15928


* Domain: applicationresponse.slowresponse
- Message: PMConnection mDNSResponder com.apple.powermanagement.applicationresponse.slowresponse 11005 ms
- Time: 7/23/11 5:26:16 PM GMT+
- Signature: mDNSResponder
- UUID: 895080D9-D546-42CD-B829-8AFC55DD0442
- Result: Noop
- Response time (ms): 11005


* Domain: applicationresponse.timedout
- Message: Kernel Google Chrome He com.apple.powermanagement.applicationresponse.timedout 30000 ms
- Time: 7/23/11 6:53:43 PM GMT+
- Signature: Google Chrome He
- UUID: 895080D9-D546-42CD-B829-8AFC55DD0442
- Result: Noop
- Response time (ms): 30000


google chrome only have 4 tabs open and the plugins running are adblock and flashblock.
if i quit chrome the sleep time goes from 45sec +- to 20sec wich is still to big, any help? why is chrome so slow?

thanks
 
Slow sleep solved!

I ran the Terminal command and also found I had a problem with cupsd timing out. Fixed it by removing old queued print jobs. Yay!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back