I have a late 2011 15" MacBook Pro.
I also had waking problems, when i closed the lid and tried to wake it.
Took it to apple store and they checked it out. Said all seemed fine, but they decided to use Disk Utilities to repair "permissions".
It worked. No more failing to wake from sleep.
I repair permissions about once a month and it seems to do the trick.
It seems like your solution worked for me.
I repaired permissions 2 days ago. No problems in waking up from sleep since.
Thanks for sharing!
Today my MBP Retina didn't wake up from sleep two times. It also seems like it's running hot when it does that, because the fans ran at full speed.
Hi there, brferreira8, how are you?
I understand that you're having problems - as I have - so don't worry, I'll help you in the process of fixing this annoying can't-wake-from-sleep.
First of all, follow this guide on how to freshly install Mountain Lion. Here is the link:
As you can see, there are 6 steps which are shown in slides - please follow them, as they are the exact same procedure I went through.
If you have any problems with any of the steps, please let me know and I'll do my best to help you help.
Be strong and good luck!
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.
This has just started happening on my very old 2009 MBP since I bought a new external display. In my case a least, the problem occurs when I pull the mini-DVi connector out of the MBP then close the lid. Then opening the lid (without the display connected) causes the problem.
Console reports this fault when the machine tries to wake:
18/10/2012 16:23:29.000 kernel: NVDA::setPowerState(0xffffff8013490000, 0 -> 2) timed out after 45232 ms
I suspect a workaround would be to disconnect the display and wait for 30s or so before closing the lid, so that the graphics software catches up and registers the change before sleep.
I've also had a similar problem in the past when closing the lid too quickly after disconnecting the external display sent the PRAM or SMC out of wack and turned my fans on full blast. For that reason, you might also try both a PRAM and SMC reset and see if those help.
I'm going to see if I can find out more about that 'setPowerState' error. Will report back if I turn up anything useful.
I have similar problem to the first poster
wnen reconnect my MBP retina to my Thunderbolt monitor my MBP either goes to sleep or shuts down. Can't tell.Ihave to press power button to restart and sometimes have to press hard several times to get MBP to re start
NO problems when I sleep the mac via command under Apple Menu
Problem ONLY when manually closing lid (clamshell mode ) OR MBP goes to sleep on its own, per the time I set in Energy Saver)
I repaired permissions, redid the SMC - no fix
Any thought, foks that the new " Power Nap" feature may be causing this? I never had this problem before but I also never had PowerNap feature.
Same question as OP, sometimes I'll leave the rMBP with the lid open and after the screen goes to sleep (turns off as set by power settings), the whole computer won't respond when I try to wake it from sleep. I can usually change the volume and the level of the keyboard backlight, but can't turn the screen back on, even if I connect an external display. The only recourse to see anything from the screen again is to hard reset the computer. I checked my console and couldn't find anything about the graphics, but did find this:
10/22/12 8:14:52.000 PM kernel: Sleep failure code 0x00000000 0x31000000
Searching around didn't give any useful information on that code, though. I just wanted to throw my hat in this ring too and hopefully get a critical mass of people so that Apple will take a look at this.
I presume it's got to be something about the graphics because it seems that the rest of the computer works, but the graphics just aren't being driven to the screen (or anywhere else...)
Sadly I am having the issues again, even after reinstalling ML and installing all my apps from scratch again. The issue seems to happen for me when my power cord is on (from the Thunderbold display) and the lid closed for a few hours. I never happens when the power cord is not on, regardless of lid being open or closed. I have not tested with the MBP power cord itself as I don't use it sonce the display provides one.
I have a MBA running 10.8.2 with the problem where the keyboard and mouse pointer wouldn't work when trying to come out of hibernate (or whatever the correct term is - going to sleep on battery power for multiple hours). Anyway, I did a repair permissions, which incidentally included the CoreGraphics framework, and some other probably less relevent things and it seems to have resolved the problem.
My Retina MacBook Pro fails consistently to wake from sleep. I have a log in dialog but no cursor and the system is unresponsive to any key presses or trackpad inputs. Before it started this behavior, it was sometimes momentarily unresponsive but after a few seconds it would allow keyboard entry. But now I'm waiting a minute or longer and finally have to turn off the machine and start up again.
I'm surprised folks are willing to go to lengths like formatting partitions, reinstalling the OS and reinstalling apps. This is a $3,000 machine and at this point I would gladly give it back to Apple for a refund. Probably too late for that since it was a September purchase. I'm terribly disappointed.
People do reinstalls and other random methods out of either ignorance or desparation - it's certainly not troubleshooting or getting to root cause. I like AppleCare, but I'm loathed to ring them up and trying working through this issue because I know it will be painful or futile given the complexity. It's going to need analysis by one of the developers with a pile of expertise.
In case there are Apple people lurking here, when the system is in this state, it's still responsive on the network and I can log in to it. I wish I could just generate a system dump and send it in for them to look at! Unfortunately my expertise is with a different flavour of UNIX, so I'm struggling. Perhaps I should file a bug and hope someone reaches out to us.