Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MBA mid-2013 wakes from sleep every minute on Mavericks

After upgrading to Mavericks my MBA mid-2013 constantly wakes up from sleep every minute during the night draining battery to 0%.I did syslog | grep -i "Wake reason" and the result is "?" for each logged wake event. There are few more reports on this all over the Internet with slight variations. This happens

while on battery and I did try SMC reset. Any tips? It's gettig quite frustrating. User uploaded file

MacBook Air, OS X Mavericks (10.9)

Posted on Oct 30, 2013 6:03 AM

Reply
Question marked as Best reply

Posted on Oct 30, 2013 1:01 PM

I'm suffering from the same thing - MBA 2013, wakes every 1 minute and drains the battery overnight. Very odd. Mountain Lion didn't do this! 😟


pmset -g log

Also produced a repeated set of info, every ~1 minute, the following is repeated. Anyone any thoughts? I've reset PRAM and SMC...


30/10/2013 10:51:24 GMT DarkWake DarkWake [CDN] : Using BATT (Charge:0%) 22 secs

30/10/2013 10:51:24 GMT HibernateStats hibmode=3 standbydelay=10800 rd=1548 ms

30/10/2013 10:51:24 GMT SlowResponse Kernel: Response from powerd is slow (powercaps:0x0) 28209 ms

30/10/2013 10:51:29 GMT Assertions PID 16(powerd) Released InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:05 id:0xe00002767 [System: PushSrvc kCPU]

30/10/2013 10:51:46 GMT Sleep Maintenance Sleep: Using BATT (Charge:0%) 51 secs

30/10/2013 10:51:48 GMT SlowResponse PMConnection: Response from com.apple.apsd is slow (powercaps:0x0) 1992 ms

30/10/2013 10:52:14 GMT Timedout PMConnection: Response from CMacPowerHelper timed out (powercaps:0x0) 28150 ms

30/10/2013 10:52:14 GMT Timedout PMConnection: Response from CMacPowerHelper timed out (powercaps:0x0) 28151 ms

30/10/2013 10:52:14 GMT WakeRequests Clients requested wake events: None

30/10/2013 10:52:37 GMT Assertions PID 16(powerd) Created InternalPreventSleep "PM configd - Wait for Device enumeration" 00:00:00 id:0xe00002779 [System: No Assertions]

134 replies

Jun 3, 2014 8:30 AM in response to alessio85

Not entirely. I have upgraded XQuartz to the latest v2.7.6 and installed all OS updates avalable as of May 27, 2014. Yet, after using Inkscape for a couple of hours and closing the lid, my laptop woke up after three hours of hybernation and failed to go into the deep sleep mode. The log was filled with usual "Wake reason: ?".


Everything was normal after that. However, I did not run Inkscape. Since I use Inkscape only sporadically, I can't tell for sure if Inkscape is the actual culprit or not. So far, both my incidents occurred after using it though.

Jun 14, 2014 3:39 PM in response to rcolonescu

Hi,

I have MacBook Pro 13" retina, i5, 16GB, 256SSD. I have it one mont and I am dealing this issue with apple support maybe 14 days.. We tried everything you described here - SMC reset, PRAM, NVRAM reset, systemconfiguration folder deleted, safe boot etc. Then they told me to erase and reinstall system, maually restore all data and install apps again.. This is exactly what I hated about windows. I guess it won't help anyway so I am not going to do that. I will try to uninstall Avast but that's a stupid solution :/ I like when it goes to standby mode and in 3 hours to hibernation. It makes sense.

The biggest problem for me is that wakes up when my mac is on the cover in my bag and it almost burned!!

Hope Yosemitee will resolve this but it is still too far..

Jun 15, 2014 11:13 PM in response to rcolonescu

"Wake reason ?" issue is still not resolved for me after the recently released MBA firmware upgrade. Avast is not installed.


Ubuntu here I come...


16/06/14 04:52:40.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 673 us

16/06/14 04:52:40.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:53:05.000 kernel[0]: Wake reason: ?

16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:53:05.000 kernel[0]: AppleCamIn::wakeEventHandlerThread

16/06/14 04:53:05.000 kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Host

16/06/14 04:53:05.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 180466 us

16/06/14 04:53:05.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 2 milliseconds

16/06/14 04:53:05.000 kernel[0]: ARPT: 111987.630522: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

16/06/14 04:53:05.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:53:05.000 kernel[0]: AppleCamIn::wakeEventHandlerThread

16/06/14 04:53:10.000 kernel[0]: AppleCamIn::handleWakeEvent_gated

16/06/14 04:53:10.000 kernel[0]: AppleCamIn::handleWakeEvent_gated

16/06/14 04:53:57.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:53:58.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 673 us

16/06/14 04:53:58.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:54:23.000 kernel[0]: Wake reason: ?

16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:54:23.000 kernel[0]: AppleCamIn::wakeEventHandlerThread

16/06/14 04:54:23.000 kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Host

16/06/14 04:54:23.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 181174 us

16/06/14 04:54:23.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 2 milliseconds

16/06/14 04:54:23.000 kernel[0]: ARPT: 112066.069968: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

16/06/14 04:54:23.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:54:23.000 kernel[0]: AppleCamIn::wakeEventHandlerThread

16/06/14 04:54:28.000 kernel[0]: AppleCamIn::handleWakeEvent_gated

16/06/14 04:54:28.000 kernel[0]: AppleCamIn::handleWakeEvent_gated

16/06/14 04:55:15.000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

16/06/14 04:55:16.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 703 us

16/06/14 04:55:16.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 0 milliseconds

Dec 23, 2014 8:00 AM in response to paulmeyers42

Changing the sleep modes fixed this for me under Mavericks. There's been a bunch of people offering different settings but this is what did it for me:


sudo pmset -b standby 0

sudo pmset -b standbydelay 0

sudo pmset -b hibernatemode 25


Under Yosemite, the default settings seems to work okay and I have not experienced the problem again. This is also while running Avast and other background daemons.

Mar 13, 2015 10:59 PM in response to spmudiraj

Thanks for all the tips. With my MacBookPro, the problem now seems to be resolved. I followed a variety of tips and let the computer alone over the night in standby. This morning I reopened it and battery was still at 100% - great. Before that, the battery would have been at 10%, the laptop would have been very warm from all the wakes.

What I did:

  • Uninstall XQuartz
  • sudo pmset -a standby 0
  • sudo pmset -a standbydelay 0
  • sudo pmset -a hibernatemode 0 (I do not want SafeSleep - this simply writes 8GB to my flash and takes a lot of time)

Here are my current settings:

pmset -g

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

standbydelay 0

standby 0

womp 0

halfdim 1

hibernatefile /var/vm/sleepimage

darkwakes 0

networkoversleep 0

disksleep 10

sleep 1

autopoweroffdelay 14400

hibernatemode 0

autopoweroff 1

ttyskeepawake 1

displaysleep 10

acwake 0

lidwake 1

MBA mid-2013 wakes from sleep every minute on Mavericks

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.