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
Pharmacoapple,
I hope your MBP stays good.
Regular hard shut downs will damage your hard drive for shure.
But hard shut downs have absolutely no influence on the hard drive cable.
Perhaps you had a doa cable.
But it's more likely that you damaged the cable yourself when changing the old hard drive for your SSD.
The cable neither the hard drive have absolutely NOTHING to do with the sleep mode problem.
It is a bug in the graphic driver or somewhere in the graphical user interface of the OS
(as I mentioned before).
Re-installing OS Mountain Lion will not help.
The only easy workaround temporary solution for 10.8 is still:
to set the sleep mode into 'never',
untill Apple releases a working update.
By the way: the mentioned sleep mode problems DON'T appear on the newst 21,5 and 27 iMac's 2012/2013.
And they don't happen either in 10.7.5
Best regards,
Danny
The issue is still present in 10.9. I "resolved" it again by tinkering with the pmset options, disallowing the Mac to to into hibernate. For me it seems to be no hibernate, no crashing on resume.
The guy I was in contact with from apple has been reassigned, looks like we'll have to wait for another generous sign of Apple.
I really wonder if they found anything on the last try to get hold of this problem....
CalChloe's answer fixed my 2007 iMac for now. Dump Caches & Cookies!
My iMac was hybernating deeper than a dormouse.
10.8.3 : Now sleep seems to be working again.. for now.
I have tried everything and believe me the ONLY solution is to erase all and clean install.
It fixes the problem for good and so far we do not have the final explanation.
Just to let you know I was travelling without any of my home gear and I was glad to be able to restart from a 8Go key simply set up with Lion Discmaker.
Let's move on now !
I'm remember now, you can hibernate changing the number to 25
Type in your terminal
sudo pmset -a hibernatemode 25
Eu lembrei agora, você pode alterar para hibernar facilmente, abra seu terminal e digite
sudo pmset -a hibernatemode 25
Pronto! Só fechar a tampa e ele *** hibernar
www.site7dias.com.br
Rob (bonfire),
This was exactly my issue. Thanks for tracking down those log files and the new driver.
For documentation purposes, I upgraded from 10.7 to 10.8.2 and had the problem described—the computer woke into "dark wake" two hours after having been put to sleep, but became unresponsive. I hadn't made any changes to wake on LAN settings. The log on my machine was very similar to what Rob posted.
Upgrading the video drivers to the ones listed solved the problem, no further steps necessary.
It'll be interesting to see if this is addressed in 10.8.3.
Andrew
Hello Pharmacoapple,
As I posted on the 22th of February, try to do this:
TEMPORARY SOLUTION
To temporary solve sleep mode problems in 10.8.2 with every Mac,
is to change the sleep mode of the computer into 'never'.
Best regards,
Danny
Happy to report that my problem has been fixed.
My sleep-wake issue has started in January of 2013. Lasted for a few months since i couldn't find a fix for it (mid-2010 MBP, so no video card update)
Eventually in Aprl my hard drive gave in. Upon startup i got a kernal panic with hard drive failure. The MBP would not go past this screen, quite scary. The Apple store did a diagnostic and everything came out good. Then they did a VERBOSE diagnostic which showed an I/O error (input-output) AKA hard drive crashed.
I purchased a new hd (Samsung SSD 840, which works flawlessly btw). After replacing the old (defective) hd with the SSD upon attempting to reformat and partition the hd i received a horrid error message, "Partition failed: Unable to write to the last block of the device." Thought the SSD was DOA but that wasn't the case. Turns out the the hard drive cable was defective. Ordered a new one on Amazon replacing the old and the reformat and partition worked flawlessly and then installed OS X ML via internet recovery.
It's been almost 2 weeks and my MBP has been normally sleeping and waking.
Now, I am not advising that you all replace your hd and hard drive cable. But possibly the hard shut offs over time may have had an influence in the hd and hd cable failing. This may be where the root of the problem lies. Although it's hard to tell for sure.
Funny, I've also been contacted by an Apple technician recently, and he's sent me some information about what to do, to gather more info, should it happen again, which it "unfortunately" doesn't.
As stated above on May 10th, I've been running on 10.8.4 beta (12E55 by now) for a while now.
And guess what: I can really have my rMBP sit for 24+ hours, reopen, and it wont crash.
Whereas previously the screen would remain dark after opening the lid, it now turns on the backlight after about a second, and the resumeing goes on as expected.
My current pmset settings:
bash-3.2# pmset -g
Active Profiles:
Battery Power -1*
AC Power -1
Currently in use:
standbydelay 7200
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
darkwakes 0
gpuswitch 2
disksleep 10
sleep 30
autopoweroffdelay 14400
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 10
acwake 0
lidwake 1
I hope they are pretty much default, because I reset them after fiddling around and ran my tests with them.
My bet: 10.8.4 fixes the issue, and I assume it has/had to do with the display or graphics-driver.
Mine is fixed now, too, after runing disk repair and deleting cache and cookies from the Library.
"Mine is fixed now, too, after runing disk repair and deleting cache and cookies from the Library."
Permanently or temporarily?
I have reset the SMC on my iMac (thanks @stoopkidsgonnaleave). I have since set all Energy Saver settings back to default and from a sample of just 2 tests, it would seem to have fixed the problem. I will see how it goes for a day or two before declaring victory. I will report my findings.
BTW, my iMac has a SSD for the main drive or has this relationship been discounted?
Hmmm... well, based on various pieces of advice, I've:
1. Repaired permissions
2. Repaired the disk (there were no problems)
3. Cleared the Caches directory
4. Reset the SMC
Unfortunately, this morning, is was suffering from the black death again. This time it was already powered up when I got to it, but everything else was the same - black screen, not responsive to any inputs, etc.
The only thing I haven't done from what was on the above list was clear the Cookies.. I'll guess I'll do that as well, but I'm skeptical.
Has anyone else been on the phone with Apple? Are they aware that many people are having this problem, not just one or two? I'd do it, but my machine is not under warranty (it's a 2008 MBP), and they'll charge me for the priviledge. Does anyone know if they actually monitor these discussion lists?
It seems, after having some trouble, my recent status is that this morning my machine woke up without any problems, despite the fact that earlier this weekend one time my battery was empty, and another time my machine didn't wake up as expected. I also sent the issue to Apple, using the feedback form.
Actions I took so far: reset the SMC, and followed the solution from CalChloe.
Problem with waking from sleep with 10.8.2
