El Capitan Wakes From Sleep

Hi all,

Adding to this thread so I can get email reminders to update you.

I'm having the same issue as well where I'm assuming it isn't actually sleeping - I went to bed with a 50% battery (probably around 3:30pm when I shut the lid) and came to work with a completely dead 2015 Macbook Pro. I haven't noticed abnormal heating through my backpack (tech bag) but also I don't have it on me constantly. I'll fully charge it and see how far it drains the battery tonight.

SO many bugs between El capitan and the new ios. I wonder if the apple employees at HQ are annoyed too...

Same issue here on a late 2008 MB Pro w/ El Cap. I noticed it work up last night. I'll try messing with the WiFi to see if it's the same issue for this generation machine.

I also noted that I had "WAKE for NETWORK ACCESS" checked in my energy saver power adapter options. I've unchecked that, perhaps that was at the root?

Regards,

HB

Hey all,

So there was another thread on this (but I can't find it now) basically saying the same things.

I ran a couple of tests over a couple of days on BATTERY (not plugged in), and the general consensus from me and the other thread:

• It's a Wifi issue and not a bluetooth or combination of both.
  • The first day, I turned off just bluetooth - still drained the battery. The second day, I turned off both BT and Wifi and it let my computer sleep.
  • The third day, I turned off just Wifi and it still let my computer sleep.
• Forcing the computer into sleep (not shutting the lid but going from the Apple menu) allowed me to watch for the screen to pop on.

  **Note, I do NOT have Power Nap enabled on Battery. It IS enabled on Power Adapter. Further tests should probably be to shut this off in both places and try again.

• Every time I got an email, text, or push notification, the laptop screen popped back on with the notification box. This leads me to believe it has to do with more developers using the notification system and Apple didn't find the loophole to sleep mode before releasing El C.

I have similar issue. I have found that after charging my 15" 2013 MBP in the evening to 100% and putting the MBP to sleep, the next morning the battery is dead and the system has had a reboot.

Same here, Macbook Pro 13 mid 2015. Since upgrading to El Capitan the back is warm in the morning after it has been to sleep at night and battery has drained a lot.

The output of syslog |grep -i "Wake reason" gives lot of these messages:

Oct 7 07:20:47 Marks-MacBook-Pro kernel[0] <Notice>: Wake reason: ARPT (Network)

Oct 7 07:20:47 Marks-MacBook-Pro kernel[0] <Notice>: ARPT: 69953.346965: ARPT: Wake Reason: Wake on excessive wake

Oct 7 07:20:47 Marks-MacBook-Pro kernel[0] <Notice>: ARPT: 69953.587548: ARPT: Wake Reason: Wake on excessive wake

Oct 7 07:20:47 Marks-MacBook-Pro kernel[0] <Notice>: [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)

Oct 7 07:21:19 Marks-MacBook-Pro kernel[0] <Notice>: Wake reason: ARPT (Network)

Oct 7 07:21:19 Marks-MacBook-Pro kernel[0] <Notice>: ARPT: 69986.224200: ARPT: Wake Reason: Wake on excessive wake

Oct 7 07:21:19 Marks-MacBook-Pro kernel[0] <Notice>: ARPT: 69986.465081: ARPT: Wake Reason: Wake on excessive wake

Oct 7 07:21:19 Marks-MacBook-Pro kernel[0] <Notice>: [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)

Same here. New 2015 mac book pro. two nights in a row completely dead in the morning, lots of logs...

Oct 8 00:15:59 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6342.289402: ARPT: Wake Reason: Wake on excessive wake

Oct 8 00:15:59 Stevens-MacBookPro kernel[0] <Notice>: [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)

Oct 8 00:16:36 Stevens-MacBookPro kernel[0] <Notice>: Wake reason: ?

Oct 8 00:16:36 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6375.129150: ARPT: Wake Reason: Wake on excessive wake

Oct 8 00:16:37 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6376.014826: ARPT: Wake Reason: Wake on excessive wake

Oct 8 00:16:37 Stevens-MacBookPro kernel[0] <Notice>: [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)

Oct 8 00:17:12 Stevens-MacBookPro kernel[0] <Notice>: Wake reason: ?

Oct 8 00:17:12 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6408.234110: ARPT: Wake Reason: Wake on excessive wake

Oct 8 00:17:12 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6408.516374: ARPT: Wake Reason: Wake on excessive wake

Oct 8 00:17:12 Stevens-MacBookPro kernel[0] <Notice>: [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)

Oct 8 00:18:16 Stevens-MacBookPro kernel[0] <Notice>: Wake reason: ?

Oct 8 00:18:16 Stevens-MacBookPro kernel[0] <Notice>: ARPT: 6468.713118: ARPT: Wake Reason: Wake on excessive wake

Oct

I ran "syslog | grep -i "Wake reason" " which yielded this:

Oct 8 08:06:12 kevinfoustsMBP kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:07:22 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:08:35 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:09:47 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:10:57 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:12:06 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Oct 8 08:13:20 kevin-fousts-macbook-pro kernel[0] <Notice>: Wake reason: EHC2

Time after time every two minutes or so the MB Pro would wake up. I've been trying to find out what EHC2 is and haven't had any luck.

I did find in another forum the possibility that the bluetooth was waking it up. So I did this: Uncheck "Allow bluetooth devices to wake this computer". It's under System Prefs, Bluetooth, Advanced. I'll see if this takes care of the sleepless MB Pro. It seems plausible, we have a ton of bluetooth devices around...

fierlessj316experiments are interesting. They got me looking at my notification center. I do have Do Not Disturb turned on from 10pm to 7am. I hadn't noticed any unusual notification activity, but I'll keep an eye out for that now.

I have also found some speculation about a Chrome helper causing this issue. I have been using Chrome, and often leaving it open when I put the MB to sleep. I'll give this a test to see what happens.

Regards,

HB

PS - Disabling "WAKE for NETWORK ACCESS" had no impact on this issue.

I am having the same issue. I have a 15" mid 2015 macbook pro running El Capitan OS. With Yosemite i didn't have this problem. I close the lid and it acts as though it goes to sleep. When really it just runs I suppose and if I leave it in my computer bag it will get very hot because of no ventilation. I too am worried about damage from heat. Im not sure if it is all the new tech, but in the old days of Apple everything just worked, including updates and new OS Software. Now things seem more buggy than Windows/ PC. Wish I had an answer to this problem.

Same issue here on my MBP (specs below).

I took it out of my bag today at work and it was steaming hot, like it had been running for hours in my bag. I have no idea what is causing this. I have tried turning off Bluetooth and Wi-Fi altogether before sleeping the machine and it still happens.

MacBook Pro (Retina, 15-inch, Mid 2015)

2.5 GHz Intel Core i7

16 GB 1600 MHz DDR3

AMD Radeon R9 M370X 2048 MB

Same problem here , mac pro 2008 , updated to el capitan.

When i hit stop it go down for 10 seconds then restart , in log there is: "Wake reason: ?".

any hint ?

A similar thread has emerged elsewhere: Wake on Excessive Wake drains battery on sleep.

Hello All,

Since I last posted, I’ve been through a number of troubleshooting iterations.

I followed this set of instructions for disabling and re-enabling the address book sync and caching functions.

https://discussions.apple.com/thread/5565445

It had no impact on the wakeup issue.

I turned of (disabled) my time machine even though the drive wasn’t attached when the wake-up problem happened.

It had no impact on the issue.

I tried booting and putting the MAC back to sleep in SAFE MODE (hold down the shift key while the MAC boots to enter SAFE MODE) which had no effect; the MAC kept waking up.

I searched through tons of threads on the web, you’ll find them too if you search a little.

It appears now that it was my PCI Express card which provides a SD card interface for my machine. The hint was right in front of me, it was in this section of my pmset log which cycled about every 45 seconds waking then allowing the MAC to sleep, then waking it again,…:

2015-10-18 11:04:55 -0700 DarkWake DarkWake [CDN] due to EHC2

and here:

Kernel Assertions: 0x4=USB

id=501 level=255 0x4=USB mod=12/31/69, 4:00 PM description=com.apple.usb.externaldevice.26300000 owner=USB Storage

The PCI card is shown under my MAC’s system information as: Location ID: 0x26300000 / 1 which matches the above kernel assertion.

There isn’t much specific info on EHC2 on the web but I learned that it has to do with the USB, or perhaps some other bus on the MAC.

Even though I hadn’t changed anything on the PCI card in years, I decided to remove it from the machine and put the MAC to sleep.

***********************

Here’s the PMSET -g log excerpt from the last test is below. Basically I put the MAC to sleep at 11:25:51. It remained in sleep mode until I woke it up at 20:28:33 :

Time stamp Domain Message Duration Delay

========== ====== ======= ======== =====

UUID: 393A74EC-A1DD-466F-9AFC-6532481111AB

2015-10-18 11:25:51 -0700 Notification Display is turned off

2015-10-18 11:25:51 -0700 Assertions PID 101(hidd) Summary UserIsActive "com.apple.iohideventsystem.queue.tickle" 00:02:28 id:0x0x900000176 [System: DeclUser kDisp]

2015-10-18 11:25:51 -0700 Assertions Kernel Idle sleep preventers: -None-

2015-10-18 11:25:52 -0700 Sleep Entering Sleep state due to 'Clamshell Sleep': Using AC (Charge:95%) 32568 secs

2015-10-18 11:25:57 -0700 PM Client Acks Delays to Sleep notifications: [com.apple.apsd is slow(5094 ms)]

2015-10-18 20:28:33 -0700 Kernel Client Acks Delays to Sleep notifications: [NVDATesla driver is slow(msg: SetState to 1)(1038 ms)] [powerd is slow(5128 ms)] [AppleAHCIDiskQueueManager driver is slow(msg: SetState to 0)(738 ms)]

2015-10-18 20:28:33 -0700 Assertions Kernel Idle sleep preventers: IODisplayWrangler

2015-10-18 20:28:33 -0700 Notification Display is turned on

2015-10-18 20:28:33 -0700 Assertions PID 93(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000025f [System: DeclUser BGTask SRPrevSleep kCPU kDisp]

2015-10-18 20:28:33 -0700 Assertions PID 93(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000025f [System: DeclUser BGTask kDisp]

2015-10-18 20:28:40 -0700 Wake Wake [CDNVA] due to EC LID0/HID Activity: Using AC (Charge:100%)

2015-10-18 20:28:40 -0700 Kernel Client Acks Delays to Wake notifications: [en0 driver is slow(msg: DidChangeState to 1)(441 ms)] [NVDATesla driver is slow(msg: SetState to 2)(586 ms)] [NVDATesla driver is slow(msg: SetState to 2)(425 ms)] [PRT1 driver is slow(msg: SetState to 2)(925 ms)] [AppleHDADriver driver is slow(msg: SetState to 1)(2610 ms)]

Total Sleep/Wakes since boot at 2015-10-18 11:22:55 -0700 :1

************************

For now, I am considering my issue tracked down and solved. I’ll work on resolving the PCI card issue. I suspect that something in the handling of the interface has changed with El Capitan 10.11 since this issue emerged after I installed El Cap.

Thanks for all the help and best luck in solving your sleep issues!

As mentioned by "dub danger", we also have a similar issue but with MBP mid 2015Wake on Excessive Wake drains battery on sleep. I notice "Kernel Idle sleep preventers: IODisplayWrangler", which was what I got what I typed "pmset -g assertions". I also found a few threads on that message but no one seemed able to explain it. Does it have anything to do with the wake issue?

I had the same issue. Thought it's some service trying to sync every time. But then I found it's the nano receiver of the wireless mouse waking laptop every time during sleep. I removed it and let it sleep overnight. Didn't notice a drastic drain.