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

Sep 26, 2012 11:47 PM in response to KarlW

KarlW wrote:


I went through CalChloe's list last night but alas today the problem is back.


I've just reset the NVRAM as suggested by Juggler00 in the other thread about this issue. Fingers crossed.


If this doesn't work then it's back to stopping my Mac from going to sleep.


I tried even that but I still have the same problem as you. Did it work for you the last time you have tried the suggestions of the other thread? I have no idea but maybe I should do a clean reinstallation of the whole system? Don't know...

Oct 2, 2012 7:17 AM in response to Draadjesman

Draadjesman observes that the problem only occurs when the system goes to sleep based on the timer.


On my MacBook Pro, I've been noticing that I see the problem more often when I put the system to sleep using the Apple->Sleep menu item.


I do notice that the problem happens most often when the computer has been sleeping for several hours. And, I usually put it to sleep manually when I know I won't be using it for a while. So, maybe the method of sleep is not the issue so much as the duration....?

Oct 3, 2012 6:18 AM in response to SusanLake

I have a MacBook Pro7,1 after the 10.8.2 update my MacBook Pro does not wake from sleep. The white LED pulses as if it was happily asleep but refuses to wake. I have had times that it seems to wake and displays the login screen. There is no mouse cursor though and I am unable to do anything but force the machine to shut down by holding the power buttom in for more than 5 sec.

PLEASE APPLE use your BILLIONS to fix the update that seems to have caused all these problems.

Oct 6, 2012 1:05 AM in response to ipacers

This may be a dumb question but what is a "supplemental update" and how can it be found and installed? When I do a "software update", the recent updates have been for apps and they were all a few days ago. I have seen no updates via the app store in recent days that look as though they would have any relevance to the wake from sleep issue.

Oct 6, 2012 5:45 PM in response to SusanLake

I am not sure if I have the same problem.Touted here by someone responding to my post of a few days ago

I have a new MBP Retina SSD.

The MBP wakes from sleep. Ok BUT I notice something happens If I carry my MBP while it is sleeping. Especially if I turn it while carrying (or turn it to reconnect it standing in my ArcSouth stand)_

I can't get the MBP to respond. There is no light on the front , not pulsing no nothing. My initial thought has been that the MBP has shut down but I don't know. To get it respond I have pushed the power key a few times and the MBP reboots, with the dialog box that I seemed to have shut down my computer because of a problem, etc etc.

After reading some of these posts, perhaps the problem I have is NOT that the MBP shuts down but rather that it does not wake from sleep and the only way I got it to respond was to shut it down.

Don't know

Have NOT had the problem as long as my MBP is stationary. It is only motion that seems problematic, no matter if the MBP is sleeping during my hour commute to work (I.e carried in a secure backpack) or If I am carrying it from one room in my home to another.

Oct 10, 2012 8:53 PM in response to blubalu

Blubalu,

Your MBP simply did not awaken?

Did it matter if it was stationary or had been moved or carried?



I just reset my SMU

Will see if THAT makes a difference


MY issue only seems to occur if put my MBP into clamshell mode and then carry or move it.

The MBP either has shut down or does not want to awake from sleep. I cannnot determine which of those two states is happening.


Mine is a new Retina MBP so maybe there is something unique to that new model

Oct 18, 2012 9:54 AM in response to SusanLake

I have the same problem with my MBP 13" Mid-2010. After the ML 10.8.2 update my MBP won't wake always from sleep (sometimes it actually does wake up). I tried PRAM reset, SMC reset, clean install of Mac OS X (10.8 from the app store, which installed immediately to 10.8.2 (?). The problem of not waking up occurred from then on less frequent. After installing the iLife and Java update yesterday, my Mac won't wake at any given moment after closing the MPB or after choosing the sleep option provided by the Apple menu in the top-left corner...


Any ideas?

Oct 20, 2012 6:46 PM in response to Daan Wielens

resetting SMU did nothing for me. My MBP awakens easily if I sleep it from the Apple menu or let it go to sleep per what I set in Energy Saver preference

I Only have issue when reconnecting the powered up - but lid closed MBP to my Thunderbolt monitor.

That seems to cause deep sleep or shut down. I now wonder if my issue is related to the MagSafe connector of the Thunderbolt display or the converter I need to use to connect my MBP to the Thunderbolt monitor.

Last night when I went to manually power up the "dead" Mac I also was alarmed as the power button on the MBP did not respond for four or five pushes. FInally, a heavy push on it got the Mac going.

Very weird

Oct 22, 2012 7:26 PM in response to Tak Boleh Sebut

sorry you, too, are having a problem


I took my MBP Retina to our apple store this weekend

Genius is convinced my MBP does not shut down but, rather, goes to sleep so i have a variant of the "not wake up" problem . But 99% of the time only when trying to re attach to my Thunderbolt 27" monitor. Lots of tests, lots of console log checking. We tried to replicate the problem with the MBP on its own, attached to several different monitors.

Could not replicate

The issue could be my monitor.- I may have to take it in to the Apple Store (not fun; the thing weighs 30+ lbs)

The only other thing I just did was,in Energy Saver, to UNCHECK the Power Nap feature as I wonder if that might confuse the Mac when I reconnect it to my monitor

My MBP wakes up well all other times, just not when put to sleep via closing lid (clamshell mode) and then attaching to my monitor.

Very strange, indeed


Tak Boleh Sebut, please post if Apple give you any infornation.

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.