3

My MacBook Air (a few months old) randomly wakes from sleep roughly 3 hours after the lid is closed. The wake reason is given as EC.LidOpen, but in fact, the lid remains closed. The mac appears to go immediately back to sleep. I am not experiencing any negative consequences from this, but wanted to be sure I shouldn't be worried about malware.

For example (this occurs every night)

log show --style syslog | fgrep "Wake reason"

2017-03-18 01:33:44.916848+0100 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.SleepTimer (SleepTimer)

2017-03-18 04:33:58.836023+0100 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.LidOpen (User)

EDIT: using pmset -g log, I got more information on the mysterious wake-ups, which seem to be caused by mDNSResponder.

2017-04-14 10:23:12 +0200 Kernel Client Acks Delays to Sleep notifications: [AppleBacklightDisplay driver is slow(msg: SetState to 0)(984 ms)] [powerd is slow(16830 ms)] [AppleThunderboltNHIType2 driver is slow(msg: WillChangeState to 2)(361 ms)] [RP03 driver is slow(msg: SetState to 0)(1277 ms)]
2017-04-14 10:23:12 +0200 Assertions PID 173(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000806d [System: DeclUser kDisp]
2017-04-14 10:23:12 +0200 Assertions PID 173(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000806d [System: DeclUser kDisp]
2017-04-14 10:23:12 +0200 DarkWake DarkWake from Deep Idle [CDN] due to EC.SleepTimer/SleepTimer: Using BATT (Charge:81%) 0 secs
2017-04-14 10:23:12 +0200 HibernateStats hibmode=3 standbydelay=10800 741
2017-04-14 10:23:12 +0200 Kernel Client Acks Delays to Wake notifications: [SSP3 driver is slow(msg: SetState to 3)(405 ms)] [SSP3 driver is slow(msg: DidChangeState to 3)(373 ms)]
2017-04-14 10:23:12 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep': Using Batt (Charge:81%) 1189 secs 2017-04-14 10:23:40 +0200 PM Client Acks Delays to Sleep notifications: [AirPort configd plug-in is slow(1835 ms)] [com.apple.apsd timed out(28012 ms)]

Edit:

 energy saver preferences on battery:
-turn display off after 15 minutes
-put hard disks to sleep when possible
-slightly dim the display when on battery power
-(power nap unchecked)

Power adapter:
-turn display off after 15 minutes
-prevent computer from sleeping automatically when the display is off
-put hard disks to sleep when possible
-(wake for wi-fi network access unchecked)
-(power nap unchecked)

One more edit: Noticed the 10800 here is exactly 3 hours! Is that a coincidence? Does anybody know how to read/change these settings? This is in response to pmset -g

System-wide power settings:
Currently in use:
 standbydelay         10800
 standby              1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 powernap             0
 gpuswitch            2
 disksleep            10
 sleep                15 (sleep prevented by coreaudiod)
 autopoweroffdelay    28800
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         15
 acwake               0
 lidwake              1
  • Check to see if Power Nap is enabled. – IconDaemon Apr 13 '17 at 21:03
  • @IconDaemon currently disabled, should I turn it on? – hunter Apr 13 '17 at 21:29
  • 2
    No. Enabling it would wake it from sleep. I was just wondering if Power Nap was the cause of the problem. It wouldn't hurt to enable Power Nap, close System Preferences, re-open System preferences then disable Power Nap. Sometimes making changes like this can fix a corrupted .plist file. The SMC reset was my next suggestion, but Monomeeth beat me to it. – IconDaemon Apr 13 '17 at 23:51
  • 1
    Well the 10800 value is fairly standard, but that doesn't mean it's not related to what's going on. Try changing the value by entering this command in the terminal: sudo pmset -a standbydelay 3600 - this will change it to 60 mins (i.e. the 3600 seconds). Then test your MBA to see if the behaviour continues and, if so, whether it's at 3hrs or 1hr. By the way, I hadn't forgotten about this - I've been trying to replicate it on a machine here, but haven't been able to do so. It's not, however, something I think you need to be concerned about (if that makes you feel any better). :) – Monomeeth Apr 18 '17 at 22:50
  • 1
    Okay, that's all to be expected. If you wanted, as another test, you could disconnect from the internet altogether prior to putting it to sleep to see whether it still reawakens. – Monomeeth Apr 19 '17 at 12:40
2

It may be worth resetting your System Management Controller (SMC) to see if this resolves this behaviour.

To do this on your MacBook Air follow these steps:

  1. Shut down your Mac
  2. Keep the MagSafe adapter (power cable) plugged in.
  3. Press at the same time shiftoptioncontrol (on the left side of the bult-in keyboard) and the power button
  4. Let go
  5. Turn your Mac back on with the power button.

Let me know how you go.

Boot into Safe Mode

Since resetting the SMC didn't resolve this for you, I'd test to see if this still happens when booted into Safe Mode. To do this, follow these steps:

  1. Fully shut down your Mac
  2. Restart your Mac
  3. Immediately press the Shift key and keep it down
  4. Let go of the Shift key when you see the login window (NOTE: If you have FileVault enabled you may need to log in twice).
  5. Take a note of what happens (i.e. Close the lid and check again to see if it still wakes up 3hrs later)
  6. Exit Safe Mode by restarting your Mac as normal

Run Apple Diagnostics

Now that we've established Safe Mode makes no difference and resetting the SMC didn't help, it's time to test your Apple hardware. Your model of MacBook Air uses Apple Diagnostics to do this. Follow these steps:

  1. Fully shut down your Mac
  2. Restart your Mac
  3. Immediately press the D key and keep it down until you see the Diagnostics screen appear
  4. Wait for Diagnostics to finish (this typically only takes a few minutes)
  5. Once complete, one of two things will appear on the screen:
    • a No issues found message
    • a brief description of any errors found plus further instructions
  6. If the diagnostics test does find errors, take a note of what they are

Note: If pressing and holding the D key at Step 3 doesn't work, start again at Step 1 and, at Step 3 press and hold both the OptionD keys instead. This will try and run diagnostics from the internet instead, so you will need to allow more time for it to complete.

Regardless, take a note of what happens and let me know how you went.

  • Thanks for the tip! I've just reset the SMC; we'll see if the mac wakes up tonight or not. – hunter Apr 13 '17 at 22:34
  • Didn't seem to work. 2017-04-14 00:56:47.400087+0200 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.SleepTimer (SleepTimer) 2017-04-14 03:57:24.258265+0200 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.LidOpen (User) – hunter Apr 14 '17 at 5:02
  • 1
    I've just updated my answer to include steps for booting into Safe Mode. Try this and let me know how you go. – Monomeeth Apr 14 '17 at 5:10
  • thanks! It still woke up 3 hours later, even in Safe Mode. 2017-04-14 07:23:13.661906+0200 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.SleepTimer (SleepTimer) 2017-04-14 10:23:47.385436+0200 localhost kernel[0]: (AppleACPIPlatform) Wake reason: EC.LidOpen (User) – hunter Apr 14 '17 at 8:48
  • 1
    Time to run Apple Diagnostics to test your Apple hardware. See my updated answer for instructions. – Monomeeth Apr 14 '17 at 9:42

You must log in to answer this question.

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