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
Mac Pro 2008
Still no solution. Upgraded GeForce 120 driver to latest from NVIDIA.
I could force machine to sleep / wake up.
When left to own devices, machine will sleep but not wake up.
This is SO frustrating.
Eric
I know this is mostly about the 10.8.2 update bug, but I'm on 10.7.5 and still have the "wake from sleep" issue....I've played with the sleep settings, I had it on NEVER at first, then this issue started, so I changed it to 3 HRS, and it started to work fine again -- for about 2 weeks. Now it's back to not waking up again, but it's not consistant, it's a crap shoot whether it will wake up or not. Not sure if this is related, but I know my battery is 3 years old and probably needs replacing soon, but it still charges fine and has the same run time as it always had. Anyone else have this problem on 10.7.5?
~Billy
Thanks Danny....I'll give it a shot....
I was having this issue bad yesterday, but today, it's been waking up like normal -- all day....
Of course now since I've mentioned it, it'll probably start staying asleep on me now....LOL....
Not sure about how to change the battery, I have a mid-2009 MacBookPro, and I know there's no battery compartment, it's built into the laptop.
~Billy
I'm left hopless still.
MBP mid-2010 running ML 10.8.2
I've:
1. Reset PRAM + SMC
2. NO VIDEO CARD DRIVERS AVAILABLE TO INSTALL (Nvidea 320M) unlike the other cases where it fixed the problem
3. Have delted:
com.apple.screensaver.plist
com.apple.screensaver.plist.lockfile
all it did was remove my login screen
4. Have done a Clean install -- the problem did not happen for 5 days (a record) a then happened again
5. Repair disk permissions several times
Still no solution.
Anyone have any other advice?
Thanks
Danny,
Unfortunately this has not solved my problem.
I've changed the sleep preferences to never for computer sleep but not display sleep, as it's rather damaging in the long run.
After changing computer sleep to never, the problem still persisted.
*This is extremely frustrating and I hope that Apple fixes this already!
so, still no real fix here? really disappointing, i must say.
same problems as most in here, mid-2009 macbook, running 10.8.2.
i also suspect it has something to do with the graphics card, as I do not remember experiencing this problem when the 'better battery life' option was selected in the energy saver preferences, as opposed to 'higher performance'. has anyone experienced / tested this? i'm tempted to return the settings to 'better battery life' to test this theory, even though such a setting is detrimental to my workflow.
hi trypt,
yes, i did note your post and i thank you for it, but a clean install is a hassle (but not unsurmountable) given you're not even sure that was what fixed it. if anyone has a more precise option, i'd love to try that first.
cheers,
thom.
A while back someone mentioned that they deleted some files and it fixed their wake problem. The files were:
com.apple.finder.plist
com.apple.finder.plist.lockfile
What does this do?
I've deleted them back then because they said that the file kept replinishing itself, but mine has never come back, and it's still missing. Is that going to give me any issues?
I have also noticed some funny things going on every now and then, like discs not reading and even a Kernel popped up and made me do a hard shutdown. I've also noticed that iMovie will slow to a crawl sometimes, as well as other programs sometimes.. Not sure what's going on.
But on a good note, since I've changed my energy settings again it stopped my waking issue for now. Who knows when that will start up again though. But I'm not running 10.8.2 like most of you on this thread. I'm still running 10.7.5.
~Billy
that's exciting re. 10.8.3! unfortunately i can't be a guinea pig for the moment as over the last week i've managed to fix (i say fix but really it's a workaround) my sleeping issues on 10.8.2.
as far as i can tell the fix will only work for dual-graphics card macbooks (NVIDIA geforce 9400M / geforce 9600M GT on 2009 macbook, for example) that allow the user to switch between the two in energy saver preferences. i've simply moved my graphics performance from 'higher performance' to 'better battery life' and i haven't had a sleep related issue in almost a week. i'm almost certain this has solved the issue.
it is a workaround and not a proper fix as i would prefer to be using the full graphics capabilities of my computer..
i'm waiting with bated breath to hear 10.8.3 experiences..
That's basically what I did too. I have the same model and graphics cards as you do. Mine has been working correctly now for about 2-3 weeks now since I've changed those settings, but this issue seems to come back when it feels like without warning. So I'll post it again when the issue comes up in the future.
~Billy
Hello Phased,
W're dealing here with two sleep issues: macbooks and other mac's.
It's great that your workaround of the performance setting to 'better battery life' works,
but this unfortunately won't help users with a mac pro or iMac.
Best regards,
Danny
Hello everyone,
with 10.8.3 my MBP still is not able to wake from deep sleep.
The greyed Desktop is shown for a view seconds while trying to restore. After that a complete reboot is done by the system. Very time-robbing.
After the hidden catch with the not working airplay feature I can say that 10.8 is the most disappointing OS X ever seen.
my mac: MBP 5,1 (early Unibody)
Tobias
UPDATE- 10.8.3. has NOT solved my sleep-wake issue
Very disappointing.
Danny,
I have set the sleep to never and have been shutting down every night now.
Although it's a temporary fix, it's extremely inconvenient and damaging in the long-term for display and battery health. What an extremely pathetic bug.
Any tips on how to downgrade to 10.8.1 before i reinstall snow leopard...?
Thanks.
Pharmacoapple,
Setting sleep to 'never' won't harm your battery in a macbook pro.
Since you can attach your power supply to it.
And because this battery has intelligent chips on board, he knows when to load, or not.
If you have your screensaver on, set it to 5 or 10 minutes and choose your computername,
your display won't damage. And set the backlite (F1 & F2) NOT to maximum, but let's say to 70 or 80%.
Restarting your mac, ipad or iphone regularly is important.
It helps - in simple words - cleaning up, regenerating and repairing several things.
Downgrading to an incomplete 10.8.1 won't be my advise.
Downgrade for just this sleep issue, although annoying, is a bit over-the-top,
but you have to decide yourself. Tips and tricks how to do downgrade can be found in another topic.
Make sure you back-up all your personal data before doing so...
Best regards,
Danny
Don't rejoice prematurely, me too thought I was rid of this wake from sleep issue after nearly a week without any troubles. BUT it occurred again after 6 days :
Mar 15 19:03:19 localhost bootlog[0]: BOOT_TIME 1363370599 0 Was the reboot after install
Mar 21 14:02:54 localhost bootlog[0]: BOOT_TIME 1363870974 0 Was the reboot after wake from sleep issue.
It occurred in the afternoon, after I came back from lunch, while before it used to be in the morning (I never switch off the machine for the night).
The trick that used to work, plug the iPhone, did failed this time.
So you have to be careful on your assumption that 10.8.3 did fix the problem, alas ..
Problem with waking from sleep with 10.8.2
