Problem with waking from sleep with 10.8.2

My Mac Pro (early 2009 2.66 GHz Quad-Core Intel Xeon) won't wake from deep sleep after installing OS X 10.8.2 . I have the default setting set for sleep. The only way to "wake" the machine is to hold the power button down to shut down and then restart. I've reset NVRAM (pram) and tried removing power cable. Nothing helps.

Mac Pro, OS X Mountain Lion (10.8.2)

Posted on Sep 21, 2012 1:53 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 26, 2012 11:47 PM

Ok, I've got great news for some of you. I've got a macpro (early 2009). After upgrading to 10.8.2 and changing the energy saver preferences to use the wake on ethernet option, I've had the un-wakeable sleep problem and its driven me nuts the past week!


I suggest you all carefully look at your /var/log/system/system.log file, as well as the /var/log/DiagnosticMessages/{date}.asl file. (you can read those with syslog -f {filename}). That is how I traced down the source of my problem.


So here's my situation. My monitors would sleep at exactly the time interval specified in energy saver preferences, note that the status light next to the powerbutton would stay solid. Then computer would then sleep roughly the time I expected it to, but rarely at the exact time. Anyways, after going to sleep, I'd hear a click and the status light would go from solid to the heartbeat thing. After reviewing the system.log, I noticed that precisely 2 hours after sleeping, the computer would go into a maintenance mode. You'll see this in the system.log:


Oct 26 14:51:25 MacPro kernel[0]: Wake reason: RTC (Alarm)

Oct 26 14:51:25 MacPro kernel[0]: RTC: Maintenance 2012/10/26 21:51:24, sleep 2012/10/26 19:51:27

Oct 26 14:51:25 MacPro kernel[0]: No interval found for . Using 8000000

Oct 26 14:51:25 MacPro kernel[0]: Graphics suppressed 0 ms

Oct 26 14:51:25 MacPro kernel[0]: Previous Sleep Cause: 5

Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0

Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0

Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0

Oct 26 14:51:25 MacPro.local configd[17]: network changed: v4(en1-:192.168.1.239) DNS- Proxy- SMB

Oct 26 14:51:25 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face001, 0

Oct 26 14:51:28 MacPro kernel[0]: Ethernet [Intel82574L]: Link up on en1, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,af48,0de1,0200,c5e1,3800]

Oct 26 14:51:28 MacPro kernel[0]: Intel82574L::setLinkStatus - active 1face001, b

Oct 26 14:51:32 MacPro.local configd[17]: network changed: v4(en1+:192.168.1.239) DNS+ Proxy+ SMB

Oct 26 14:51:34 MacPro kernel[0]: Intel82574L::timeoutHandler - no link - reset the chipset once 1face000, 0

Oct 26 14:51:34 MacPro kernel[0]: Intel82574L::setLinkStatus - not active 1face000, 0

Oct 26 14:52:05 --- last message repeated 2 times ---

Oct 26 14:52:10 MacPro kernel[0]: NVDA::setPowerState(0xffffff801df17000, 0 -> 1) timed out after 45476 ms


Note the 4th line, where it says graphics suppressed, then the last line where it says NVDA:: .... timed out.... That was the clue I needed. It seems that this maintenance mode wakes up to turn on the network interfaces, but tries to suppress the graphics card from waking up... However, the graphics card just times out. Apparently it doesn't support this action very well. I carefully watched my system and precisely 2 hours after it goes to sleep, I hear the system click, and the status light would go from heartbeat to solid.... Thats when the system freezes and you can no longer revive it. Actually, to be clear, the system was still accessible by ssh, so more accurately I'd say that probably it was just the graphics card was frozen... Nothing but a reboot would fix it. Note that I even tried issuing a reboot via SSH (thinking that was slightly safer than just holding the powerbutton), and although it did shut down some services (like SSH) it wouldn't complete the reboot and I'd still have to hit the Power button....


So anyway, now that I was pretty sure it was graphics card related (and triggered by the maintenance mode apparently related to the wake-on-lan), I googled 10.8.2 and nvidia... and what do you know? Nvidia released new drivers specifically for 10.8.2 this month!


This is the driver I needed for my stock GeForce GT 120:

http://www.nvidia.com/object/macosx-304.00.05f02-driver.html


PLEASE read the notes, it says its that this particular driver is for MacPro's only and 10.8.2 only.


Possibly check for drivers for other nvidia cards if this isn't you!

http://www.nvidia.com/Download/index.aspx?lang=en-us


So I installed the driver, rebooted, and voila, all works fine. I let it sleep, it went into maintenance mode after sleeping for two hours, and this time the monitor came on for 30 seconds, then went back to sleep (again with the heartbeat). I could issue a wakeonlan signal and then ssh in, or I could wake the computer by pressing the power button briefly. From my perspective, all is working fine. I can wake it properly from the power button, and I can wake-on-lan it properly too.


And just for reference, I use this wake-on-lan perl script. It works great, even through a router and wifi.

http://gsd.**.uminho.pt/jpo/software/wakeonlan/

I didn't realize this at first, but when sending the wakeonlan through a router you don't specify the IP address of the computer you're trying to contact. Just use the default ip (255.255.255.255 or your local network broadcast ip, like 192.168.1.255). The problem with routers is that once you're computer sleeps the router forgets your computer, so you need to broadcast the message to ALL ips and wait for the right one to match the macaddress and wake up... So just run it like "wakeonlan <macaddress>" and it works perfect. It even wakes my macbookpros connected only by wifi.


Also note that I tried the "darkwake=0" thing as well. I'm not really sure if that made any difference, but it is still set that way on my machine. You may or may not need that, I'm just not sure.


And one last note, I called applecare thinking my macpro still had coverage, but it turns out it expired a few months ago. They had me explain the problem anyways and said this is a "known issue" and that they could fix it for $59 or whatever. I told them no and figured it out on my own, but, it kinda ****** me off considering this was NOT really a hardware problem. It was an issue introduced by OS X 10.8 and I just recently PAID for this O/S upgrade. Personally I think they should be supporting this since I bought the O/S. My hardware was fine, it was the stock graphic card drivers bundled in 10.8.2 that was the problem! I fully assume that a future upgrade (maybe 10.8.3 if you're lucky) will include the updated drivers... Until then they're happy to NOT publish this simple fix anywhere and charge you for it instead. VERY LAME APPLE!


Best of luck to the rest of you. If this doesn't solve your problem, check those log files I pointed out, try to pinpoint the time your machine freezes and look for related events in the log files!


Cheers,

Rob

267 replies

May 26, 2014 4:26 PM in response to SusanLake

I just went thru similar problem and what I learned may be helpful to others: Late 2012 MBP Retina just out of nowhere stopped waking up from sleep - had to shut down and then restart. 4 tech support calls didn't solve tho after the hardware reset call, noted that they had me unplugg all preipherals. I left them unplugged and noted the problem disappeared. Then, I started reconnecting one at a time and then restarting and waiting. No problem until I plugged in the 3rd hard drive in a 3-drive chain of thunderbolt drives. Then no waking. So then I ran a verify and repair scan on all three disks. Found one was faulty - it was the middle drive. I reformatted that drive. Now with everything reconnected all seems to be solved. Amazing.

Oct 2, 2012 12:31 AM in response to Coxize

I noticed that the problem only occurs when my system (Mac Mini, late 2009) goes to sleep based on the timer as defined in Energy Settings. When put to sleep manually (keyboard key-combination or finder menu) all is well. When wake-on-lan is enabled, the system will also sleep based on some timer. This will trigger the problem as well. So now I have set: wake-on-lan disabled and Energy Settings set to never sleep. As I result I have to put my system to sleep manually every time. Never happened before 10.8.2 upgrade. Apple please fix.

Oct 2, 2012 7:31 AM in response to SusanLake

Thanks for reposting this approach to solving the wake from sleep problem with 10.8.2. In my case, it has now been two full days since it happened and I am keeping my fingers crossed.


On my machine, I think that a new driver v. 6.3.4-3 (posted last week) for my Wacom Intuos 5 Touch tablet fixed things. The previous driver would simply quit from time to time. The first time my computer started up under an energy saver setting, it went to sleep and then wouldn't wake up. After force restarting, I repaired permissions, and it hasn't happened again. Don't know if it is worth mentioning, but I installed 10.8.2 from a combo updater that I downloaded from the Apple website, not via the update in the App Store.

Oct 6, 2012 5:23 AM in response to bratman91

Yesterday I posted saying that I had applied the supplemental update and it had not solved the wake problem.

I'm revising that statement. Looks like my problem may be fixed. Following the update yesterday I found that bluetooth was not working. When I attempted to turn it on I got a message that the bluetooth module was not present and to check my hardware. Never seen that message before and wasn't sure what it meant.


I tried a shutdown and restart without solving the problem. So I did a NVRAM reset--power down, hold the command, option, p, and r keys during power up until the machine boots the second time. That fixed the bluetooth issue.


Next I turned the wake-for-network-activity option back on and let the laptop sleep. My MacBook Pro slept normally from noon yesterday until this morning. It woke normally this morning with just a click on the mouse pad. Checking the system log I saw a number of RTS alarm wakes overnight--those were the kiss of death for me before--with normally sleep operations following them.


Looks like my problem is sloved. Don't know if others will have the same success, but I hope so.


As bratman91 I didn't see the update show up in the app store. Found it by doing a google search for 10.8.2 supplemental. You can download the update from Apple support page http://support.apple.com/kb/DL1600.

Oct 28, 2012 1:35 PM in response to Sascha_Rheker

Sascha, were you getting the "NVDA .... timed out ..." message before the driver update? Are you still getting it after?


Note that it was the maintenance mode that runs precisely 2 hours after sleeping that triggered this problem. If this is when your system becomes un-wakeable (like mine), investigate your /var/log/system.log file, look for the first logged "Wake reason: RTC (Alarm)" after your last crash. That should be logged at 2 hours after sleeping. Your computer wakes up and runs, turns on your network interfaces, etc... It was right after that I used to see the "NVDA ... timed out..." messages. If thats not your problem, maybe its another device that is having problem waking up and shutting down, causing the issue. There might be some clues there somewhere.


best of luck,

Rob

Oct 29, 2012 5:13 AM in response to bonfire

Just had a wild thought on this problem.


The condition appears to start with an RTC alarm. This is related to wake-for-network-access as it does not occur when that option is off. RTC generates a Full Wake / Dark Wake / Maintenance Wake mode--see messages in system log file. As this is a dark wake the display is turned off. Following this wake we see a time out of the graphics driver (or card.)


Is the graphics card timing out because the dark wake turned it off? When the next command to the card is issued, the card isn't listening. I noticed that if I use the better-battery-life energy saver option that uses memory instead of the graphics card, I do not have the hang problem. System sleeps and wakes normally even with wake-for-network-access on. Anyone want to bet the problem is the graphics card is turned off?

Dec 6, 2012 10:41 PM in response to SusanLake

Hi,


Because of "nda" I'm afraid I can't speak too much about it, but any person with this problem and registred at adc ( Register ) can give a try at Mac OS ML last update. It is possible to register for free...

For others the solution could be there in a couple of weeks ( days ? ) via Software Update in the Apple menu ..


It worked for me and this black screen pulsing but dead Mac thing I had for months is gone now. As is the sound the graphic card used to make : a slight puf-puf-puf-puf, very slight but never ending noise when Mac was supposedly asleep.


hth and that I did not broke the "non disclosure agreement"

Jan 27, 2013 7:30 AM in response to Chet Rindfuss

Chet Rindfuss wrote:


My point of view is the problem is hard to fix because there isn't a single cause.


...


When the user attempts to "wake" the Mac its not really alseep. It appeas to be asleep because the screen is dark. Nothing will wake the Mac because its already awake in the dark maintenance mode.


The bug really is finding out what is blocking the Mac from returning to sleep.


As always, this is my situation and others may be seeing other issues here. Bottom line. This is a complicated issue.

I have to agree with Rindfuss, re; it's likely not isolated to one issue and complicated to identify. I would not expect a fix from Apple since it is likely caused by 3rd party software tha is not fully ML compatible.


I was able to isolate the issue and fix the problem by troubleshooting "Login Items":

Dec 9, 2012 9:01 AM (in response to sleepystu)


It sounds like updating the SMC and graphics drivers has worked for some, but not others.


My advice would be:

1) to either try the trobleshooting suggestions made between these two forums (at your own risk, since some are rather invasive), or,

2) try a Full, Clean, Fresh reinstall of the OS and software - without Migration Assistant or Time Machine (otherwise you will just end up copying over the problem). Install Applications one at a time to test if the probelm reccurs. A lenghty process, but I don't think Apple is going to come to the rescue with an update on this one.

Mar 12, 2013 6:34 AM in response to SusanLake

I have been battling something similar for quite a while. I have a Macbook Pro with identifier 5,3 (I think that's 2009). Short periods of sleep wake up fine; however it refuses to wake whenever I come back after a night a way from the office. Here's the key info:


Macbook Pro (5,3)

Mountain Lion 10.8.2

External monitor with powered USB hub.

USB keyboard plugged into hub and bluetooth trackpad.

and the kicker:


The issue doesn't happen as long as all apps appearing to use webkit are quit prior to sleep. This list includes Chrome, Safari, Spotify, and iTunes.


I hope this last bit helps others narrow down a solution.

Sep 25, 2012 7:09 AM in response to SusanLake

I have a MBP 17" late 2011. I just did upgrade from Lion to Mountain Lion 10.8.2. Immediately after the upgrade I was experiencing the exact same problem as the OP - it would take anywhere from 1.5 to 2 minutes to wake up.


I finally called Apple. They told me to:


1. Boot up holding down the CMD and R keys to get to Disk Utilities.

2. Run Repair Permissions.

3. Run Repair Disk.


4. Close out of the Disk Utilities and boot the machine.


5. Open the Finder. Hold down the Option key, choose GO from the menu and select LIBRARY.


6. From the Library drag the CACHE fold and the COOKIES folder to the trash.


7. Delete the trash.


I was sceptical but thus far it has fixed my problem.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problem with waking from sleep with 10.8.2

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.