Retina MacBook Pro wont wake from sleep

Question

Level 1

5 points

Retina MacBook Pro wont wake from sleep

This issue is frustrating me to the point where I want to return it. About 1 in every 2 times when I try to wake this computer from sleep it will NOT respond to any mouse or keyboard action. The computer is still on (caps lock light works), but the screen just wont turn on. The only solution is to force shut off via power button and restart.

I turned off the "But hard drive to sleep" option in case its an issue with that and the SSD in this computer, but still have the issue. The macbook pro is connected to a cinema display most of the time and it occures more frequently when I connect/disconnect the cinema display. I also have screensaver/log back in after sleep enabled and im pretty sure this only happens when the "enter password to wake from sleep" is enabled so its obviously some sort of OS issue.

(ps I just installed snow lepard and the issue is still happening).

MacBook Pro with Retina display, Other OS, 10.8

Posted on Jul 28, 2012 2:30 PM

Reply

Answer 1

ClayG

Level 4

1,416 points

Jul 28, 2012 2:36 PM in response to jstefanop

Issues related to sleep are notoriously difficult to diagnose. I would recommend contacting AppleCare about this one. It will be much more efficient than waiting for replies here.

If you want to try some troubleshooting on your own, the first place you should look is in Console (it's in your Utilities folder). The next time you have this problem waking from sleep, once you finally do get it to come on, look in Console, select All Messages, and see if there are any messages that say anything about sleep. Post them here if you'd like.

Reply

Answer 2

jstefanop Author

Level 1

5 points

Jul 28, 2012 3:01 PM in response to ClayG

Ok here we go, below ive posted all console message from the last time this happen and ill explain each time stamp what occured..

At 3:58 the laptop was sleeping and I pulled the cinema display and usb cable that connects to it, shut the lid, and put the computer in my bag

At 4:40 the computer was still in my bag and there was no intervention from me so these events happend while the computer was still supposed to be in sleep and im assuming this is where the problem occured from reading all the error messages from this timeframe

At 5:05 is when I got home and opend the lid and this is where the screen was blank and nothing would respond. Its obviouse from the messages that the computer tried to wake up (and you can see that it joined my home airport network "John's Network") so things seem to be working correctly internally but for whatever reason the screen was never powered on.

At 5:08 is when I forced rebooted the machine after the display wouldnt respond.

What catches my eye is this message

7/28/12 5:06:17.000 PM kernel[0]: NVDA::setPowerState(0xffffff8030425000, 0 -> 2) timed out after 45426 ms

My translation of this is "tried to power on Nvidia GPU but timed out after 45 seconds". And this makes since since wake occured 5:05:32 and 45 seconds later is 5:06:17. So it seems like some issue is going on with waking up the graphics chip and or graphics drivers.

7/28/12 3:58:53.436 PM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fe815005260> Sat Jul 28 16:40:39 2012 EDT (approx)

7/28/12 3:58:53.436 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fe815005260> Sat Jul 28 16:40:39 2012 EDT (approx)

7/28/12 3:58:53.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

7/28/12 3:58:57.000 PM kernel[0]: en0: BSSID changed to 20:4e:7f:47:e7:7e

7/28/12 3:58:57.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0

7/28/12 3:58:57.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

7/28/12 3:58:57.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed

7/28/12 3:58:57.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

7/28/12 3:58:57.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

7/28/12 4:40:39.000 PM kernel[0]: Wake reason: RTC EHC1 (Alarm)

7/28/12 4:40:39.000 PM kernel[0]: RTC: Maintenance 2012/7/28 20:40:39, sleep 2012/7/28 19:58:58

7/28/12 4:40:39.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

7/28/12 4:40:39.000 PM kernel[0]: Previous Sleep Cause: 5

7/28/12 4:40:39.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2)

7/28/12 4:40:39.000 PM kernel[0]: en0: 802.11d country code set to 'X0'.

7/28/12 4:40:39.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165

7/28/12 4:40:39.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

7/28/12 4:40:39.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

7/28/12 4:40:39.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d100000) may have caused a wake by being disconnected

7/28/12 4:40:39.000 PM kernel[0]: TBT W (2): 0x0100 [x]

7/28/12 4:40:39.000 PM kernel[0]: [0xffffff8030434000](0)/(5) Device not responding

7/28/12 4:40:39.560 PM hidd[73]: MultitouchHID: device bootloaded

7/28/12 4:40:39.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

7/28/12 4:40:40.256 PM com.apple.backupd-helper[2134]: Not starting scheduled Time Machine backup - computer is on battery power.

7/28/12 4:40:40.000 PM kernel[0]: Graphics suppressed 1222 ms

7/28/12 4:40:40.702 PM configd[17]: network changed: v4(en0-:192.168.1.8) DNS- Proxy- SMB

7/28/12 4:40:40.000 PM kernel[0]: en0: 802.11d country code set to 'US'.

7/28/12 4:40:40.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165

7/28/12 4:40:45.380 PM coreservicesd[31]: Application App:"Apple80211Agent" [ 0x0/0x2b02b0] @ 0x0x7f9b15546b00 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x205205:, ASN:0x0-0x1001:) ), so denying.

7/28/12 4:40:45.381 PM WindowServer[89]: [cps/setfront] Failed setting the front application to Apple80211Agent, psn 0x0-0x2b02b0, securitySessionID=0x186a6, err=-13066

7/28/12 4:40:45.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep

7/28/12 5:05:32.010 PM loginwindow[68]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check

7/28/12 5:05:32.000 PM kernel[0]: Wake reason: EC.LidOpen (User)

7/28/12 5:05:32.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

7/28/12 5:05:32.000 PM kernel[0]: RTC: PowerByCalendarDate setting ignored

7/28/12 5:05:32.000 PM kernel[0]: Previous Sleep Cause: 5

7/28/12 5:05:32.000 PM kernel[0]: NVRM: 0x702a called in D3

7/28/12 5:05:32.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

7/28/12 5:05:32.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

7/28/12 5:05:32.000 PM kernel[0]: TBT W (2): 0x0100 [x]

7/28/12 5:05:32.568 PM hidd[73]: MultitouchHID: device bootloaded

7/28/12 5:05:32.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

7/28/12 5:05:34.862 PM airportd[2131]: _doMaintenanceWakeAutoJoin: No scan results (null)

7/28/12 5:05:37.000 PM kernel[0]: MacAuthEvent en0 Auth result for: 00:21:e9:f7:3f:49 MAC AUTH succeeded

7/28/12 5:05:37.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0

7/28/12 5:05:37.000 PM kernel[0]: AirPort: Link Up on en0

7/28/12 5:05:37.000 PM kernel[0]: en0: BSSID changed to 00:21:e9:f7:3f:49

7/28/12 5:05:37.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed

7/28/12 5:05:38.024 PM airportd[2131]: _doAutoJoin: Already associated to “John's Airport”. Bailing on auto-join.

7/28/12 5:05:38.067 PM airportd[2131]: _doAutoJoin: Already associated to “John's Airport”. Bailing on auto-join.

7/28/12 5:05:38.106 PM airportd[2131]: _doAutoJoin: Already associated to “John's Airport”. Bailing on auto-join.

7/28/12 5:05:41.354 PM configd[17]: network changed: v4(en0+:10.0.1.4) DNS+ Proxy+ SMB

7/28/12 5:05:41.377 PM UserEventAgent[11]: CFPreferences: user home directory for user mobile at is unavailable. User domains will be volatile.

7/28/12 5:05:41.381 PM UserEventAgent[11]: Captive: en0: Probing 'John's Airport'

7/28/12 5:05:41.458 PM UserEventAgent[11]: Captive: Online (not captive)

7/28/12 5:05:41.461 PM configd[17]: network changed: v4(en0!:10.0.1.4) DNS Proxy SMB

7/28/12 5:06:17.000 PM kernel[0]: NVDA::setPowerState(0xffffff8030425000, 0 -> 2) timed out after 45426 ms

7/28/12 5:06:24.000 PM kernel[0]: considerRebuildOfPrelinkedKernel prebuild rebuild has expired

7/28/12 5:07:26.100 PM coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=115

7/28/12 5:08:34.000 PM bootlog[0]: BOOT_TIME 1343509714 0

Reply

Answer 3

Jul 29, 2012 3:12 AM in response to jstefanop

Hey there,

I too have the same problem, it's really really frustrating! I added a bug to http://bugreport.apple.com I advice you to open a critical bug too.

I upgraded from Lion and I don't remember having this wakening problem - only after I installed ML, but I could be wrong. Anyway, it happens a lot. I tried to narrow down by closing all the open application prior to entering sleep mode. The last time it didn't wake was when I only had gfxCardStatus - next time I will try to close it too(I too think it has something to do with graphics switching, so maybe gfxCardStatus causing some issues? I doubt it, but I have to try to close it too next time I'm entering sleep mode).

Please update if you discover what is causing the wakening problem, as I'm pretty sure(and hope) it's software-related and not hardware problem(in which case means we need to replace our laptops)

Reply

Answer 4

Jul 29, 2012 4:36 AM in response to kernixster

Did you install the SMC firmware update for the Retina MacBook Pro that just came out yesterday? Would be interesting to know whether it fixes this issue.

Reply

Answer 5

Jul 29, 2012 6:16 AM in response to Tim Lorenzen

Yes, I did install the firmware update few days ago and it didn't help.

UPDATE: wakening now caused beep sounds!!! What is going on here??? had to hard shutdown again.

and another UPDATE: before going to sleep I closed gfxCardStatus - that didn't help -it didn't wake up and made those beeping sounds!

I will go to sleep now when gfxCardStatus is opened and will let it work with the integrated card only.

Reply

Answer 6

Shootist007

Level 6

16,709 points

Jul 29, 2012 6:20 AM in response to jstefanop

Not sure what version of OS X you just installed but it certainly was not Snow Leopard. SL would not even boot that Retina MBP from the install DVD. SL does not have, and never will have, the correct driver package to work on that new Mac.

Your problem is hardware based and Apple needs to replace your Mac. That goes for kernixter also.

Reply

Answer 7

Jul 29, 2012 10:12 AM in response to Shootist007

I don't think it's hardware problem, because before upgrading to ML I had no sleep-wakening problems.

2 Updates:

1 - twice today my computer didn't wake from sleep - and now it makes beeping sounds with the black screen.

2 - I tried to close gfxCardStatus before entering sleep mode, and it didn't help. In addition I tried changing to use only integrated card and that didn't help either.

I'm considering making fresh Mountain Lion install on the system, I have no idea what is the problem.

Also, I'd like to note that if I enter sleep mode for few minutes I have no wakening problems.

Reply

Answer 8

ClayG

Level 4

1,416 points

Jul 29, 2012 10:17 AM in response to kernixster

Sleep problems are rarely hardware-based. Almost definitely software or firmware. My best guess is that your Mac is actually having a problem going to sleep, which then caused the sound you hear when you keep pressing keys to wake it.

I'd recommend a reinstall of the OS from the Recovery Partition. To do this, restart while holding down command and R keys. Just make sure you have all of your stuff backed up somewhere first!!

Reply

Answer 9

Jul 29, 2012 10:19 AM in response to ClayG

That's exactly what I'm thinking about - a fresh new install. What would you recommend - I'm willing to delete all my files in the HD and making a new fresh installation from scratch. Maybe some applications causing it, and maybe fresh installation is the best. What do you think?

Reply

Answer 10

Jul 29, 2012 2:01 PM in response to ClayG

OK, I've just finished with Recovery installation, now I'll put it to sleep and see what happens. I'll update when I try to wake it.

Reply

Answer 11

Jul 29, 2012 4:48 PM in response to kernixster

Unfortunately, even after fresh new Recovey installation still having wakening problems ( occurs after one and a half hours of sleep).

Next thing I'll try is fresh new installation.

Reply

Answer 12

Shootist007

Level 6

16,709 points

Jul 29, 2012 7:04 PM in response to kernixster

kernixster wrote:

Unfortunately, even after fresh new Recovey installation still having wakening problems ( occurs after one and a half hours of sleep).

Next thing I'll try is fresh new installation.

What exactly do you mean by a Fresh Recovery install? If you mean wiping the drive and then restoring from a TM backup made just before you wiped the drive that is in no way any type of Fresh install. You are putting back exactly what was on the computer before the wipe. Nothing Fresh about it.

I do hope that a CLEAN install solves your Sleep/Wake problems but I am still of the option that it is related to a hardware fault of some type.

Good Luck.

Reply

Answer 13

Jul 30, 2012 1:09 AM in response to Shootist007

Good morning ladies and gentlemen, I come with happy update!

After all the trouble I went through I came with a solution - and for me a good one.

As I said in my previous messages, yesterday I learned how to freshly install ML. That means, formatting the partition in which ML was installed, and installing it from scratch.

Hapilly now I don't have any wakening problems. Moreover, I'm 99% sure that it fixed my problem, and I'll get into more detail:

Since I encountered wakening problems, I learned that in order to reproduce black-screen-from-sleep, all I needed to do was get into sleep mode for about an hour an a half or more, and then I couldn't wake the machine. This could be reproduced every single time.

Today, after going to sleep for 5 hours, I went to the laptop and crossed my fingers that after formatting and installing I won't have wakening problems. I then put it to sleep for another hour and a half and again - NO PROBLEM!

The result: No Wakening problem after entering sleep mode for more than hour and a half! I'm thrilled! All the hard work paid off and it's not hardware related as I thought so, due to the fact that I had no sleep-wakening issues on Lion.

I'll update this thread after I'll do a little more testing throughout the week, and after I'll install some applications on the system, but for now I'm very happy.

Cheers!

Reply

Answer 14

Jul 30, 2012 4:18 AM in response to kernixster

Will be good to hear how your testing goes kernixster. I actually had a couple of issues waking from sleep even on Lion so I don't think it's just a ML thing.

I was thinking it could have been an app I had running. I've been using Tweetbot alpha, so I've made sure it's closed before sleeping. So far so good, but it still seems a little odd when waking from sleep.

Sometimes my screen will be filled with lines and blurred for about 5 seconds even whilst being able to move the mouse, before waking up properly. Still doesn't seem normal to me. So hopefully it's just a software thing.

Reply

Answer 15

Jul 31, 2012 3:26 AM in response to yesterdayshero

Hey,

Quick update: After installing several applications and have gone to sleep mode few times - including long sleep times of 8 hours - I can say that formatting the partition and freshly installing ML seems to have fixed my sleep-awakening-problem.

Reply