Q: My late 2013 15" MacBook Pro Retina occasionally does not wake up when lid is opened.
-
Jan 10, 2014 1:01 PMby Supreem,Thanks for clearing up my confusion with your previous post pal.
For the issue to occur on all the 3 MacBooks you've had I'm starting to wonder if this problem is related to a piece of software that we have installed on our laptops causing them to not sleep properly when that said piece of software is left open when putting the MBP to sleep. Just a thought anyway.
-
Jan 10, 2014 1:47 PMby Supreem,Based on the fact you've had 3 MBP's and still have this problem I'm going do a test from now on whereby I shall be putting my MBP to sleep at night as usual by closing the lid but from now on I will be shutting down every single app so there's nothing left running, if I can go 4 weeks without any sleep/wake up issues then at least then I can put it down to a conflict between the MBP and one of the apps I have on it.
-
Jan 11, 2014 3:37 AMby pippatron,For that reason when i got my third MBP i did not install from backup i started from scratch did the updates, configured email account/ web favourites and instaled a few mac apps Numbers etc other than that it is pretty much bare bones. i have virtualy nothing installed other than the OS.
Strangely enough it woke from sleep fine this morning.
I am not replacing mine anymore, I guess for now i will just have to live with it and hopefully a fix will come in time.
-
Jan 14, 2014 1:39 AMby McPerlt,I have been in online chat with Apple Support. They suggested that it might be a program or process in either login items (in System Settings - User Accounts) or in the LaunchAgents folder in Library.
The Apple Support agent supposed that it was a piece of (3rd party) software preventing the MBP from waking after sleep.
After having looked through these items and removed a few, the problem persists, though.
I'd be interested to know what you all have in your Startup Items and LaunchAgents folder. Here's mine:
Startup Items:
Skype
Dropbox
LaunchAgents:
com.adobe.ARM.202f4087f2bbde52e3ac2df389f53a4f123223c9cc56a8fd83a6f7ae.plist
com.macpaw.CleanMyMac2Helper.diskSpaceWatcher.plist
com.macpaw.CleanMyMac2Helper.scheduledScan.plist
com.macpaw.CleanMyMac2Helper.trashWatcher.plist
com.valvesoftware.steamclean.plist
ws.agile.1PasswordAgent.plist
-
Jan 14, 2014 1:45 AMby Supreem,I can confidently confirm that (at least for me) the sleep crash issue is not due to 3rd party apps being launched or being left running when being put to sleep.
For the last few days I have 'quit' all applications down before closing the lid of my rMBP and this morning the same crash has occurred causing me to once again perform a hard shut-down and restart.
Now though I've began immediately saving the 'Console' logs that have been produced by the my rMBP when I boot-up from a crashed sleep such as today, so when I get chance to take my laptop to the Apple store I can simply say here are the system logs for this problem so get it sorted ASAP or replace my laptop.
-
Jan 14, 2014 7:38 AMby ncon64,I'm going to do the same. However, I'm going to narrow my paths to 'wake' or 'wake reason' and see what that feeds back after each sleep. So, Suprrem if you observe all logs and I observe specifics, we may be able to close in on the issue. Gosh, the things we do for Apple!!!
-
Jan 14, 2014 10:01 AMby Supreem,ncon64 wrote:
I'm going to do the same. However, I'm going to narrow my paths to 'wake' or 'wake reason' and see what that feeds back after each sleep. So, Suprrem if you observe all logs and I observe specifics, we may be able to close in on the issue. Gosh, the things we do for Apple!!!
Did you get any further on your hardware fault after the diagnostics test?
As far as the Console logs, each time it crashes when trying to hibernate and isn't able to wake-up I've noticed a definite recording of a "sleep failure" as can be seen in the screen-shot here:
Not only this but I've also noticed that when I have my headphones plugged into my rMBP and I put to sleep for say half an hour, sometimes once I wake it back up I have no sound on my rMBP at all! None in the headphones and none in the laptop speakers either, which requires a re-start to fix.
This £2k rMBP of mine is riddled with problems and I am an extremely unhappy customer, I use my laptop for work and I travel a lot so it's an absolute pain in the rear to have to send my laptop in for examination and repair/replacement, basically I lose income each day without my MacBook, all thanks this piece of junk they've sold to me. I'll be having some very strong words with Apple when I'm back in the UK next.
-
Jan 14, 2014 1:06 PMby RS1999ent,Hi,
I just wanted to chime in. My late 15" Retina macbook pro, which I just got last Monday, exhibits the same problem. Twice so far, I've come back in the morning only to find that the system has rebooted. The console log displays the following:
Jan 11 11:04:48 localhost kernel[0]: Sleep failure code 0x0000002a 0x27006900
Jan 11 11:50:45 localhost kernel[0]: Sleep failure code 0x0000002a 0x27006900
Jan 11 11:50:45 localhost kernel[0]: System was rebooted due to Sleep/Wake failure
Jan 11 11:50:49 <machine name>.local spindump[144]: Saved diag report for Sleep Wake Failure version ??? to /Library/Logs/DiagnosticReports/Sleep Wake Failure_2014-01-11-115049_<machine name>.diag
Jan 11 12:36:02 Hawker-Siddeley kernel[0]: Shutting down due to repeated Sleep/Wake failures
Jan 11 12:36:43 localhost kernel[0]: Sleep failure code 0x0000002a 0x27006900
Jan 11 13:22:42 localhost kernel[0]: Sleep failure code 0x0000002a 0x27006900
Has anyone had any success getting to the bottom of this problem? I set this laptop up as new, so I didn't migrate anything but data files from my old laptop.
EDIT: I have submitted an apple bug report about this (# 15817527). From everything I've read on this posts, my inclination is that this is a software problem w/Mavericks, not a hardware problem. But, I am concerned that I might be wrong, in which case, my 14-day return window expires in a week
-
Jan 14, 2014 3:03 PMby ncon64,No wake up problem thus far. However, not sure what EHC1 or RTC (Alarm) mean.
13/01/2014 16:45:38.000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
14/01/2014 07:13:50.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 07:42:39.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 09:38:55.000 kernel[0]: Wake reason: RTC (Alarm)
14/01/2014 10:33:03.000 kernel[0]: Wake reason: RTC (Alarm)
14/01/2014 10:53:13.000 kernel[0]: Wake reason: EHC1
14/01/2014 11:31:07.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 12:42:11.000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
14/01/2014 15:24:58.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 16:49:37.000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
14/01/2014 17:21:33.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 18:18:33.000 kernel[0]: Wake reason: EC.LidOpen (User)
14/01/2014 19:56:08.000 kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
14/01/2014 22:54:34.000 kernel[0]: Wake reason: EC.LidOpen (User)
-
Jan 14, 2014 5:24 PMby Sandylp,I haven't had any wake problems, either, since 12/21/13. Here is a sample of my recent sleep/wake events in terminal.
1/13/14, 8:02:16 AM PST Wake DarkWake to FullWake [CDNVA] due to HID Activity: Using BATT (Charge:100%) 1168 secs
1/13/14, 8:21:44 AM PST Sleep Software Sleep pid=66: Using BATT (Charge:99%)
1/13/14, 8:22:40 AM PST Sleep Maintenance Sleep: Using AC (Charge:99%)
1/13/14, 3:19:16 PM PST Wake DarkWake to FullWake [CDNVA] due to HID Activity: Using BATT (Charge:100%) 3995 secs
1/13/14, 4:25:51 PM PST Sleep Software Sleep pid=66: Using BATT (Charge:82%) 588 secs
1/13/14, 4:35:39 PM PST Wake Wake [CDNVA] due to EC.LidOpen/Lid Open: Using BATT (Charge:82%) 2627 secs
1/13/14, 5:19:26 PM PST Sleep Software Sleep pid=66: Using BATT (Charge:70%) 16 secs
1/13/14, 5:20:09 PM PST Sleep Maintenance Sleep: Using AC (Charge:70%)
1/14/14, 7:44:07 AM PST Sleep Maintenance Sleep: Using AC (Charge:100%) 13 secs
1/14/14, 7:44:20 AM PST Wake Wake [CDNVA] due to EC.LidOpen/Lid Open: Using AC (Charge:100%) 6248 secs
1/14/14, 9:28:28 AM PST Sleep Software Sleep pid=66: Using BATT (Charge:100%)
1/14/14, 9:29:31 AM PST Sleep Maintenance Sleep: Using AC (Charge:100%)
1/14/14, 2:00:45 PM PST Wake DarkWake to FullWake [CDNVA] due to HID Activity: Using BATT (Charge:100%) 3246 secs
1/14/14, 2:54:51 PM PST Sleep Software Sleep pid=66: Using BATT (Charge:88%) 780 secs
1/14/14, 3:08:17 PM PST Sleep Maintenance Sleep: Using BATT (Charge:88%)
1/14/14, 3:25:33 PM PST Sleep Maintenance Sleep: Using AC (Charge:87%) 5644 secs
1/14/14, 4:59:48 PM PST Wake DarkWake to FullWake [CDNVA] due to HID Activity: Using AC (Charge:100%)
I accessed the timeline of sleep/wake events by entering the following in terminal:
pmset -g log|grep -e " Sleep " -e " Wake "
-
Jan 15, 2014 2:09 AMby McPerlt,My sleep/wake logs:
When my MBP fails to wake on opening lid, it registers a sleep event with Failure code:0x1F006C00...
12/01/14 21.27.43 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 1192 secs
12/01/14 21.48.20 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:100%) 3600 secs
12/01/14 22.49.05 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 175 secs
12/01/14 22.52.45 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:100%) 3600 secs
12/01/14 23.53.30 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 00.54.15 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 01.55.00 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 02.55.45 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 03.56.30 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 04.57.15 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 3600 secs
13/01/14 05.58.00 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 2303 secs
13/01/14 06.36.23 GMT-3 Wake Wake [CDNVA] due to EC.LidOpen/Lid Open: Using AC (Charge:100%) 2428 secs
13/01/14 07.16.51 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%)
13/01/14 07.17.21 GMT-3 Sleep Maintenance Sleep: Using BATT (Charge:100%)
13/01/14 07.52.03 GMT-3 Wake DarkWake to FullWake [CDNVA] due to HID Activity: Using AC (Charge:100%) 3176 secs
13/01/14 08.44.59 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 471 secs
13/01/14 08.52.50 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 2215 secs
13/01/14 09.29.45 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 86 secs
13/01/14 09.31.11 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 1521 secs
13/01/14 09.56.32 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 72 secs
13/01/14 09.57.44 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 1164 secs
13/01/14 10.17.08 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 2025 secs
13/01/14 10.50.53 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 2793 secs
13/01/14 11.37.26 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 513 secs
13/01/14 11.45.59 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 4205 secs
13/01/14 12.56.04 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 141 secs
13/01/14 12.58.25 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 7065 secs
13/01/14 14.56.10 GMT-3 Sleep Clamshell Sleep: Using BATT (Charge:100%) 10808 secs
13/01/14 17.56.26 GMT-3 Sleep Maintenance Sleep: Using BATT (Charge:100%)
13/01/14 19.50.54 GMT-3 Sleep Idle Sleep: Using BATT (Charge:94%) 394 secs
13/01/14 19.57.28 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using BATT (Charge:94%) 534 secs
13/01/14 20.06.22 GMT-3 Sleep Idle Sleep: Using BATT (Charge:92%) 341 secs
13/01/14 20.12.03 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using BATT (Charge:92%) 2879 secs
13/01/14 21.00.02 GMT-3 Sleep Clamshell Sleep: Using BATT (Charge:82%) 10809 secs
14/01/14 00.00.21 GMT-3 Sleep Maintenance Sleep: Using BATT (Charge:81%)
14/01/14 06.28.51 GMT-3 Sleep Sleep (Failure code:0x1F006C00): Using BATT (Charge:77%)
14/01/14 07.15.08 GMT-3 Sleep Clamshell Sleep: Using BATT (Charge:70%)
14/01/14 07.57.12 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:71%) 62 secs
14/01/14 08.00.14 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:74%) 516 secs
14/01/14 08.08.50 GMT-3 Wake Wake [CDNVA] due to EC.LidOpen/Lid Open: Using AC (Charge:80%) 1058 secs
14/01/14 08.26.28 GMT-3 Sleep Idle Sleep: Using AC (Charge:91%) 2860 secs
14/01/14 09.14.08 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 4444 secs
14/01/14 10.28.12 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 3121 secs
14/01/14 11.22.13 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:100%) 2087 secs
14/01/14 11.59.00 GMT-3 Sleep Maintenance Sleep: Using AC (Charge:100%) 1615 secs
14/01/14 12.25.55 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 1928 secs
14/01/14 12.58.03 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 562 secs
14/01/14 13.07.25 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 3871 secs
14/01/14 14.11.56 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 3600 secs
14/01/14 15.13.56 GMT-3 Sleep Sleep Service Back to Sleep: Using AC (Charge:100%) 987 secs
14/01/14 15.30.23 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 1354 secs
14/01/14 15.52.57 GMT-3 Sleep Idle Sleep: Using AC (Charge:100%) 480 secs
14/01/14 16.00.57 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using AC (Charge:100%) 522 secs
14/01/14 16.09.39 GMT-3 Sleep Idle Sleep: Using BATT (Charge:100%) 2546 secs
14/01/14 16.52.05 GMT-3 Wake Wake [CDNVA] due to EC.LidOpen XHC1/Lid Open: Using BATT (Charge:100%) 362 secs
14/01/14 16.58.07 GMT-3 Sleep Idle Sleep: Using BATT (Charge:100%) 418 secs
14/01/14 17.05.05 GMT-3 Wake Wake [CDNVA] due to XHC1/HID Activity: Using BATT (Charge:100%) 4882 secs
14/01/14 18.26.27 GMT-3 Sleep Idle Sleep: Using BATT (Charge:83%) 10809 secs
14/01/14 21.26.48 GMT-3 Sleep Maintenance Sleep: Using BATT (Charge:82%)
15/01/14 06.52.53 GMT-3 Sleep Sleep (Failure code:0x1F006C00): Using BATT (Charge:78%)
-
Jan 15, 2014 2:53 AMby ncon64,My active profiles at the mo'on my Mac book pro retina late 2012. Does anyone suggest I change?
Active Profiles:
Battery Power 1
AC Power -1*
Currently in use:
standbydelay 4200
standby 1
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
darkwakes 1
sms 1
networkoversleep 0
disksleep 10
sleep 10
autopoweroffdelay 14400
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 10
acwake 0
lidwake 1
-
Jan 15, 2014 3:00 AMby ncon64,Igoogled failure code and found this:
Dec 25, 2013 9:15 PMSince I bought my mbp retina 13" early 2013 with Mac OS 10.8.5, I am experiencing a problem with hibernation/sleep. Every time it gets nearly 0% batt it should hibernate (hibernate mode is 3, default) saving the session memory to /var/vm/sleepimage so as to recover it as soon it is put to charge again. But rather it will start over, losing previous session... Logs from console will show sleep failure status like this:
25/12/13 23:25:40,000 kernel[0]: Sleep failure code 0x00000000 0x1f006a00.
And logs from pmset ("pmset -g | grep failure") will show sleep failures status like this:
13/12/13 01:17:20 BRST Sleep Sleep (Failure code:0x3A98012006A00): Using AC (Charge:0%)
13/12/13 01:54:14 BRST Sleep Sleep (Failure code:0x1F006A00): Using AC (Charge:0%)
13/12/13 02:10:15 BRST Sleep Sleep (Failure code:0x1F006A00): Using AC (Charge:0%)
25/12/13 23:25:42 BRST Sleep Sleep (Failure code:0x1F006A00): Using BATT (Charge:100%)
It is curious that, on last episode (on 25dec2013, as above) the battery was in fact discharged and then the system was supposed to store memory to sleepimage and hibernate, but the Sleep Failure log says Charge was 100%...
By the way: PRAM and SMC resetting were already performed, and the problem persists.
I am losing all my sessions data because of this... Does anyone suffering from the same issues?
I'm starting to think it more a case of it not going to sleep as expected that's causing the wake up issue - comunication glitch with in it causing confusion and wrong instructions. Could be a a dodgy chip in side some of the MBPR's
-
Jan 15, 2014 3:09 AMby Supreem,Yes it's definitely a case of 'failure to sleep' leading to a crash and the inability to wake up. This has always been the case simply because for example I put my MBP to sleep on 100% charge and whenever the failure to sleep and crash occurs, the laptop is A) warm to the touch in the morning, and B) Only with say 20% battery life remaining out of the 100% when put it to sleep.
Secondly, yes I agree that I think this is a hardware issue as it's not widespread, if it was a software duplicated issue then this thread would be thousands of pages long by now and it would be big news in the tech media.
-
Jan 15, 2014 3:13 AMby ncon64,Not that this is totally related to issues on this thread...I found this and thought it might interest some:
I never had this with my 2008 MBP, but since a few months, I have had a rMBP:
It keeps waking from deep sleep
Since the hard drive is so fast, and I rarely shut it down entirely, I have set the sleep mode to save to disk only (on closing the lid). Works fine, except ... some times when I approach the sleeping rMBP, the fan is running wild, and it is quite hot!
So I wondered why it would wake up by itself, nothing attached at all, and I think I have narrowed it down to "Wake for WiFi network access" in the Energy Saver settings.
I found a hint to use terminal to search for what disturbs its sleep, using
syslog |grep -i "Wake reason"
and it came up with loads of wakes:
Oct 4 09:13:01 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:14:17 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:15:43 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:17:08 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:18:35 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:19:49 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:21:11 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:22:31 localhost kernel[0] <Debug>: Wake reason: RTC (Alarm)
Oct 4 09:23:58 localhost kernel[0] <Debug>: Wake reason: EC.LidOpen (User)These are just the last few, there are loads of them, the last one being me opening the lid as I heard the fan running (while it should have been sleeping).
I narrowed this down to Energy Saver, waking the rMBP on WiFi. I guess this is not unique to retina MBPs, but any mountain lion MB?
The solution is simply to enter System Preferences > Energy Saver > Untick "Wake for WiFi network access"
I hope this can help others with similar problems.
Being plugged in, closing the lid, and then it wakes up by itself ... there is not a lot of cooling for it, and it cannot open the lid itself, only turn the fans on!
When I put my mac into deep sleep, I want it to ... deep sleep! Otherwise I would put it into a power nap, right?
Potentially, if waking while in my bag, it could overheat to an extend to cause a thermal runaway on the battery (I know, it's not plugged in to my bag, but I HAVE FOUND it to be waking, even when unplugged inside my bag). I can assure you, metal lithium batteries that overheat ... are not to be taken lightly! More and more airlines now prohibit or limit the transport of these batteries in bulk, or how many you can carry as a passenger. Loose batteries even more restricted than those inside consoles. And this is not just to annoy passengers, but because of real fire hazards!
