After installing Yosemite, my macbook air crashes every time it wakes from 'longish' sleep

Quote from Drugstore: "I'm sure it would have never been released under Steven Jobs"

Well, I'm afraid it would. I remember big trouble with wifi-connections when OS X 10.7 Lion was introduced. That was a real buggy release for most users.

Yosemite has some bugs and these seem to be nasty for some users, but to put this a bit in perspective here's the average evaluation-score for Yosemite in the Mac App Store

So Yosemite seems to make a lot of people happy.

I Have a 2008 unibody Macbook and i have a multitude of crash problems with Yosemite. Worked great on first install then froze from sleep then froze on start up 10 times before i finally got it to start up, its a nightmare. Absolute rubbish and im going back to Mavericks sadly. All the hype and its completely flawed, Steve Jobs must be spinning in his grave!

You sound like you work for Apple, what a load of pias rubbish. ive never had problems like this with any previous OS

Same issue with my MacBook Pro (Mid 2012)... nothing plugged-in but the power, yet to paraphrase the old song: "Waking up is hard to do!"

Same problem on 27" desktop late 2009.

I have the same problem but the cause may be different

11" Macbook Air, mid-2012, Core i7

Nothing plugged in

If it sleeps for a few minutes it wakes up just fine. If it sleeps for a longer period it can only be started from the power button and appears to do a reboot (requires login from gray screen, apps reload, MS Excel notifies of unexpected exit)

I checked console logs and pmset logs to see what I could find.

1) Console logs show a memory linking error and panic

5/11/2014 9:51:01.909 PM pboard[201]: Attempt to unlink previous shared memory during startup returned an error. Continuing...

5/11/2014 9:51:02.197 PM sharingd[207]: 21:51:02.194 : Starting Up...

5/11/2014 9:51:02.206 PM sharingd[207]: 21:51:02.205 : Device Capabilities (Handoff:YES, Instant Hotspot:YES, AirDrop:YES, Legacy AirDrop:YES, Remote Disc:YES)

5/11/2014 9:51:04.212 PM fmfd[240]: Initialized sandbox

5/11/2014 9:51:04.272 PM ReportPanic[234]: Failed to connect (panicHeaderLabel) outlet from (ReportPanicAppDelegate) to (NSTextField): missing setter or instance variable

5/11/2014 9:51:04.272 PM ReportPanic[234]: Failed to connect (panicMessageLabel) outlet from (ReportPanicAppDelegate) to (NSTextField): missing setter or instance variable

5/11/2014 9:51:04.273 PM ReportPanic[234]: Failed to connect (reportButton) outlet from (ReportPanicAppDelegate) to (NSButton): missing setter or instance variable

5/11/2014 9:51:04.671 PM ReportPanic[234]: ReportPanic could not stat /Library/Logs/DiagnosticReports/Kernel_2014-11-05-215056_Jonathan-2.panic

2) pmset log shows a driver panic also

Sleep/Wakes since boot at 2014-11-05 18:40:02 -0500 :2 Dark Wake Count in this sleep cycle:0

UUID: (null)

Sleep/Wakes since boot at 2014-11-05 21:50:56 -0500 😁 Dark Wake Count in this sleep cycle:0

UUID: Unknown UUID

Someone else posted about manually shutting down wifi before sleeping the laptop. That is not a practical solution but I will try that later to see if it has any impact on the sleep/wake issue.

This did not help me. Will also try disabling Wifi before shutting down.

My most recent experimentation says that the issue does not present when wifi is disabled before shutting the lid. When I leave wifi enabled the problem presents. Sounds like a bug.

I solved the problem for my Macbook Air although it is not particularly elegant.

1) In the energy saver control panel turn off "Power Nap" for battery and power adapter

2) In the energy saver control panel turn off "Wake for Wifi Network Access" for power adapter

3) In the general control panel turn off "allow handoff"

I have not tried anything more detailed...i.e. to determine if one or more of the above could be turned back on. However, with all of those off the laptop is back to behaving normally.

The Console used to have a ton (thousands) of handoff messages in addition to the driver panics in my prior posting. I am guessing that some combination of very frequent "handoff" connection attempts and the power nap feature are conflicting. At some point I will try combinations of the above three settings to see if I can narrow it down.

Good luck,

j

Me too.

Yosemite 10.10.1 update seems to have solved the problem. I have it installed and since then, I have no problem waking up my MBA.

🙂 The recent Yosemite update to OSX 10.10.1 resolved my sleep wake issue for my MacBook Air when using a external speaker and Thunderbolt to HDMI external monitor adapter.

So glad they resolved my issues with the latest update.

Sorry, but the updated Yosemite 10.10.1 DOES NOT fix the problem.

more info: I just close lid to sleep. no monitor, no speakers, ntt'in. open lid, and it shows login screen, but trackpad and keyboard non-responsive. attaching usb mouse has no effect. hard restart only solution.