Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Liberty.

macrumors 6502
Original poster
Sep 13, 2008
266
2
Already disabled powernap and looked for a solution utilizing Google, couldn't figure anything out.

What do I do now?

I use the latest Yosemite-version.
 
How about shutting it down completely at night? That's what I do.
That shouldn't be necessary with a Mac. I never do. And it does not discharge overnight.
There must be something keeping the machine spinning at load. I would start at checking the CPU load.
 
That shouldn't be necessary with a Mac. I never do. And it does not discharge overnight.
There must be something keeping the machine spinning at load. I would start at checking the CPU load.

I always shut it down in case of a power failure and for security. In sleep mode, if I remember right, the drive remains partially decrypted (I've FV2 enabled).
 
OK. I am not concerned about this and don't have anything on my laptop that would call for disk encryption.

My job as a software developer is in an environment where XTS-AES 128 is the absolute minimum encryption standard.

Most of my stuff is AES-256 encrypted.

Meanwhile, my cinematography job doesn't require encryption of that standard, but I still use it anyway to prevent leakages.

And honestly, you should seriously consider encrypting your drive even if you couldn't give a bloody toss about security. FileVault is easy to use, and besides the performance hit is negligible, and especially less so with an SSD.
 
That shouldn't be necessary with a Mac. I never do. And it does not discharge overnight.
There must be something keeping the machine spinning at load. I would start at checking the CPU load.

But its a good diagnostic, it will seperate machine running being the cause from battery self-discharge for example
 
Your MacBook is definitely not sleeping--and something is keeping it from sleeping--and using a lot of CPUs if your laptop is dead in the morning. In sleep mode, you should only lose a few percentage points overnight.
 
Already disabled powernap and looked for a solution utilizing Google, couldn't figure anything out.

What do I do now?

I use the latest Yosemite-version.

Does it go into sleep normally? If the magnet/sensor in the screen isnt working then it wont sleep when you shut the lid (as it doesn't know the screen is shut).
 
Close every program and remove all cables/devices before putting it to sleep and see if that solves the problem. It could be that the computer doesn't actually sleep, or it is trying to charge a device that is plugged in.
 
10.02.15 17:51:37,000 kernel[0]: Wake reason: EC.LidOpen XHC1 (User)
10.02.15 17:51:37,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320
10.02.15 17:51:37,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 17:51:37,000 kernel[0]: AppleCamIn::wakeEventHandlerThread
10.02.15 17:51:37,000 kernel[0]: AppleThunderboltNHIType2:rePCIWake - power up complete - took 2 us
10.02.15 17:51:37,000 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 12 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
10.02.15 17:51:37,005 discoveryd[53]: Basic DNSResolver UDNSServer:: PowerState is Wakeup
10.02.15 17:51:37,000 kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 1 milliseconds
10.02.15 17:51:37,000 kernel[0]: The USB device Card Reader (Port 4 of Hub at 0x15000000) may have caused a wake by being disconnected

10.02.15 17:57:20,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 17:57:21,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 17:57:40,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000280
10.02.15 17:57:40,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 17:57:40,000 kernel[0]: AppleThunderboltNHIType2:rePCIWake - power up complete - took 3 us
10.02.15 17:57:40,000 kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 0 milliseconds
10.02.15 17:57:42,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 17:57:42,000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
10.02.15 20:57:43,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
10.02.15 20:57:43,000 kernel[0]: AppleCamIn::wakeEventHandlerThread
10.02.15 20:57:43,000 kernel[0]: AppleThunderboltNHIType2:rePCIWake - power up complete - took 1 us
10.02.15 20:57:43,000 kernel[0]: The USB device Card Reader (Port 4 of Hub at 0x15000000) may have caused a wake by being disconnected

11.02.15 02:04:04,000 kernel[0]: full wake request (reason 1) 18381929 ms
11.02.15 02:04:04,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320
11.02.15 02:04:04,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
11.02.15 02:04:04,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
11.02.15 02:04:04,000 kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000300
11.02.15 02:04:04,586 sharingd[266]: 02:04:04.586 : Starting AirDrop server for user 501 on wake

I didn't even touch the device during this time.
 
Was that with no devices plugged into the USB or TB ports?

Only point of near-commonality between those errors is they are USB devices (internal kb and SD slot are on the internal USB hub). I don't know if the lid shut sensor is also USB but I would have thought not.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.