You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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 Top-ranking 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

Mar 16, 2014 10:20 AM in response to rcolonescu

Hi, I just bought my rMBP a week ago, two days ago I was normally using the machine and then after a while I plug the cord and charge the device to 100%, after that I unplugged the cord and put it to sleep for like 16 hrs, when I woke up the computer it has 34% of battery left, this didnt look ok, so I decided to run some kind of test, so yesterday I charged the machine to a 100% and put it to sleep (unplugged) for like 15 hrs, and this morning when I woke up the computer again, the battery was 49%, I think this should not be happening, and as im within my 14 days, I want to know if I had some bad machine so i can take it back, or its a software proeblem that I can fix or some bug from Mavericks. Im also noticing that my battery runs out very fast after this..

Mar 16, 2014 7:28 PM in response to sunQH

Perhaps for some Parallels is the culprit, but not for all. I have never had parallels installed and this it could have been 'the true reason' for my issue. I did resolve my issue some time ago in the steps I outlined in an earlier post and have not had trouble since.



For those stating that the fix is to then off the deep sleep, that is not a solution, that is a work around and for many of us we want to use the included hibernation functionality of our Macs.



For the record, I'm certain my issue started after xquartz was installed, but I resolved the issue by adjusting the times for my display sleep and sleep so the one did not occur before the other and have not had this issue since. I do hope Apple puts out a fix for this and other issues soon and hope those of you battling the issue for various reasons find your own solutions or benefit from a fix.

Mar 16, 2014 10:03 PM in response to sunQH

I have had this issue with completey stock systems with nothing installed. In general, disabling deep sleep (hybernate) with 'sudo pmset -b standby 0' fixes the problem for most people. The issue appears to be rooted in the Mavericks power management kernel and how it interacts with certain chipsets. The more recent chipsets seem to be the ones affected. My late 2012 MBP 15", for example, does not have this issue with VMWare or Parallels running during sleep. However, my late 2013 MPB 13" without a VM does have this issue. Disabling sleep on the latter system allows it to sleep properly 95% of the time, but it still wakes up once or twice a month and exhausts the battery.

Mar 17, 2014 4:45 PM in response to rcolonescu

I think I found my particular issue.


Parallels was not identifying itself as a laptop to the Windows VM. Once I shutdown Windows I was able to go into the VM configuration, then the optimize section and enable the box to show battery status in Windows. This let Windows configure different AC power settings and battery power settings. I set both battery and AC power on Windows to sleep 1 minute before the Mac pmset standbydelay setting. (i.e. on battery Windows sleeps after 5 minutes and Mac goes to standby after 6 minutes). I also set Windows to hibernate when battery drops to 15% that way the Mac has time to hopefully go to standby before the battery is totally dead.


I'll update after I've tested a bit.

Mar 20, 2014 10:26 PM in response to frame_of_mind

Follow up to my last post. My MBA is no longer waking every minute! The only change I made was to shut off Parallels whenever I was done using my MBA. That way, Parallels would not be running in the background while my MBA was sleeping. And I've been completely free of the issue for all of last week.


I imagine that there's a conflict between the Windows sleep/hibernate system and the OS X sleep/hibernate system. OS X wants to hibernate, but for whatever reason, Parallels/Windows doesn't allow it.


Now I'm going to try some ot the Parallels-related solutions that the other users post. Maybe even report the issue to Parallels themselves. They are very good about fixing to user-reported bugs.

Mar 21, 2014 4:18 PM in response to rcolonescu

So Parallels support asked me to submit a problem report from the software and they took details on my pmset configuration as well as Windows settings. Then I get this lovely reply


We have escalated this issue to our Development Team for further investigation. They are continually working on issues that are escalated from our Support Team, however do not share an ETA for a fix until one is available.



If a fix is available it will be included in an upcoming software update. To enable automatic updates, from the Parallels Desktop Menu, select Preferences > General > Download Updates Automatically.



Since this issue has been escalated to our Developers Request Tracking tool, and is no longer being worked on by Parallels Support, we will be marking this support ticket as 'resolved'. The Development Team does not provide individual updates but if additional information is required or a workaround becomes available shortly, Parallels will contact you directly. At this time, no additional actions are required from you.



Needless to say, I'm not impressed with their support, and I have not heard from their development team about an upcoming fix for this. It sounds like they are aware of the problem because there was zero troubleshooting done and this is the most non-automated reply I got from them the entire time.


I, like many, have taken to either shutting down Parallels when I remember, or just accepting that my battery will be dead in a few hours. This is very frustrating and their software is not operating as advertised. Seamless integration to me would mean when I sleep the computer, it actually goes to sleep. With their software running I do not get the expected result, and the VM operates very different from the host.


I am looking into VMWare Fusion since we may already have licensing in our company, and it can't be any worse at sleeping the computer. If it weren't for the crappy job Microsoft did with Office for Mac, or the lack of HTML support in the existing Apple Mail application I wouldn't need Windows/Office on my computer to begin with.

Mar 21, 2014 6:21 PM in response to falterego

Not to derail your issue, but this thread was originally about late 2013 MBP 13 and Airs without a specfic VM going dead with Mavericks. Perhaps you should open a new thread related to issues specific to Parallels as it sounds like you have a specific related issue.


For reference, I run VMWare and my MBP 15 (late 2012), sleeps just fine with the VM running and the with Windows power config set to the default behaviour. I pass the battery info to the VM in the VM configuration. I can't speak to the MBA, but assuming it is the VM, you might want to give the trial VMWare a try. Note that I had used Parallels in the past on the same MBP15 computer but did not experience your particular problem. However, that was under Lion and Mountain Lion.


It is possible that there is a specific conflict with Parallels and Mavericks, and from the sound of it, you have identified it. Does your log support the fact that the VM is causing the machine to wake and provide any details?

Apr 2, 2014 7:13 PM in response to Liquid.Phynix

I have been reading through this thread the past few days now and I think I finally have a solution or at least a workaround for my specific circumstances. I followed the info from Liquid.Phynix and change my standby mode

to 0. All this really does is bypass regular sleep when closing the lid. I have my hibernate set to 3, so when I close the lid the system creates the wake image on the disk and keeps an image in the RAM to boot from when I open the lid. Bypassing the regular sleep mode isnt an issue for me because even when waking from deep sleep(hibernate) the system still comes up instantaneously like is would from regular sleep. This is because my MacBook Air (mid2013) has the PCIe based flash storage that is super quick. This configuration also has the benefit of lower power consumption during the sleep cycle and the moment is falls alseep is saves the wake image to the disc just in case there is a loss of power. Using the pmset standby 0, I have had no issues for 2 days now. And to clarify, I have left; dropbox, onedrive, google drive, avast antivirus, and mail; all running when I put the system to sleep on battery power. This is a super easy solution worth a shot. just open terminal and type the following:


sudo pmset -a standby 0


granted this is a work around and the problem still remains but with this configuration its completely tolerable until APPLE gets it together on this one.

Apr 4, 2014 5:53 AM in response to rcolonescu

It just happened to me as well. I have a 13" rMBP late 2013 model running 10.9.2 with all updates installed. As reported by other people here, the laptop woke up after 3 hours on standby in order to hybernate but ended up in an infinite darkwake loop with the wake reason unknown, i.e. "kernel[0]: Wake reason: ?"


The laptop was disconnected from the power source and from all external devices. Bluetooth was off. Powernap was off as well. I don't run any AV software. I installed XQuartz well before this occurrence of insomnia, so it shouldn't be a problem in itself. However, I installed Inkscape and Tablet the day before. Being a Java application, Tablet probably has nothing to do with it. Inkscape on the other hand was mentioned before in this thread. Nevertheless, at the time of sleep the only running applications were Thunderbird, Firefox, and Skype.


For now, I just changed the sleep value from 1 to 12 in both battery and AC profiles. I will post again if I discover anything interesting.

May 9, 2014 10:19 AM in response to rcolonescu

I have the same problem, and nothing seems to wake up the computer consistently to drain battery.


Then I have done what Liquid.Phynix said on page 6. That seems to solve the problem. But I think it is not a good solution, as your computer always goes to hibernation when you disable standby.

This is not a good thing if you use ssd. SSDs are not good with constant writing operations. Everytime you hibernate, you unnecessarily create a file that is around 4 Gbs. This happens because contents of ram is copied to Harddrive.


I want to have a case where the computer goes to standby, and only after a couple of hours it goes to hibernation. Can anyone tell me if it is possible to do that.

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 Account.