Güni wrote:
Solved with workaround!?
Deactivated the power nap function in system preferences last evening and had not a single crash over night!
I'm going to try this, but I bet this is a solid workaround. I've crashed 3 times in the past 10 days. Each time, a "Sleep Wake Failure" log has been left in /Library/Logs/Diagnostic Reports. Checking /var/log/system.log shows an attempt to wake up (which I now realize is power nap) and looks like:
Apr 28 00:10:47 Matthews-MacBook-Pro kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
Apr 28 00:10:47 Matthews-MacBook-Pro kernel[0]: Previous Sleep Cause: 5
Apr 28 00:10:47 Matthews-MacBook-Pro kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
It goes on to have a lot of errors (a few pages full), and then appears to decide to reboot:
Apr 28 00:12:30 Matthews-MacBook-Pro kernel[0]: process powerd[16] caught causing excessive wakeups. Observed wakeups rate (per sec): 436; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 65479
Apr 28 00:12:30 Matthews-MacBook-Pro.local ReportCrash[15845]: Invoking spindump for pid=16 wakeups_rate=436 duration=104 because of excessive wakeups
Apr 28 00:13:04 Matthews-MacBook-Pro kernel[0]: process Dropbox[454] caught causing excessive wakeups. Observed wakeups rate (per sec): 794; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 318881
Apr 28 00:13:04 Matthews-MacBook-Pro.local ReportCrash[15849]: Invoking spindump for pid=454 wakeups_rate=794 duration=57 because of excessive wakeups
Apr 28 00:13:52 Matthews-MacBook-Pro.local G2MUpdate[15850]: G2MUpdate activated at 2014-04-28 06:13:52 +0000
Apr 28 00:13:52 Matthews-MacBook-Pro.local G2MUpdate[15850]: Next Update Check at 2014-04-29 09:28:18 +0000
Apr 28 00:15:28 Matthews-MacBook-Pro.local fseventsd[64]: SLOWDOWN: client 0x7ffd92808c00 (pid 246) sleeping due to too many errors (num usleeps 15)
Apr 28 00:16:45 localhost bootlog[0]: BOOT_TIME 1398665805 0
It's possible here that it isn't intending to event actually reboot since it does say "sleeping due to too many errors (num usleeps 15)"; which I'd translate into power nap deciding to give up and go back to sleep, but then 75 seconds later, it boots cold (easy to tell because it has lost its hostname that early in the boot process).
Anyhow, thanks for posting, and hopefully apple can find the issue with power nap soon. Neat idea.