Sleep and Wake problems under Lion

I realize this is a Mac Pro discussion, but FYI I've had the same problem described by Sewer Sleuth on my late-2011 MacBook Pro 13/2.4G/128 SSD/Lion 10.7.2. The oddball behavior disappeared when I disabled the auto logout option in System Preferences under Security & Privacy ("Logout after nn minutes of inactivity").

I have an early 2008 MacBook Pro 15" running the latest Lion, with exactly the same symptoms.

I have tried all standard solutions: PowerButton, SMC reset, RAM reseated, (can't PRAM reset because it won't boot), etc., but it stays sleepy (black screen, tiny disk spin and SuperDrive click, with non-pulsating LED on screen unlock button). Is this logic board ugliness or wierd Lionnage?

Any thoughts on a real forced reboot (all battery out button action tried), so I can get the keyboard running and reset PRAM?

+1 on the sleep and fan issues.

Im running a 2008 dual Guad MacPro with GT 8800 graphics card (I think) and since updating to Lion I'm having these issues.

I now have an Apple TV but the problem of the fans spinning up to 100% was occuring before I got that. The only correlating factor seems to be 'waking for network access'. It seems Apple broke this for some of us in the Lion update.

It's hardly the only thing that broke but it's one of the most annoying!!! Hopefully a fix will be forthcoming...

Thanks Bill - will give this a try.

I'll just chime in with yet another useless Lion based macbook Pro 2010. The thing has been very close to being hurled into the fireplace but a new logic board was supposed to fix a selection of other issues. In the proces of months of calling Applesupport I've done at least 2 complete virgin installs, a full zero sum format, every combination of PRAM and SMC boots, pref resets and much more.

Day 2 after receiving it back from Group8 and a new and exciting problem now exists. It now has great difficulty in turning on (5min of flashing power light before it springs to life randomly) and if it sleeps for longer than 10mins it will very liklely need a power button kill and reboot. The sleep problem has intermittently been around pretty much since I 'upgraded' to Lion.

Lion is junk, Macbooks of 2010 vintage in my experience are total garbage; buy a Windows PC people. Unless you absolutely require OSX (no idea why nowadays??) I would now avoid it wherever possible. When I can justify the expense, and the Applecare contract dies, this will get a sacrificial visit to the driveway and I will relish driving over it with my car to be replaced with a PC.

Snow Lion (or whatever we get) I'm sure will be promoted as a total fix for the clattering disaster that Lion has proven to be for me.

Avoid like the plague.

Woah. Perhaps I should note that this is a minor problem with an easy work-around. It's annoying, but certainly not something that renders my computer "junk." In fact, Lion is quickly becoming my preferred OS (I am working with three of them at the moment): the interface is brialliant, the apps are efficient and memory handling works better than I've ever experience. I get nothing but jealousy from my PC-using pals. Catch it like the plague!

Herewith the update to my saga:

For me it turned out to be a logic board failure.

So this has meant a new MacBookPro because the original workhorse was "uneconomical" to repair at the young age of four...

Heheh..I have mellowed slightly and I may not actually run it over yet I suppose but I'll add that this has been dragging on for months now with a variety of official suggestions that haven't really worked. New logic board may have fixed the overheating and pinwheeling crashes but wake from sleep and wifi issues are well recognised by Support gurus and it normally ends with a "we can try this but 7.3 has been seeded to the devs, maybe it's best to just wait". Bah humbug..

Lion looks pretty, the machined ally Macbook looks pretty - nice work Ive m'lad. Years of OSX usage and 'it just works' faith have been destroyed by this really. In the last 2 months I've spent more time on the blower to support and with a non functioning doorstop than with a working computer. Angry, disgruntled forum punter I may well be but I can only imagine that others may have a less intrusive selection of issues.

Did you work out the problem with your iMac? I have the same issue with my MacBook Pro.

Mac Pro (Early 2008), 2 x quad-core 3.2 GHz CPUs, 14 GB RAM (yeah, I know, it's an odd amount of RAM... the two 1GB sticks that originally came with the machine failed and I had to pull them), 3 TB drive

I don't use auto-sleep, nor do I use "wake for network access" (it is switched off in Energy saver). Instead I manually sleep the computer (via Apple menu -> Sleep) when I go to bed and wake it in the morning. The computer wakes up just fine, except that sometimes the network doesn't come back - my network shares disappear and any attempt to access any network resources (web sites, file servers, etc.) fail; attempting to "ping" my router from the command line gets me an error message to the effect of "no buffer space" (sorry, I forgot the exact wording). If I go to the Network control panel and disable/enable the network adapter (under the "Configure IPv4" pulldown, set it to "Off", hit Apply, wait a few seconds, set it back to "Using DHCP" and hit Apply again) then the network comes back and everything is fine.

Note that this only happens maybe 1 out of every 5 sleep-wake cycles.

Same issue for me, exaserated by using a LED Cinema Display. I put the 2010 MBP to sleep (in clampshell mode) disconnect and go home.

Reattach in the morning, press mouse or keyboard and the machine fails to wake and display on the Cinema Display.

If I then open the MBP I see the login screen and while the trackpad works, clicking in the log in box doesn't work and the keyboard is none functional.

Only way out is to hold down power button on MBP and restart - never a problem under Snow Leopard.

Experienced the same thing with my Zeon 2x2.66 under 10.6.8. Sleep normally took about '3 seconds' max was now taking around 20 seconds while the cursor still visible. Did some research and someone suggested that a 'paused print document' was the cause. I opened my Printer Queues one by one and spotted an unprinted document on pause. Deleted it, and Sleep went back to normal. Worth a try...

Just tried - no dice, no unprinted documents in any of the print queues...

Ben, your dilemma is different than the post I originally replied to and the only thing I can offer is to try using the Console to troubleshoot. (Once my Mac was waking immediately after sleep, and after opening the Console I searched for 'wake' and found something called 'wake event.' The preceding text read '...USB caused wake event.' I removed an older USB hub (the only peripheral other then the mouse and keyboard) and that was that.)

You could try viewing the 'system log' files and search for words that might be relevant, like 'display, wake, keyboard, login, hang...' It could be a useless venture but sometimes the log files have clues hidden within the text. Just be sure to read the preceeding and following text lines should you locate a key word.

I don't use 10.7 and it might not be until 10.7.5 that I upgrade.

Hi pseifer, good thought. Took a look through console and the first error after the problem is:

AppleUSBCDC: start - initDevice failed

Attached to the Cinema Display are an external HDD (for TimeMachine), Plantronics USB Bluetooth (to pair with my wireless headset for Skype/calls) and my keyboard and mouse.

All these devices were working correctly this way before Lion so it's clearly a problem with Lion. I suppose the only hope is 10.7.3 but sadly I get the feeling this one will run and run...