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)
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
My point of view is the problem is hard to fix because there isn't a single cause.
It appears that your Mac is asleep normally when something occurs that wakes it. Network activity, a timed maintence event, or a third-party program can fire the wake up signal. You Mac wakes as requested. Because the wake was not from the UI the Mac wakes in "dark wake / maintenance wake" mode. The display remains dark, keyboard, and mouse are not activated.
During the maintenance wake the Mac takes care of the condition that triggered the wake and then wants to go back to sleep. If you check the system log you should find a sleep command followed by a sleep failed command.
Programs can tell the system that they are not in a state to be put to sleep when the system wants to sleep. This is to protect critical operations. It also prevents your Mac from sleeping during a movie or when showing a Keynote presentation. Lots of other programs, both Apple and third-party, can tell the Mac not to sleep.
Something in the Mac tells the system not to go back to sleep following the maintenance wake. What that something is can be any app running at the time. On my machine its the XYZ app. On your Mac its the FGH app. On another user's machine its the ABC app. Or it might be a combination of apps.
The point is that during testing my Mac would wake in dark maintenance mode to handle the wake event normally. Once the event had been handled (all normal to this point), the Mac attempts to go back to sleep. This is where the sleep failure happens. The Mac never goes back to sleep.
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.
- MBP 13" mid 2012 i7
- DIY upgrade to 16GB DDR3-1600
- DIY upgrade to dual Intel 520 SSD 480GB
- CCC whole system from my old MB 13" early 2009 (10.8.2)
I had the similar problem, finished work on MBP, left the lid open and go out or goto bed, came back and press spacebar or enter twice, the screen woke up in pure black, I can see the dim led light at the edge of the screen. One thing to point out, if I left it to sleep mode but came back within 3~5 minutes, it will resume to normal, but longer than that it's dead black.
These are the things I've tried and didn't work:
*** There's this old widget called DeepSleep, delete it if you have it at all cost, it does nothing but mess up your hibernatemode. No matter what hibernatemode I've setup, it alters to 5 & 7, which are not compatibible with 10.8.2
These are the things I've tried and might have worked as the solution, in exact steps:
Now my MBP with 10.8.2 is working fine, I'll keep testing for upto a week to see if any comebacks.
I also check the update list, I have http://support.apple.com/kb/DL1611 installed.
I haven't installed http://support.apple.com/kb/DL1626, http://support.apple.com/kb/DL1633 and http://support.apple.com/kb/DL1609
Also attached my Terminal SS for ref.
That's about it.
For the moment 10.8.3 has been correct and the issue did not came back, BUT I'm still not relax about it and keep to charge my iPhone directly on a wall charger. Because if it happens again I will be able to wake up my MacPro just by pluging my iPhone in one of the USB port of the hub.
Until now every time the mac would not wake up after pressing a key on the keyboard, plugging the iPhone would switch on the lights of the hub and MacPro then wakes up. Does not work if the iPhone was charged through MacPro USB, disconnected and reconnected, it has to be disconnected before the machine goes sleeping.
Just in case it would help others ..
By the way, i just read in another thread that it`s a well known bug.
It only happens with 10.8.2 and 10.8.3. A lot of users (not all) have the same problem.
Newest imac's are not affected.
Temporary solution until Apple comes with an update:
set sleep mode into 'never'.
Sound not that optimistic and sounds like either always turn completely off or let run for ever solution.
As strange as it seems, I've stopped having this issue the day I unplugged an usb cable that was plugged to the apple screen I use with my MacPro (this usb cable was always there to charge my ipad or iphone).
Turning off 'Wake for network access' seems to have fixed the problem. MacBook Pro seems to be going to sleep normally now. Anyone else having similar success?
I'm happy to report that the 10.8.2 Supplemental Update has fixed this problem for me. No problems at all today, deep sleep or not. Yay! 😀
With "wake on LAN" off everything seems to be fine. At least until Apple will address this issue with 10.8.3
: o )
this is the driver I used - I have a Mac Pro "early 2009"
http://www.nvidia.com/object/macosx-304.00.05f02-driver.html
I'd be curious to see, does this occur with all types of sleep occurrences?
Macs will go to sleep 1 of 3 ways:
1. Software timeout sleep
2. Clicking > Sleep
3. Hardware mechanisms: On portables closing the lid activates a magnetic sleep switch, on desktops quickly pressing the power button sends it to sleep.
Anyone willing to post a copy of their logs from after attempting to sleep? If so:
1. Mark the time you put the system to sleep
2. After a reboot open Applications > Utilities > Console
3. Under kernel.log, provide the logs from the time your system went to sleep, till whatever the current time is.
Might be interesting to see if there's some weird issue causing the systems not to enter sleep correctly.
I did a variant on the advice here that seemed to work
- Deleted my cache under both users and hard drive (emptied trash)
- Reset SMC
Seems to now be fine, although I still have no internet connection via wifi for a minute or two after it wakes. Maybe I'll try the disk repair in case that works somehow! Anything to avoid another lengthy re-install!
I received an email from an Apple Senior Specialist along with his phone number in regard to this issue. He sent me instructions on how to gather the files he needed to investigate this problem, along with a program called Capture Data. I've aleady sent the information, so let's hope they gather enough data from us to get a fix out.
After I had a few of these incidents I stopped allowing my Mac Pro tower to sleep, instead shutting it down each night. Interesting that unchecking "wake for Ethernet network access" solved the problem for another user. I'm pretty certain I had that and "sleep disks when possible" checked by default. I'm going to leave the sleep disk option checked and turn off ethernet access and put it asleep tonight to see what happens in the morning.
@jadewocky: Thanks for your observations. The default setting on my MBA is to sleep first and after 4200 seconds go into hibernation. Use the 'pmset -g' command for more info. When hibernate starts, the hibernatefile (/var/vm/sleepimage) is updated. So, if the problem only occurs after a long sleep period, it might be related to the fact that the laptop switched from sleep into hibernation. This switch is triggered by a timer... Does the problem occur when put to sleep manually and wake happens within this 4200 seconds period?
ipacers wrote:
Did anyone have any success with the 10.8.2 Supplemental Update released today?
+1
I would like to know this, too. I wiped my machine and re-installed 10.8.2 only to find it freezing up again (seemed to happen to me after a period of inactivity, as well as after going to sleep). After a lot of digging I found a copy of 10.8.0 and did another clean install. I'm sitting at 10.8.1 now and it has not frozen up since (was freezing up about a dozen times a day).
I am very wary of upgrading to 10.8.2, but I am anxious for a fix since I can't re-install Aperture from the App Store until I do... :-/ Also, the (1) badge on my App Store icon is taunting me.
Yesterday I followed Chet's suggestion to perform an NVRAM reset. For the first test I kept 'Wake for network access" disabled and put my MBP to sleep yesterday evening. This morning it woke and works like a charme again.
Thanks to Chet for this hint!
Tonight I'm going to reenable "Wake for network access" (althouth I've never needed this in the past) and tomorrow morning will show if the problem is fully gone.
Problem with waking from sleep with 10.8.2
