3

I'm having issues with my MacBook Air 2013 waking from sleep into Dark Wake every minute since I upgraded to Mavericks. Whenever it's been to sleep and goes into standby it keeps waking up. This is what pmset -g log looks like:

2013-10-25 06:52:41 CEST DarkWake               DarkWake [CDN]  : Using BATT (Charge:60%)                                   45 secs   
2013-10-25 06:53:26 CEST Assertions             PID 18(powerd) Released InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:45  id:0xe00001348 [System: No Assertions]              
2013-10-25 06:53:26 CEST Sleep                  Maintenance Sleep: Using BATT (Charge:60%)                                  16 secs   
2013-10-25 06:53:28 CEST SlowResponse           PMConnection: Response from com.apple.apsd is slow (powercaps:0x0)                    1996 ms       
2013-10-25 06:53:28 CEST WakeRequests           Clients requested wake events: None                                                   
2013-10-25 06:53:42 CEST Assertions             PID 18(powerd) Created InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:00  id:0xe0000135c [System: No Assertions]           
2013-10-25 06:53:42 CEST DarkWake               DarkWake [CDN]  : Using BATT (Charge:59%)                                   45 secs   
2013-10-25 06:54:27 CEST Assertions             PID 18(powerd) Released InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:45  id:0xe0000135c [System: No Assertions]              
2013-10-25 06:54:27 CEST Sleep                  Maintenance Sleep: Using BATT (Charge:59%)                                  18 secs   
2013-10-25 06:54:29 CEST SlowResponse           PMConnection: Response from com.apple.apsd is slow (powercaps:0x0)                    1831 ms       
2013-10-25 06:54:29 CEST WakeRequests           Clients requested wake events: None                                                   
2013-10-25 06:54:45 CEST Assertions             PID 18(powerd) Created InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:00  id:0xe0000136f [System: No Assertions]

And so on throughout the entire night. The console says 2013-10-25 06:41:20,000 kernel[0]: Wake reason: ? for every wake, so I guess my only shot is trying to figure out what DarkWake [CDN] means which there doesn't seem to be any info on. Also, this is while the Mac is on battery and with pmset -g darkwakes 0 (I.e. Power Nap turned off for battery).

  • Have you attempted to reset the SMC or zap the PRAM to see if that helps? Do you have all external devices or other media (DVD/SD card) disconnected when testing (Created InternalPreventSleep "PM configd - Wait for device enumeration")? "InternalPreventSleep" may be an assertion that is preventing sleep? – Eddie Kelley Oct 25 '13 at 21:24
  • Did both of those, no dice. Nope, no external devices connected. – Rick Oct 26 '13 at 15:26
  • Rick, do you happen to be running a virtual machine of any kind in the background? I'm seeing the same issue as you and wondering whether that could be a culprit... – benilov Oct 31 '13 at 11:15
  • Nope, I hade no VMs. – Rick Nov 4 '13 at 10:17
  • Is System Preferences / Energy Saver / Wake for network access checked? Maybe something pings your machine regularly or something similar is happening? – biziclop Feb 2 '14 at 13:16
4

My workaround was to disable sleep using sudo pmset -b standby 0. Not really a fix but a temporary workaround until I revisit the issue.

  • I solved similar issue with setting MBP to always hibernate. – krtek Dec 19 '15 at 19:00
1

I am having the same issue with my Macbook Air 2013 since upgrading to Mavericks

SMC and PRAM reset did not solve the problem.

After 3 hours sleeping on battery, Mac tries to change from sleep to DeepSleep (hibernate) mode. Then, constantly waking itself back up each minute afterwards until the battery drains to <1%.

It has to be a bug on Apple side.

  • My workaround was to disable sleep using sudo pmset -b standby 0. I thought it might be related to Better Touch Tool since it's gotten a bunch of "Mavericks compatibility" updates but I haven't tried re-enabling hibernate since those, the battery life is still great even without that. – Rick Oct 31 '13 at 10:10
  • @Rick Can you post this as an answer? – nohillside Nov 3 '13 at 13:24
  • Sure, but it's not really an answer as much as a temporary workaround. – Rick Nov 3 '13 at 17:00

You must log in to answer this question.

protected by Community Nov 4 '13 at 4:28

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .