El Capitan Frozen After Sleep

arcticmed wrote:

I wish some Apple tech would moderate some of these forums like Microsoft does with their forums.

They do, to some extent - someone from Apple contacted me based on my involvement in this thread.

I've not heard anything from them in a while, though.

I've got a 15 inch MacBook Pro (mid-2015) - 2.8GHz i7 - basically a brand new machine. Came with El Capitan (now 10.11.1), didn't migrate apps from my last MBP, just installed everything fresh and copied over some folders w/ data. When leaving the machine on overnight (lid open, Mac drops into sleep mode) the Mac will not wake - this happens 1-2 times per week. It will slowly display a login but the KB is unresponsive. Mouse pointer moves but is not clickable.

If I wait around long enough (usually 5-10 minutes) I start seeing notifications about email pop up. I've even tried typing in my PW at the login screen even though it was unresponsive and a few minutes later the astericks appear in the PW area, but it can take another 5 minutes. Even then, the machine is unusable and I have just power the MBP down and restart from scratch - a full reboot.

My MBP is connected to an Elgato Thuderbolt expansion hub with a Magic Trackpad 2, an MS Ergo KB and a Dell 4K display running max res. I run the displays side by side to have as much real estate as possible.

Reading through this thread I upgraded my copy of VM Ware from 6.X to the latest 8.1, though I normally don't have it loaded (and in fact it wasn't running on my most recent lockups) - I doubt this was the cause but upgraded nonetheless.

I run Time Machine and it's backing up to a NAS based array (Synology device on network). The lockups MAY have been happening when TM was trying to perform backups. Looking through the logs via console I'm seeing quite a few messages indicating things were starting to go bad. Some selected events leading up to attempting to wake the machine:

12/12/15 9:51:16.000 AM kernel[0]: Sandbox: tccd(277) deny(1) mach-lookup com.apple.lsd.modifydb

12/12/15 9:51:16.257 AM tccd[277]: LaunchServices: disconnect event received for service com.apple.lsd.modifydb

12/12/15 9:58:27.130 AM WindowServer[165]: send_datagram_available_ping: pid 1124 failed to act on a ping it dequeued before timing out.

12/12/15 9:58:27.000 AM kernel[0]: IOThunderboltSwitch<0>(0x1)::listenerCallback - Thunderbolt HPD packet for route = 0x1 port = 10 unplug = 1

12/12/15 9:58:27.000 AM kernel[0]: AppleThunderboltDPOutAdapter<0>::hpdStateDetermined - deactivate paths

12/12/15 9:58:27.000 AM kernel[0]: IOThunderboltSwitch<0>(0x1)::listenerCallback - Thunderbolt HPD packet for route = 0x1 port = 11 unplug = 0

12/12/15 9:58:27.663 AM WindowServer[165]: handle_will_sleep_auth_and_shield_windows: Deferring.

12/12/15 9:58:27.667 AM WindowServer[165]: CGXDisplayDidWakeNotification [405928712853659]: posting kCGSDisplayDidWake

12/12/15 9:58:28.000 AM kernel[0]: IOThunderboltSwitch<0>(0x1)::listenerCallback - Thunderbolt HPD packet for route = 0x1 port = 11 unplug = 1

12/12/15 9:58:28.000 AM kernel[0]: IOThunderboltSwitch<0>(0x1)::listenerCallback - Thunderbolt HPD packet for route = 0x1 port = 10 unplug = 0

12/12/15 9:58:28.000 AM kernel[0]: AppleThunderboltDPPathManager<0>::createPath - path type 0x1: Initial Credits [int=0 src=0 dst=0] NFC Credits [int=14 src=11 dst=14]

12/12/15 9:58:28.000 AM kernel[0]: AppleThunderboltDPPathManager<0>::createPath - path type 0x2: Initial Credits [int=2 src=4 dst=1] NFC Credits [int=0 src=0 dst=0]

12/12/15 9:58:28.000 AM kernel[0]: AppleThunderboltDPPathManager<0>::createPath - path type 0x4: Initial Credits [int=2 src=7 dst=1] NFC Credits [int=0 src=0 dst=0]

12/12/15 9:58:41.651 AM watchdogd[797]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

12/12/15 9:58:46.853 AM spindump[1074]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-12-12-095846_Browncoat-3.user space_watchdog_timeout.spin

12/12/15 9:58:46.877 AM watchdogd[797]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-12-12-095846_Browncoat-3.use rspace_watchdog_timeout.spin)

12/12/15 9:59:06.708 AM watchdogd[797]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

12/12/15 9:59:09.374 AM spindump[1074]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-12-12-095909_Browncoat-3.user space_watchdog_timeout.spin

12/12/15 9:59:09.377 AM watchdogd[797]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-12-12-095909_Browncoat-3.use rspace_watchdog_timeout.spin)

12/12/15 9:59:15.796 AM WindowServer[165]: send_datagram_available_ping: pid 935 failed to act on a ping it dequeued before timing out.

Having been developing on Macs exclusively for the past 8 years with zero issues like this, it's a bit disconcerting.

I'm running El Capitan 10.11.1, MBP retina 2015 and running virtual box. My guess is that OS X does not work well with virtualization software or something. I even changed the settings using local login versus icloud verification and all failed. I even have automatic login, etc.

So this is what I had done so far. Clean install of El Capitan erasing everything. (I was so happy I made a USB install of El Capitan because I bricked the mac somehow when I formatted the hard drive and it would not install wirelessly, kept keeping some error message. Used the USB install method and recoved!!!)

Reinstall Virtualbox 5.0.10. At first it didn't hang after returning from sleep but after the second day it started having the same issue again. I removed VB 5.0.10 using the uninstall tool from VB. Reinstalled an earlier version that I did not have any problems with v5.0.6 and now no more problems. However, before I installed v5.0.6 I had install the new update for El Capitan to 10.11.2 (though on the release note there was no mention of login/sleep issues).

Now my MBP runs overnight with VB running in the background doing video tasks etc and so far for the past 3 days with constantly on, I have not had any problems when waking the mac from sleep. This is what worked for me. I have no clue about VM ware or other software but I know with VB at least the prior, not the newer version, worked flawlessly.

So, for days now I've been trying to isolate this problem. But before I go on with that I've discovered, I must say that since 10.11.2 came out, the SBBOB has not occurred again; perhaps others can add to this observation to the contrary if it is still occurring on their MB/MBP (note again, I am running a 6 core, 32GB RAM, 1 TB SSD Mac Pro WITH 5 attached discs (USB3 and Thunderbolt)).

But, before 10.11.2, here is what I tried and discovered: again, I was just trying to isolate the problem while hopefully keeping it from occurring (albeit, I can recover in about 3 mins). My suspicion (gut feeling) was that it was somehow related to Window Manager or some other process that was holding a lock, whatever, at the system level).

1. Shut off daily put Mac to sleep at midnight, wake up at 5:30 AM. (un-ticked start/stop boxes)

STILL OCCURS

2. Stop putting discs to sleep when possible. (un-ticked box in settings)

STILL OCCURS

3. Shut off putting monitor to sleep after 30 mins (set to never).

STILL OCCURS

4. Turned off screen saver (set to never).

STOPPED OCCURRING

I don’t know if the last one was “it” or if it was just that I was no longer involving a “sleep” event of sorts that was triggering behaviour in Window Manager somehow, but it did stop the SBBOD. I did one morning get a successful shift-control-option-command-period tgz file but have not as yet examined its contents.

But, now I’ve put everything back to “normal” with no SBBOD since 10.11.2. (By put it “back to normal” I reversed in order the four steps above).

Interesting - didn't realize 10.11.2 was out (I usually just wait until the notification comes up) - downloading that now. Also, I didn't realize my screen saver was set to activate after 20 minutes. Turned that off since I have the display power down after 15 minutes anyway. I'll post back in here if this does happen again, however if I don't post, it's not happening. Thanks mdturnerinoz.

Folks:

Sorry to report, but I was ahead of myself on 10.11.2 having a "solution" to this problem. The same SBBOD occurred on my Mac Pro again this morning when I first logged in (I left it in my Mac Pro in its usual wake-up mode as stated in my last posting).

Albeit, it is occurring less frequently than before (this is the first reoccurrence since 10.11.2), but 10.11.2 was not the panacea I'd thought; I hope your experiences are more positive.

Oh well ...

i updated the 10.11.2 ,but the problem is still exist, it seem like the bug not fixed ..... when i close the cover , mac is sleep , then take few hours, open the cover , login the account , the mac is frozeen , then is crashed ,,, each time the crash log is different.... i check my hardware all of them are good , i call the apple tech support ,hope can fix my problems..

My MacBook Pro is 1 week old today. It came pre-loaded with El Capitan from Best Buy. Downloaded all updates immediately. I've noticed the same crashing as everyone else after a sleep time of overnight or so. Unable to wake it without hard-booting the start button. Today I did that hard boot and after it went to sleep for only 15 minutes, I had to hard boot it again. Not what you should expect from a $2500 Mac.

TThat's interesting. Do you have any kind of virtualization software installed? I know I had to revert to an older version of virtualbox and now i am not experiencing any issues regarding the frozen lock screen/screen saver after extended period.

HOwever er I think I have a new problem now with an external two button mouse with usb dongle. Again it worked fine before and for some reason at times it becomes unresponsive for a bit and then works fine then skips all within a few minutes. I even tried another mouse I had and still issues. I have not tried a Bluetooth mouse yet. the track pad seems to do ok.

IM wondering if this is an OS X issue not playing nice or some other bug

Right out of the box it did it. The only software I had on it was the updates when it first happened. That time it didn't even sleep first. It finished up the downloads for Updated El Capitan, etc. and it locked up. I'm not even sure what virtualization software is, but my only software other than what came on the computer is Photoshop Elements.

WWow that is totally screwed up. I came from Windows and am still a fan of Windows in general. But got a Mac so I can develop apps for the iPhone and actually like using it. windows is not perfect but I've found neither are macs. Virtualization allows you to run a copy of Windows within the OS X environment without resorting to boot Camp. You can basically run both Mac Windows and even a variant of Linux and even another copy of OS X all at the same time without leaving the host OS X desktop.

OThers er on this post are running VMware and having the same issues. Therefore since you have a virgin machine and having the same issues it must be the software that's messed up. You can try doing a fresh install of OS X to see. But make sure you make a usb drive of el capitan. I accidentally "bricked it" by accident when I reformaated the ssd partitions and it would reinstall over wifi. I freaked out but finally remembered I had made a usb copy and installed from there.

I switched to Mac in 2009 and really no problems. Guessing there will be an explanation at some point. Thanks

Hi all,

I also had Virtual Box and reverted to the older version, but it did not solved the problem. Also removing it completely (with their script) had no effect (removing kernel modules etc.). I also expected the 10.11.2 update to fix the bug, but I am actually typing this message with an external keyboard and an external mouse... and a completely unusable laptop.

My machine was locked two times this day, and even hard reboot did not solved the issue (also did all the NVRAM and SMC things with no effect). This is one of the most annoying bug I ever had with OS X...

If I check :

- SMC reset did not solved the issue,

- NVRAM reset did not solved the issue,

- Never had VMWare installed,

- Removing VirtualBox did not solved the issue,

- Older versions of VirtualBox did not solved the issue,

- The fact things where connected in USB before does not seem to be the cause (must be confirmed),

- Hard reboot almost never solve the issue,

- The last 10.11.2 update did not solved the issue...

Waiting by rebooting or going to sleep several times seems, with patience, seems the only temporary cure.

Guesses ? Someone having a log in the console that shows something interesting ?

sSorry to hear.

YOu you may want to consider doing a clean install of OS X. Format the Hd then reinstall El Capitan. then lleave it on overnight without installing anything to see if the issue is something else besides being software related. Then update e capitan. Then install virtual box 5.0.6 And not 5.0.10.

THise is were the steps I took And I have not had any issues since then. I even run virtual box overnight with processes running and have not had any issues.

if you are still having issues with it after the clean install I would bring it to Apple Store with it locked up and have the geniuses figure it out given that all you have is El Capitan.

Yes, an thank you for sharing the way you fixed this.

I will do this, having no other solution, but tis is terrible to have no explanation on such a problem.