Display not awakening after Beta El Capitan 15A263e install

I hope your right. As i also have made no changes to my mac in the last month. The only solution I have found is to keep the disply on 24/7.

I'm on the GM candidate now, but have been having the "not waking up from sleep" issue through a number of these beta releases.

Here's the output from the suggested command, ls -1lt /Library/Logs/DiagnosticReports

Last login: Tue Sep 15 19:54:53 on console

MacBook-Pro:~ kxxx$ ls -1lt /Library/Logs/DiagnosticReports

total 19304

-rw-rw----@ 1 root admin 40088 Sep 15 21:12 com.apple.AmbientDisplayAgent_2015-09-15-211233_MacBook-Pro.crash

-rw-rw----@ 1 root admin 1551583 Sep 15 19:54 WindowServer_2015-09-15-195403_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 1548149 Sep 15 19:53 WindowServer_2015-09-15-195338_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 1551159 Sep 15 19:53 WindowServer_2015-09-15-195322_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 320 Sep 15 19:23 awdd_2015-09-15-192326-1_MacBook-Pro.awd

-rw-rw----@ 1 root admin 12889 Sep 15 19:23 awdd_2015-09-15-192326_MacBook-Pro.awd

-rw-rw----@ 1 root admin 16183 Sep 15 16:31 Spotlight_2015-09-15-163114_MacBook-Pro.wakeups_resource.diag

-rw-rw----@ 1 root admin 11781 Sep 15 16:30 com.apple.AmbientDisplayAgent_2015-09-15-163039_MacBook-Pro.wakeups_resource.diag

-rw-rw----@ 1 root admin 1567828 Sep 15 16:29 WindowServer_2015-09-15-162926_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 65885 Sep 15 16:29 SystemUIServer_2015-09-15-162918_MacBook-Pro.wakeups_resource.diag

-rw-rw----@ 1 root admin 1525324 Sep 15 16:28 WindowServer_2015-09-15-162859_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 1529729 Sep 15 16:28 WindowServer_2015-09-15-162843_MacBook-Pro.userspace_watchdog_timeout.spin

-rw-rw----@ 1 root admin 28910 Sep 15 07:39 backupd_2015-09-15-073942_MacBook-Pro.cpu_resource.diag

-rw-rw----@ 1 root admin 88726 Sep 15 01:03 powerstats_2015-09-15-010351-1_MacBook-Pro.diag

-rw-rw----@ 1 root admin 159370 Sep 15 01:03 powerstats_2015-09-15-010351_MacBook-Pro.diag

-rw-rw----@ 1 root admin 84566 Sep 15 01:03 powerstats_2015-09-15-010349_MacBook-Pro.diag

-rw-rw----@ 1 root admin 71957 Sep 14 22:20 WindowServer_2015-09-14-222057_MacBook-Pro.wakeups_resource.diag

MacBook-Pro:~ kxxxx$

Anyway, I noted the exact time when I couldn't awaken the computer (7:51.05) and captured the console entries from around that time. I shut down and rebooted around 7:54. Maybe someone can figure it out from this.

9/15/15 7:43:46.273 PM launchservicesd[88]: SecTaskLoadEntitlements failed error=22

9/15/15 7:43:46.298 PM appleeventsd[57]: SecTaskLoadEntitlements failed error=22

9/15/15 7:43:46.309 PM SIMBL Enabler for Sandboxed Apps[717]: Set up watching for containers directory at URL file://localhost/Users/kvatz/Library/Containers/

9/15/15 7:44:01.313 PM SIMBL Enabler for Sandboxed Apps[717]: Will terminate until reinvoked again by launchd.

9/15/15 7:46:26.435 PM mdworker[718]: Cannot find function pointer MetadataImporterPluginFactory for factory 37401ADE-1058-42DB-BBE5-F2AAB9D7C13E in CFBundle/CFPlugIn 0x7fbc88c11e30 </Applications/Thunderbird.app/Contents/Library/Spotlight/thunderbird.mdimporter> (bundle, loaded)

9/15/15 7:46:26.435 PM mdworker[718]: (Import.Error:722) Could not create instance for plugIn 'file:///Applications/Thunderbird.app/Contents/Library/Spotlight/thunderbird.mdimporter/'

9/15/15 7:46:26.435 PM mdworker[718]: (Import.Error:878) BAD IMPORTER ~~~~~~~~~~~~~~~~~~ file:///Applications/Thunderbird.app/Contents/Library/Spotlight/thunderbird.mdimporter/

9/15/15 7:47:25.635 PM Safari[512]: tcp_connection_tls_session_error_callback_imp 44 __tcp_connection_tls_session_callback_write_block_invoke.434 error 22

9/15/15 7:50:46.000 PM syslogd[47]: ASL Sender Statistics

9/15/15 7:53:05.491 PM WindowServer[205]: handle_will_sleep_auth_and_shield_windows: Deferring.

9/15/15 7:53:05.494 PM WindowServer[205]: CGXDisplayDidWakeNotification [9886760897736]: posting kCGSDisplayDidWake

9/15/15 7:53:05.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

9/15/15 7:53:06.000 PM kernel[0]: IOThunderboltSwitch<0>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 1

9/15/15 7:53:11.087 PM watchdogd[312]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

9/15/15 7:53:22.319 PM spindump[618]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-09-15-195322_MacBook-Pro.userspace_watchdog_timeout.spin

9/15/15 7:53:22.320 PM watchdogd[312]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-09-15-195322_MacBook-Pro.userspace_watchdog_timeout.spin)

9/15/15 7:53:36.177 PM watchdogd[312]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive

9/15/15 7:53:38.752 PM spindump[618]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-09-15-195338_MacBook-Pro.userspace_watchdog_timeout.spin

9/15/15 7:53:38.753 PM watchdogd[312]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-09-15-195338_MacBook-Pro.userspace_watchdog_timeout.spin)

9/15/15 7:54:31.000 PM bootlog[0]: BOOT_TIME 1442364871 0

9/15/15 7:54:32.000 PM syslogd[46]: Configuration Notice:

ASL Module "com.apple.AccountPolicyHelper" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

9/15/15 7:54:32.000 PM syslogd[46]: Configuration Notice:

ASL Module "com.apple.Accounts" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

9/15/15 7:54:32.000 PM syslogd[46]: Configuration Notice:

ASL Module "com.apple.Accounts" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

And here's an example of when it /did/ wake up at 9:12:28:

9/15/15 9:06:14.076 PM launchservicesd[88]: SecTaskLoadEntitlements failed error=22

9/15/15 9:06:14.078 PM launchservicesd[88]: SecTaskLoadEntitlements failed error=22

9/15/15 9:06:14.099 PM appleeventsd[57]: SecTaskLoadEntitlements failed error=22

9/15/15 9:06:14.108 PM SIMBL Enabler for Sandboxed Apps[627]: Set up watching for containers directory at URL file://localhost/Users/kvatz/Library/Containers/

9/15/15 9:06:29.119 PM SIMBL Enabler for Sandboxed Apps[627]: Will terminate until reinvoked again by launchd.

9/15/15 9:12:28.332 PM WindowServer[203]: CGXDisplayDidWakeNotification [4679288860324]: posting kCGSDisplayDidWake

9/15/15 9:12:28.332 PM WindowServer[203]: handle_will_sleep_auth_and_shield_windows: Deferring.

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

9/15/15 9:12:29.032 PM WindowServer[203]: Received display connect changed for display 0x3f003e

9/15/15 9:12:29.034 PM WindowServer[203]: Found 27 modes for display 0x003f003e [27, 0]

9/15/15 9:12:29.034 PM WindowServer[203]: Display 0x003f003e changed state to online

9/15/15 9:12:29.038 PM WindowServer[203]: Received display connect changed for display 0x3f003f

9/15/15 9:12:29.038 PM WindowServer[203]: Found 1 modes for display 0x003f003f [1, 0]

9/15/15 9:12:29.038 PM WindowServer[203]: Received display connect changed for display 0x2b281ad0

9/15/15 9:12:29.038 PM WindowServer[203]: Found 1 modes for display 0x2b281ad0 [1, 0]

9/15/15 9:12:29.038 PM WindowServer[203]: Display 0x2b281ad0 changed state to offline

9/15/15 9:12:29.042 PM WindowServer[203]: Received display connect changed for display 0x3f0041

9/15/15 9:12:29.042 PM WindowServer[203]: Found 1 modes for display 0x003f0041 [1, 0]

9/15/15 9:12:29.044 PM com.apple.AmbientDisplayAgent[256]: CGSServiceForDisplayNumber: Invalid display 0x04280642

9/15/15 9:12:29.052 PM Flux[479]: Set a breakpoint at CGSLogError to catch errors as they are logged.

9/15/15 9:12:29.052 PM Flux[479]: CGSGetSizeOfDisplayTransfer: Invalid display 0x2b281ad0

9/15/15 9:12:29.053 PM WindowServer[203]: Display 0x04280642: GL mask 0x5; bounds (1920, 0)[1440 x 900], 27 modes available

Main, Active, on-line, enabled, built-in, boot, Vendor 610, Model a019, S/N 0, Unit 2, Rotation 0

UUID 0xf466f621b5fa04a00800cfa6c258decd, ColorSpace { -206507792 }

Hi Ken,

As with GellieG, there were no log entries corresponding to the time of the failed wake - only some detailing the handling of the WindowServer crash ~150 seconds later, so there's not much to go on there.

More interesting is the log you posted of when it did wake. That shows the rapid flicking between integrated and discrete GPUs that have been noted elsewhere on this build (El Capitan GM). It's a bug that can be worked around by un-ticking the "Automatic Graphics Switching" option in the Energy Saver SysPref pane.

Towards getting this fixed, it would be good if you could file a bug report: http://bugreport.apple.com.

Max

Max, thanks very much. I'll file the bug report as suggested and change the setting.

One other observation--this failure to awaken only occurs when the rMBP (15" mid 2014) is left sitting for a couple hours or so /without/ putting it to sleep, and all the automatic sleep functions are off. The MBP has the lid closed with a 4K Dell monitor attached via TB and a mini DP cable. (No, opening the lid doesn't help). If I actually put the computer to sleep, say, overnight, it awakens normally. Does that tell you anything?

Any ideas at to how to troubleshoot this further?

Ken

I'm not clear about the first sentence of the observation you make. You say that all automatic sleep options are off and yet I infer from the contrast you make in the third sentence that you don't manually put it to sleep either - so of course I'm wondering what triggered the sleep that it fails to awake from.

Anyway though, I'm now pretty sure that this is related to a wider graphics switching bug that I'm glad you've contributed to the fixing of by submitting your report. As for troubleshooting this further, you could try to reproduce the behaviour without the monitor connected. If it only occurs with the monitor connected then you could also try a different connection config, or a different monitor if you have one...

Max,

Sorry about the ambiguity. I was saying that I wasn't actively putting the MBP to sleep, rather, just letting it sit unattended, and it seemed as if it had gone to sleep by itself, despite my settings in Preferences.

Here are the settings: I had checked the following: "Prevent computer from sleeping automatically when display is off," Wake for Wi-FI access," and "Enable Power Nap while plugged into a power adapter." And I now have unchecked "Automatic graphics setting," as per your suggestion, but haven't yet had the chance to test it, because I left the computer in safe mode today while I was at work, to see if it would fail to turn on. And, by the way, there were no problems today waking up from whatever state it was in when it was in Safe Mode.

So, if I experience the difficulty in getting the computer to turn on even with the automatic graphics setting turned off, I'll then disconnect the external monitor and see what happens.

I suggest you un-check "Enable Power Nap while plugged into a power adapter" too, as a power nap may well be the state that it fails to wake from.

Thanks, Max. I've just unchecked the Power Nap box.

Overnight, even with that box checked, I had let the MBP sit without actively going to sleep, with the 4k external monitor plugged in. The computer came out of this state normally this morning--no problem. Maybe it was the automatic graphics switching that had been causing the problem.

I'll continue to watch it and report back.

Ken

Yes, I too think that the graphics switching is the underlying bug. From what you've reported so far it's only triggered from Power Nap when Graphics Switching is enabled.

Initial results seem to show that only disabling Graphics Switching is sufficient, and it may also be the case that only disabling Power Nap is sufficient.

@GellieG - I suggest you open System Preferences, then "Energy Saver" and un-tick the "Automatic graphics switching" option.

Max,

We (you, that is,) may have solved a major problem with El Capitan!

I'm just a guest here on this Developer Forum--glad I found it. I am surely not a developer--really just a basic end user. I assume from your Level 7 that you are into the nitty gritty of the OS, but I always wonder why Apple itself doesn't seem to solve these issues when they are reported.

There's another ongoing issue that spans several OS versions, and that is the "Disk not ejected properly" error message, pertaining mostly to external TB or USB HDs, and it even has a few threads in the Apple Forums devoted to it. It's been years, now, and people submit logs and everything, but no one seems to be able to figure it out. It, too, seems to be some sort of power handling issue. I have it with one USB 3.0 WD HD. Again, how is it that Apple can't or won't take possession of this and solve the problem, or at least explain it?

Ken

Frustration at what can seem like the "black hole" of Apple bug submission is not uncommon - particularly among developers in cases where the bug they report is marked as a duplicate, resulting in them not receiving any further information on an issue that may be critical to the funtionality of their app.

As for the specific issue you mention, I'm not as familiar with it as you perhaps are. If it's a matter of external drives spontaneously disconnecting, triggering the "Disk not ejected properly" notification, then this is likely due to the threshold at which the current drawn by a peripheral is deemed dangerous and a safety shutdown of the bus is triggered.

Apple have to find a balance here - if the threshold is too high, there is the risk of component damage in the event a short circuit somehow occurs in the peripheral. Too low, and a high-draw peripheral under heavy load may register as a false positive and trigger the safety shutdown when it shouldn't.

Part of the responsibility therefore lies with the designers of the peripherals - if they don't ensure operation is regulated within tight parameters then that device could, under heavy load, cause the bus of a sensitive computer to shut down. This may be the case with your 3.0 WD HD and Mac.

Part of the responsibility also lies with Apple to get the threshold "right" and one could argue that they set it too low. Of course, they might say that they are prioritising the safety and longevity of your Mac's hardware.

Anyway, I may be completely off base in regard to the actual issue you were highlighting, but perhaps the above is at least tangentially relevant...

Best,

Max.

Max,

That's actually the most cogent explanation or hypothesis I've read concerning the DNEP issue. It seems to fit what is going on.

In fact, to my knowledge, no one has even talked about the thresholds, but it makes a whole lot of sense, especially since some HDs seem to be more affected than others. Most of the ideas on these threads had to do with software configuration, preferences, etc., but nothing has ever worked consistently. For me, the DNEP is only a minor annoyance, because it never affects performance the way I use the external drives, mostly for backup, including Time Machine. there has never been data loss or corruption, so far as I know.

If what you postulate is correct about the DNEP problem (and I understand that we don't know if it is or not), why doesn't Apple just come out and say so, rather than keeping everyone wondering? Surely, someone at Apple is aware of the problem, even though claim not to monitor the public forums. No doubt "bug" reports have been submitted, with many duplicates.

Ken

Well I can't speak for Apple, but I'm glad you found the explaination helpful 🙂