Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MBHockey

macrumors 601
Original poster
Oct 4, 2003
4,063
314
Connecticut
Hi all,

Having a really annoying problem with El Capitan and my 2015 15" MBP (dGPU). 100% of the time, if i take my MBP in sleep mode (clamshell) and plug it into the charging cable and external monitor, and then attempt to wake the MBP by the using the external keyboard/mouse the entire system freezes and I have to hard reboot it. Sometimes i'll get this strange artifactual log in screen that I cannot type anything into, sometimes it's just a blank screen, and sometimes I'll get a windows login screen with an indefinite beach ball.

I recently turned on FileVault for my SSD along with having users log in when I wake from sleep, so maybe this has something to do with it. I see a lot of error messages relating to WindowServer in Console around the time it happens.

Is anyone else having this issue?

I'm using the older Aluminum Apple Cinema Display (30") connected via thunderbolt adaptor.

I have no problem sleep/waking it if the MBP is already connected to the monitor when I sleep and then wake it. It's only an issue when attempting to wake the computer after I plug it in to the external monitor.
 
Hi all,

Having a really annoying problem with El Capitan and my 2015 15" MBP (dGPU). 100% of the time, if i take my MBP in sleep mode (clamshell) and plug it into the charging cable and external monitor, and then attempt to wake the MBP by the using the external keyboard/mouse the entire system freezes and I have to hard reboot it. Sometimes i'll get this strange artifactual log in screen that I cannot type anything into, sometimes it's just a blank screen, and sometimes I'll get a windows login screen with an indefinite beach ball.

I recently turned on FileVault for my SSD along with having users log in when I wake from sleep, so maybe this has something to do with it. I see a lot of error messages relating to WindowServer in Console around the time it happens.

Is anyone else having this issue?

I'm using the older Aluminum Apple Cinema Display (30") connected via thunderbolt adaptor.

I have no problem sleep/waking it if the MBP is already connected to the monitor when I sleep and then wake it. It's only an issue when attempting to wake the computer after I plug it in to the external monitor.

I am not surprised that you have problems from sleep when you change the configuration during sleep. For what its worth, I NEVER sleep my MBP.
 
Hi all,

Having a really annoying problem with El Capitan and my 2015 15" MBP (dGPU). 100% of the time, if i take my MBP in sleep mode (clamshell) and plug it into the charging cable and external monitor, and then attempt to wake the MBP by the using the external keyboard/mouse the entire system freezes and I have to hard reboot it. Sometimes i'll get this strange artifactual log in screen that I cannot type anything into, sometimes it's just a blank screen, and sometimes I'll get a windows login screen with an indefinite beach ball.

I recently turned on FileVault for my SSD along with having users log in when I wake from sleep, so maybe this has something to do with it. I see a lot of error messages relating to WindowServer in Console around the time it happens.

Is anyone else having this issue?

I'm using the older Aluminum Apple Cinema Display (30") connected via thunderbolt adaptor.

I have no problem sleep/waking it if the MBP is already connected to the monitor when I sleep and then wake it. It's only an issue when attempting to wake the computer after I plug it in to the external monitor.

This seems to be an issue with el capitan hopefully the next update will sort it out, report it to apple so they know to look into it.
 
I had a few similar issues during the betas (hanging when coming out of sleep), but I've not had an issue since the final release
 
I did a little more digging. Looks like my system.log is filled with these entries at the time of the hangup:

Code:
10/21/15 7:27:47.458 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.463 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.467 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.472 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.476 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.481 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.486 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.490 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.495 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.500 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.504 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.510 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.515 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.520 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.525 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.530 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.535 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.540 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.545 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.550 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.555 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.559 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.565 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.569 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.574 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.579 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.584 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.589 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.594 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.599 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.604 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.610 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.615 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.620 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.625 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.629 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)
10/21/15 7:27:47.634 PM WindowServer[196]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness)

Looks like WindowServer is hanging. Googling around shows that this issue has been popping up on several different machines since 2012 all the way up to the most recent 12" macbooks and newest Mac Pro. Not very encouraging.
 
Ever find a solution to this. I bought a new mid-2015 15" rMBP and have the same issue. It's VERY frustrating because I have to take the macbook out of my vertical dock and power cycle it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.