Sleep/wake crash OSX Mavericks, Macbook Air 2013

I have a 2013 MBA and have found what seems like a solution for me. When I first got the notebook, I had this issue a lot. After upgrading to Mavericks, it seemed like the issue went away, but then it came back. What I have done is I have just been careful to let it wait a minute after automatically entering sleep mode before I try and wake it. This has worked great for the issue that I have been having when the crash occurs just trying to wake the machine too quickly, but I don't know if this will work for everyone.

The only way I can reproduce this problem is to let the computer sleep or force it to sleep and then quickly wake it up. If the machine is asleep for some small number of seconds then it wakes up normally every time. Energy Saver settings and battery vs. a/c are irrelevant.

MBA 2013, 10.9.1.

Same problem for me on a MacPro tower, 2009, running mavericks, never had any issues till I upgraded the harddrive and put mavericks on it

any ideas ???

Anonymous UUID: C78319BF-6FC4-7A78-D0EA-1D7D04E2A9EB

Tue Jan 7 10:04:20 2014

panic(cpu 0 caller 0xffffff8019cdc19e): Kernel trap at 0xffffff7f9b006af7, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0x00000000176fb000, CR3: 0x000000001c784000, CR4: 0x00000000000206e0

RAX: 0xe94f5bf898930094, RBX: 0xffffff806cf35f88, RCX: 0xfffffffff41091c8, RDX: 0x7fffffffffffffff

RSP: 0xffffff833886bfa0, RBP: 0xffffff833886bfb0, RSI: 0x0000000000000002, RDI: 0xdeadbeefdeadbeef

R8: 0xffffff801a180f20, R9: 0xffffff801a201910, R10: 0x00000000000003ff, R11: 0xffffffffffffffff

R12: 0xffffff806d938e30, R13: 0xffffff8050f2fcf0, R14: 0x0000000000000000, R15: 0xffffff8050f2fcf0

RFL: 0x0000000000010282, RIP: 0xffffff7f9b006af7, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x00000000176fb000, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff8328bc1c50 : 0xffffff8019c22f69

0xffffff8328bc1cd0 : 0xffffff8019cdc19e

0xffffff8328bc1ea0 : 0xffffff8019cf3606

0xffffff8328bc1ec0 : 0xffffff7f9b006af7

0xffffff833886bfb0 : 0xffffff8019cd6aa7

Kernel Extensions in backtrace:

com.digidesign.fwfamily.driver(9.0f4)[EA9004EA-D8CD-1CA7-6281-17C82B2AF0EF]@0xf fffff7f9aff8000->0xffffff7f9b019fff

dependency: com.apple.iokit.IOFireWireAVC(4.2.2)[90DCC875-0911-3857-8D4E-838CA0149D3F]@0xff ffff7f9ab71000

dependency: com.apple.iokit.IOAudioFamily(1.9.4fc11)[5077FB4F-0903-3D79-8280-5B2341E93BF3]@ 0xffffff7f9afc1000

dependency: com.apple.iokit.IOFireWireFamily(4.5.5)[C83215A8-3406-35EC-8C24-A1746E9565DF]@0 xffffff7f9a59e000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

13B42

Kernel version:

Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64

Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393

Kernel slide: 0x0000000019a00000

Kernel text base: 0xffffff8019c00000

System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 4403458852143

last loaded kext at 249364858340: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f9c0f2000, size 65536)

last unloaded kext at 433269969597: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f9c0f2000, size 57344)

loaded kexts:

com.digidesign.fwfamily.driver 9.0f4

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.filesystems.autofs 3.0

com.apple.driver.AudioAUUC 1.60

com.apple.driver.AppleTyMCEDriver 1.0.2d2

com.apple.driver.AGPM 100.14.11

com.apple.iokit.IOBluetoothSerialManager 4.2.0f6

com.apple.driver.AppleUpstreamUserClient 3.5.13

com.apple.driver.AppleMCCSControl 1.1.12

com.apple.driver.AppleUSBDisplays 360.8.14

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.kext.AMDFramebuffer 1.1.4

com.apple.driver.AppleHDA 2.5.3fc1

com.apple.driver.AppleMikeyDriver 2.5.3fc1

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.0f6

com.apple.AMDRadeonX3000 1.1.4

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleLPC 1.7.0

com.apple.kext.AMD5000Controller 1.1.4

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleHWAccess 1

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.4.0

com.apple.iokit.SCSITaskUserClient 3.6.0

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 35

com.apple.driver.AppleFWOHCI 4.9.9

com.apple.driver.AppleUSBHub 650.4.4

com.apple.driver.AirPort.Brcm4331 700.20.22

com.apple.driver.Intel82574L 2.6.1b1

com.apple.driver.AppleAHCIPort 2.9.5

com.apple.driver.AppleUSBEHCI 650.4.1

com.apple.driver.AppleUSBUHCI 650.4.0

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleACPIButtons 2.0

com.apple.driver.AppleSMBIOS 2.0

com.apple.driver.AppleACPIEC 2.0

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 216.0.0

com.apple.nke.applicationfirewall 153

com.apple.security.quarantine 3

com.apple.driver.AppleIntelCPUPowerManagement 216.0.0

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 10.0.7

com.apple.driver.AppleUSBAudio 2.9.3f17

com.apple.driver.DspFuncLib 2.5.3fc1

com.apple.vecLib.kext 1.0.0

com.apple.iokit.IONDRVSupport 2.3.6

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.0f6

com.apple.iokit.IOAcceleratorFamily 98.7.1

com.apple.iokit.IOSurface 91

com.apple.driver.AppleSMBusController 1.0.11d1

com.apple.iokit.IOBluetoothFamily 4.2.0f6

com.apple.driver.AppleHDAController 2.5.3fc1

com.apple.iokit.IOHDAFamily 2.5.3fc1

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.driver.AppleSMBusPCI 1.0.12d1

com.apple.kext.AMDSupport 1.1.4

com.apple.AppleGraphicsDeviceControl 3.4.12

com.apple.iokit.IOGraphicsFamily 2.3.6

com.apple.driver.AppleSMC 3.1.6d1

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 5.5.1d27

com.apple.iokit.IOAudioFamily 1.9.4fc11

com.apple.kext.OSvKernDSPLib 1.14

com.apple.iokit.IOFireWireAVC 4.2.2

com.apple.driver.AppleUSBHIDKeyboard 170.15

com.apple.driver.AppleHIDKeyboard 170.15

com.apple.iokit.IOUSBHIDDriver 650.4.4

com.apple.driver.AppleUSBMergeNub 650.4.0

com.apple.driver.AppleUSBComposite 650.4.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.0

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOAHCISerialATAPI 2.6.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.0

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IO80211Family 600.34

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOUSBUserClient 650.4.4

com.apple.iokit.IOAHCIFamily 2.6.0

com.apple.iokit.IOUSBFamily 650.4.4

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 278.10

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.AppleKeyStore 2

com.apple.driver.DiskImages 371.1

com.apple.iokit.IOStorageFamily 1.9

com.apple.iokit.IOReportFamily 21

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 2.0

com.apple.iokit.IOPCIFamily 2.8

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

com.apple.kec.pthread 1

Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.4 GHz, 28 GB, SMC 1.39f11

Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB

Memory Module: DIMM 1, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732314755363746393333334700000000

Memory Module: DIMM 3, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

Memory Module: DIMM 4, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

Memory Module: DIMM 5, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

Memory Module: DIMM 6, 8 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732314755363746393333334700000000

Memory Module: DIMM 7, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

Memory Module: DIMM 8, 2 GB, DDR3 ECC, 1333 MHz, 0x80AD, 0x484D54333235553743465238432D48392020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)

Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en2

PCI Card: ATI Radeon HD 5770, Display Controller, Slot-1

Serial ATA Device: HL-DT-ST DVD-RW GH80N

Serial ATA Device: Hitachi HUA722010CLA330, 1 TB

Serial ATA Device: Hitachi HDS721050CLA362, 500.11 GB

Serial ATA Device: SanDisk SDSSDX240GG25, 240.06 GB

USB Device: Keyboard Hub

USB Device: Apple Keyboard

USB Device: Hub

USB Device: Apple LED Cinema Display

USB Device: Display iSight

USB Device: Display Audio

USB Device: BRCM2046 Hub

USB Device: Bluetooth USB Host Controller

USB Device: Kensington Expert Mouse

FireWire Device: unknown_device, Unknown

FireWire Device: built-in_hub, Up to 800 Mb/sec

FireWire Device: Mbox 2 Pro, DIGIDESIGN, Up to 400 Mb/sec

Thunderbolt Bus:

Got this MBA for Christmas, immediately updated from 10.9 to 10.9.1, and this happened to me for the first time last night. I had closed the lid most of the way - not all the way - and then reopened it immediately, and the screen was black. Nothing I pushed would bring it back to life - tried brief and extended push on power button, clicked any number of keys - nothing. In Battery I had Display set at turn off after one minute, UNchecked put HD to sleep when possible, UNchecked power nap; in Power Adapter had Prevent Sleeping checked, put HD to sleep unchecked. So last night I had what seemed to be a dead computer. I closed the lid, and in a few minutes went upstairs to bed, but then came back down because it was worrying me - opened the lid and voila! Back to life. Closed the lid most of the way - remember I have it set to never turn off the HD, just the display - I run World Community Grid computing 24/7 so I don't want it to shut down ever except manually.

So this morning I was going to call Apple, but when I opened the lid I had this error message about the sleep wake failure, reported it to Apple. Then I found this thread, and repeated YeOldMacFan's experiment - shut the lid then opened it immediately - and once again it "crashed" or whatever it's doing. I again clicked keys and tapped the power button, to no avail, then held the power button down for a while. The dark screen went blacker, and I knew it had shut down for real - meaning it had been asleep. And then it restarted, brought me back to this screen.

So YOMF is probably right - it has something to do with closing and quickly reopening the lid even if you've disabled sleep and power nap.

This is my first laptop since my 1990 Toshiba with whopping 42MB HD, so I'm unclear on whether closing the lid puts it to sleep even if you've disabled sleep. And last night it happened without closing the lid all the way - I was trying that to see if it went to sleep anyway, trying to determine if I had to keep the lid open a certain amount to prevent sleep.

I have found the same issue and the work around that I've found was to not put it to sleep with the lid. Manually choose the sleep option from the menu and then it will wake up like it's supposed to. It's a pain, but it's better than the 50/50 shot of waking up or not.

This isn't just an issue with laptops and lids. It is happening with a standard desktop iMac so therefore I don't believe it's related to a hardware issue but a 'wake up from sleep' fault.

I have deliberately started to put the machine to sleep instead of just using a hot corner to turn off the display. For part of the time it worked and others not. Unfortunately having to force a reboot has incurred a cost of corrupted data which is why this is such a big issue. I have lost information and I am as thorough as I can be in regular saving.

To re-iterate, this only happens since the Mavericks upgrade (? - the question mark is because I'm not sure it was ready for prime time!)

My company own a Macbook Air i5, with the same issue mentioned by several people.

I talked to Apple Support in Sweden today, and according to them is this "something the engineers know about", and "we have this in our papers". They expected this to be fixed in the next update...
I asked for a bug id, some way to track this issue so that I know when this will be fixed, but according to them they do not have an open bug list or any tracking of known issues.

I'm close to newbie on OSX/Mac, and have been really tired of the windows/microsoft world a long time, but this way of handling paying customer *****, big time. So, Ubuntu next 🙂

Well, nothing new here but I have the same issue on a 2009 model Mac Mini. Just upgraded from Snow Leopard to Mavericks and the same issues described above occurred. So it is not hardward, its the OS. When ever my mini sleeps the monitor never comes back and must reboot. I suppose we wait for a fix?

I just got back from where I have my servers and had found the same. One 2012 Mac Mini would not respond to keyboard and mouse, I went in from the net and it was fine. All week I've been sshing into it not realizing it was "hung" from a video, mouse and keyboard standpoint. It suggests it's not actually a crash, but that just the wake up of the keyboard, mouse and monitor is the problem. The dumb thing I did was forgot to go and see if the monitor came alive when I woke it from the network. That would have been interesting info for coming up with a workaround, but I didn't care at the moment, it's supposed to be a headless server with the sleep set to never. I just forgot to set it on that one.

The significance is that maybe your computers are not actually hung. If you have another machine around, logging in via ssh will let you reset it gracefully until they provide an update. Power cycling is risky.

If this is the case then screen sharing might work to regain control of the Mac.

FWIW, this has not happened to me again on my iMac (yet), and the two or three times it happened I did not lose any data, as others have reported. The Mac restarted where Ieft off, including open documents, so it happened after the versioning feature saved my place.

Hi guys - I've just tested this out and can report the following:

Once your mac has gone into this crash, you can still SSH into it. Yay! However you cannot Screen Share - that capability is dead.

You can execute a shutdown -r now command. This will do its best to nicely shut your processes down. It's up to the application to be smart about dealing with this event (e.g. saving work etc.). However upon "shutdown" the computer does not actual shut down. Meaning you still can't get it back "on" until you hard reset it.

Does anyone have any clever ideas on perhaps reactivating the windowing system or waking the keyboard via the command line?

For those who are interested, here's a sys log from my machine as it happens:

Me triggering "black screen death":

Jan 10 19:21:11 MBADD kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIO

ReturnSuccess) -- 0x6c00 ****

Jan 10 19:21:18 MBADD kernel[0]: AppleIntelFramebuffer::setPowerState(0x53871544d8e9ac55, 2 -> 1) timed out after 45390 ms

Jan 10 19:22:24 MBADD.local identityservicesd[82702]: [Warning] IMSetKeychainData: -25320 -- Could not store data for service: com.apple.facetim

e account: registrationV1 accessGroup: nil

Me logging in via SSH & executing shutdown -r now as root:

Jan 10 19:22:37 MBADD.local sudo[83484]: myadmin : TTY=ttys003 ; PWD=/Users/myadmin ; USER=root ; COMMAND=/usr/bin/su

Jan 10 19:24:01 MBADD.local shutdown[83510]: reboot by myadmin:

Jan 10 19:24:01 MBADD kernel[0]: Kext loading now disabled.

Jan 10 19:24:01 MBADD kernel[0]: Kext unloading now disabled.

Jan 10 19:24:01 MBADD kernel[0]: Kext autounloading now disabled.

Jan 10 19:24:01 MBADD kernel[0]: Kernel requests now disabled.

Jan 10 19:24:01 MBADD.local shutdown[83510]: SHUTDOWN_TIME: 1389342241 741248

Jan 10 19:24:01 MBADD.local NotificationCenter[83363]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local NotificationCenter[83363]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local Dock[83336]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Dock[83336]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local SystemUIServer[83339]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local SystemUIServer[83339]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local Finder[202]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Finder[202]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local Dock[200]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Dock[200]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local Mail[34434]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Terminal[191]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Terminal[191]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local NotificationCenter[229]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local SystemUIServer[201]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

Jan 10 19:24:01 MBADD.local Mail[34434]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local NotificationCenter[229]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

Jan 10 19:24:01 MBADD.local SystemUIServer[201]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

And from there it's all boot messages from after the hard reset.

Late 2010 iMac on Maverick. Same issue. I've tried every Apple suggestion and every reset and every reformat listed. I've completely "Erased" my HD and loaded Maverick. I did NOT restore from backup. I've discounted every external accessory and left every item as factory (in theory). The same problem occurs the first thing of EVERY morning. My computer will NOT wake from sleep in the morning. Keyboard and mouse dead. Power button or nothing.

I have found one solution that works every time however. When I leave the office I "SHUTDOWN" my imac, (I type this in a sarcastic tone). Very annoying issue. Have NO CLUE how to resolve. I have bought the new MacPro tower coming in February, maybe that will fix the problem.

A long time ago, killall -HUP WindowServer as root would force restart of the windowed side of the system. I doubt this would trigger the applications that get killed to save elegantly, but it would be interesting to test that. I also wonder if it would actually force a complete restart since it sounds like even the shutdown is bumping up against a hung process. The signal may bubble down, but usually it seems that apps are written to ask on the console if you want to save when triggered to close. If so, the save dialog will never be seen.

Bravo on the choice, a round Pro is in my future too I hope.

I have the problem on a MBP that has been rock solid running SL. It doesn't happen every time. I'm running some jobs that take several hours to complete, so if I have to leave the computer and return it is sometimes sleeping.

Sometimes I just get a blank screen and it only responds to power off, other times I get a login panel but when I try to enter the password I get a spinning wheel. I can move the wheel around.

I have tried ssh from other systems, but so far without luck. The last time, a linux avahi-discover reported ssh on IPv6 but not IPv4 which is what I have on the linux box. Only power off gets me going again (boot to another system, repair Mavericks system disk, which so far always says the disk can't be repaired, but doesn't find problems if I run a second repair). The disk repair seems to loose the most recent log entries, so console shows gap of several hours between the last entry and the reboot.

My 2007MBP started having problems waking from sleep immediately after upgrading to Mavericks (10.9.1). Twice I put it to sleep at night and found it with the fans running the next morning and it would not wake from sleep. I did a SMC reset and it seems to have solved the problem. Thanks ViShVa.