2012 mbp - slow wake up from sleep after last mbp update

Has anyone tried unchecked put hard disk to sleep in energy preference. I read somewhere that it will not go into hibernation when on charger mode.

I have the same MacBook Pro as you and that's the exact problem I am having with the hard drive or CD drive noise and the progressive bar. Did you ever update the EFI?

- Daniel 

I am not sure what is EFI update?

I do all my updates only from the Mac App Store that prompted me. Now running 10.8.2, everything up to date according to Mac App Store now.

The EFI update would've been in the Mac App Store as a system update. I asked because I only seemed to have this problem after an EFI update (which I'm not sure exactly what it is either), not after updating to 10.8.2.

- Daniel 

There is a new update today!! It just appeared in my mac app store.

Has anyone download it already? Maybe it will solve our problem. 🙂

I also posted the problem today. So do you think Apple simply changed the behavior how Macs sleep or is it actually a bug?

I downloaded the update and installed it. It doesn't seem to have worked.

- Daniel 

Same here... I downloaded the new update and just checked my MacBook Pro after more than 4 hrs it goes to hibernate, while it is still plugged in to the charger.

Looks like the new update did not address our issue.

Has anyone changed their pmset settings like I mentioned a few posts back? This does work, I have not had the slow wake problem/grey screen w/ progress bar since I did so.

Hi Debra, it was really great effort of you to figure out the solution to solve the issue.

However, I not change anything inside pmset because I was hoping for apple to give us their official version. Furthermore, I was told by apple support not to touch anything in pmset. Will I mess up my system if there is an update later in the future?

I sort of welcome the change, like you said in your earlier post it will save battery, but the problem is that my MacBook Pro only goes into hibernation when is on charger, but remains in sleep throughout battery mode. It should be the opposite, very strange.

Unlike another user here, N748, I also tried closing the lid while is on battery, it goes on sleep even after many hours and never into hibernation.

Seems like some of us have different issues, which really puzzles me.

At 15:27 I closed the lid of my MBP. Four hours later it woke to do something. Twenty minutes later I opened the lid. Is someone more experienced with the OS X logs than me? I suspect it has to do with time machine or some PowerNap feature rudimentary...

Nov 29 15:27:24 x kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

Nov 29 15:27:24 x kernel[0]: /drv/ MacModule.cpp:304 powerStateWillChangeTo: flags=4 stateNumber=2

Nov 29 15:27:24 x kernel[0]: /drv/ MacModule.cpp:309 powerStateWillChangeTo: found flag=kIOPMSleepCapability (4)

Nov 29 15:27:27 x kernel[0]: en1: BSSID changed to xxx

Nov 29 15:27:27 x kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0

Nov 29 15:27:27 x kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

Nov 29 15:27:27 x kernel[0]: en1::IO80211Interface::postMessage bssid changed

Nov 29 15:27:27 x kernel[0]: [AppleMultitouchDevice::willTerminate] entered

Nov 29 15:27:27 x kernel[0]: [AppleMultitouchDevice::stop] entered

Nov 29 15:27:28 x kernel[0]: /drv/ MacModule.cpp:304 powerStateDidChangeTo: flags=4 stateNumber=2

Nov 29 15:27:28 x kernel[0]: /drv/ MacModule.cpp:309 powerStateDidChangeTo: found flag=kIOPMSleepCapability (4)

Nov 29 15:27:28 x kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)

Nov 29 19:27:27 x kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

Nov 29 19:27:27 x kernel[0]: /drv/ MacModule.cpp:304 powerStateWillChangeTo: flags=2 stateNumber=3

Nov 29 19:27:27 x kernel[0]: /drv/ MacModule.cpp:305 powerStateWillChangeTo: found flag=kIOPMPowerOn (2)

Nov 29 19:27:27 x kernel[0]: /drv/ MacModule.cpp:304 powerStateDidChangeTo: flags=2 stateNumber=3

Nov 29 19:27:27 x kernel[0]: /drv/ MacModule.cpp:305 powerStateDidChangeTo: found flag=kIOPMPowerOn (2)

Nov 29 19:27:27 x kernel[0]: Previous Sleep Cause: 5

Nov 29 19:27:27 x kernel[0]: en1: 802.11d country code set to 'X3'.

Nov 29 19:27:27 x kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140

Nov 29 19:27:27 x kernel[0]: TBT W (1): 0 [x]

Nov 29 19:27:28 x kernel[0]: Graphics suppressed 1846 ms

Nov 29 19:27:28 x configd[17]: ipsec_wake_up: System slept for 14404.000000 secs (more than 7200.000000 secs), interface utun0 will disconnect.

Nov 29 19:27:28 x racoon[1332]: Connecting.

Nov 29 19:27:28 x configd[17]: IPSec disconnecting from server xxx

Nov 29 19:27:28 x racoon[1332]: IPSec Phase1 started (Initiated by me).

Nov 29 19:27:29 x racoon[1332]: IKE Packet: transmit success. (Initiator, Aggressive-Mode message 1).

Nov 29 19:27:29 x configd[17]: SCNC Controller: service_ending_verify_primaryservice, waiting for PrimaryService. status = 1.

Nov 29 19:27:29 x racoon[1332]: IPSec disconnecting from server xxx

Nov 29 19:27:29 --- last message repeated 1 time ---

Nov 29 19:27:29 x kernel[0]: SIOCPROTODETACH_IN6: utun0 error=6

Nov 29 19:27:29 x com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fcb29c375f0> Thu Nov 29 16:09:01 2012 CET (approx)

Nov 29 19:27:29 x configd[17]: SCNC Controller: ipv4_state_changed, done waiting for ServiceID.

Nov 29 19:27:29 x com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fcb29c375f0> Thu Nov 29 16:09:01 2012 CET (approx)

Nov 29 19:27:29 x kernel[0]: hibernate image path: /var/vm/sleepimage

Nov 29 19:27:29 x kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

Nov 29 19:27:29 x kernel[0]: hibernate_alloc_pages act 453337, inact 451530, anon 101756, throt 0, spec 49073, wire 383339, wireinit 116913

Nov 29 19:27:29 x kernel[0]: hibernate_setup(0) took 0 ms

Nov 29 19:27:29 x kernel[0]: sizeof(IOHibernateImageHeader) == 512

Nov 29 19:27:29 x kernel[0]: kern_open_file_for_direct_io(0) took 0 ms

Nov 29 19:27:29 x kernel[0]: Opened file /var/vm/sleepimage, size 8589934592, partition base 0x0, maxio 400000 ssd 1

Nov 29 19:27:29 x kernel[0]: hibernate image major 1, minor 0, blocksize 512, pollers 5

Nov 29 19:27:29 x kernel[0]: /drv/ MacModule.cpp:304 powerStateWillChangeTo: flags=4 stateNumber=2

Nov 29 19:27:29 x kernel[0]: /drv/ MacModule.cpp:309 powerStateWillChangeTo: found flag=kIOPMSleepCapability (4)

Nov 29 19:27:29 x kernel[0]: /drv/ MacModule.cpp:304 powerStateDidChangeTo: flags=4 stateNumber=2

Nov 29 19:27:29 x kernel[0]: /drv/ MacModule.cpp:309 powerStateDidChangeTo: found flag=kIOPMSleepCapability (4)

Nov 29 19:27:29 x kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff80df2f6000, 0xffffff80df336000

Nov 29 19:47:58 x kernel[0]: hibernate_page_list_setall time: 360 ms

Nov 29 19:47:58 x kernel[0]: pages 1326290, wire 369119, act 279398, inact 8, cleaned 0 spec 100, zf 55067, throt 0, could discard act 171300 inact 375033 purgeable 5891 spec 49095 cleaned 21279

Nov 29 19:47:58 x kernel[0]: hibernate_page_list_setall found pageCount 703692

Nov 29 19:47:58 x kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0

Nov 29 19:47:58 x kernel[0]: IOHibernatePollerOpen(0)

Nov 29 19:47:58 x kernel[0]: encryptStart 13270

Nov 29 19:47:58 x kernel[0]: bitmap_size 0x3f8e0, previewSize 0xd09818, writing 700013 pages @ 0xd5c368

Nov 29 19:47:58 x kernel[0]: hibernate_machine_init: state 2, image pages 368915, sum was c88ade23, image1Size 1f26d000, conflictCount 4225, nextFree 1350

Nov 29 19:47:58 x kernel[0]: hibernate_page_list_discard time: 259 ms, discarded act 171300 inact 375033 purgeable 5891 spec 49095 cleaned 21279

Nov 29 19:47:58 x kernel[0]: IOHibernatePollerOpen(), ml_get_interrupts_enabled 0

Nov 29 19:47:58 x kernel[0]: IOHibernatePollerOpen(0)

Nov 29 19:47:58 x kernel[0]: hibernate_machine_init reading

Nov 29 19:47:58 x kernel[0]: PMStats: Hibernate read took 1906 ms

Nov 29 19:47:58 x kernel[0]: hibernate_machine_init pagesDone 703488 sum2 b5fcc189, time: 1906 ms, comp bytes: 1280618496 time: 1223 ms 998 Mb/s, crypt bytes: 587154944 time: 248 ms 2251 Mb/s

Nov 29 19:47:58 x kernel[0]: vtd[0] fault: device 3:0:0 reason 0x5 W:0x85aeb000

Nov 29 19:47:58 x kernel[0]: Wake reason: EC.LidOpen (User)

Nov 29 19:47:58 x kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

Nov 29 19:47:58 x kernel[0]: /drv/ MacModule.cpp:304 powerStateWillChangeTo: flags=2 stateNumber=3

Nov 29 19:47:58 x kernel[0]: /drv/ MacModule.cpp:305 powerStateWillChangeTo: found flag=kIOPMPowerOn (2)

Nov 29 19:47:58 x kernel[0]: /drv/ MacModule.cpp:304 powerStateDidChangeTo: flags=2 stateNumber=3

Nov 29 19:47:58 x kernel[0]: /drv/ MacModule.cpp:305 powerStateDidChangeTo: found flag=kIOPMPowerOn (2)

Nov 29 19:47:58 x kernel[0]: Previous Sleep Cause: 5

Nov 29 19:47:58 x kernel[0]: Previous Shutdown Cause: 5

Nov 29 19:47:58 x com.apple.launchd[1] (com.apple.newsyslog): Throttling respawn: Will start in 7 seconds

Nov 29 19:47:58 x kernel[0]: TBT W (1): 0 [x]

Why did this hibernation function suddenly activate after sleeping for 4 hrs? I used to leave my macbook to sleep for ages while charging and it will wake in an instant when i press the spacebar.

Today i just discovered that when i unplugged my charger while it is hibernating after 4 hrs, it wakes up and goes to sleep, (pulsating sleep light) and when i try to turn it on by pressing the spacebar, nothing happens. I have to press the power button to turn it on. This has never happen before....

I just want my macbook pro to function like it used to. 😟

I just want my macbook pro to function like it used to. 😟

Full acknowledgement.

Well to be honest, I am not going to fiddle around with my mac. Since this problem is with many other users and doesn't seem to be a really major problem, I am happy to wait for Apple to release a fix for this problem. I don't mind a bit of waiting before my mac starts up, not that impatient.

I was worried simply because I thought this was a big issue and that there is some sort of glitch in my machine, but it isn't so. But now that I know that many other people face the same problem, I am somewhat relieved and I'll just go ahead and wait for that update.