Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2017 MBP 15 - Radeon GPU does not work after resume from long sleep
- Thread starter jeh72
- Start date
- Sort by reaction score
This is very annoying and has been driving me crazy as well. I've had nothing but problems with these new TB models... I'm about to return this one, yet again, and just continue to use my late 14 model. My first model of the TB had this annoying click keyboard, and the second one had the same issue.. now this is my third one and the GPU doesn't even work as intended.
Just a little update: it hasn't done it yet in 10.13.3 beta 3, but it's only been two days and I did have to restart yesterday. With beta 2, it took a couple of days after installation to start doing it again, so I'm not convinced yet. I'll keep you posted.
Make sure you start Unigine Heaven or some other high gpu power app briefly and then close it before putting the computer to sleep...it may be just me but it seems like taxing the GPU in the computing session before a long sleep triggers it more easily.
So far no issue! But I’ve had to shut down again because I’m in transit between countries so I’ll report back again in another day...
It’s looking promising, but the last time I said that it started doing it again, so for now I’ll cross my fingers and hope!
I don't have the 2017 model but have you guys tried gfxCardStatus? It's an app that allows manual or dynamic (auto) switching between the integrated and discrete GPU?
You can find it here. https://gfx.io/
You can find it here. https://gfx.io/
It's not an issue with apps stuck running on the intel gpu; it's a problem with the radeon gpu being stuck in lower power states (and performing like an intel gpu).
And now beta 4 is available so here's hoping it doesn't break what appears to be working in beta 3. Downloading now and will report back again.
Well, it's still normal after last night's sleep. Maybe, just maybe... it's fixed?
Did the graphics driver number change compared to the previous betas or the last released version?
Thanks for you efforts @friednoodles !
Thanks for you efforts @friednoodles !
I'm not sure where to see the video driver version (System Information shows things like VBIOS and EFI firmware versions, which aren't what we're after as far as I know), but looking in Photoshop's System Info dump shows these lines, which seem to indicate when the GPU drivers (or at least the parts relevant to compute acceleration) were updated:
clgpu[1].CLDriverVersion="1.2 (Jan 3 2018 16:19:12)"
clgpu[0].CLDriverVersion="1.2(Dec 19 2017 22:07:15)"
clgpu[1] is the AMD GPU, while clgpu[0] is the Intel GPU. So it looks like the AMD driver, or at least part of it, was last updated on January 3, while the Intel driver was last updated December 19.
Overnight it was plugged in for sleep and today it was on battery for sleep for a couple of hours, and so far everything's still normal. Fingers crossed!
clgpu[1].CLDriverVersion="1.2 (Jan 3 2018 16:19:12)"
clgpu[0].CLDriverVersion="1.2(Dec 19 2017 22:07:15)"
clgpu[1] is the AMD GPU, while clgpu[0] is the Intel GPU. So it looks like the AMD driver, or at least part of it, was last updated on January 3, while the Intel driver was last updated December 19.
Overnight it was plugged in for sleep and today it was on battery for sleep for a couple of hours, and so far everything's still normal. Fingers crossed!
10.12.6 also lists 01.00.927 as the EFI firmware version, so I don't think that's relevant for the driver version.
You should check under:
About this Mac > System Report > Software > Extensions > AMDSupport
On 10.12.6 this extension has version number 1.51.8
On 10.13.3 beta 4 the version number for AMDSupport is 1.60.26 and was last updated on 25.08.17 as well.
However, looking in this same area there are a number of things that show as updated when I installed the latest beta, including things like AppleGraphicsDeviceControl, version 3.16.21, and IOGraphicsFamily, version 517.22, though I have no idea whether these are relevant.
Last edited:
Still working fine after another night's sleep
Sounds good for the final 10.13.3 release. If everything works well in the final release I might just upgrade from 10.12.6 to 10.13.3
So it only took them 4ish months to fix a critical performance bug on their flagship machine...
I'm guessing it was a side-effect of adding external GPU support over TB3. The OS needs to account for eGPUs being added/removed from the system now. It was complex enough for Craig F to mention its difficulty during the WWDC keynote last Summer.
For the 2015 MBP 15" the discrete AMD GPU issue seems to be fixed with the latest betas. However I'm now seeing the issue with the Integrated Intel GPU after using the AMD GPU and sleeping. I see general UI slowdowns and especially issues with Safari on certain webpages. It becomes unusable. The complete bug report I've just sent:
Sometimes when coming out of sleep the graphics system WHEN USING THE INTEGRATED INTEL IRIS PRO seems to be in some sort of slow state that cuts the performance of Safari in particular, but also animations of the UI in general. It seems to happen when running a graphics intensive app that engages the discrete graphics chip (AMD Radeon R9 M370X), then quit it, then sleep. Coming out of sleep after a while when you go to http://www.icloud.com with the floating bubbles, everything is slow. It takes multiple seconds to drop down the File or Edit menu in Safari.
Steps: (Doesn’t happen all the time, but fairly frequently)
1. Run a graphics intensive application to engage the discreet AMD GPU.
2. Quit the graphics intensive application to engage the integrated INTEL GPU.
3. Put the computer to sleep
4. Wait for an hour or two
5. Wake the computer
6. Go to www.icloud.com
7. Notice the bubbles move very slowly, only a couple frames a second.
8. Notice when trying to open the File or Edit menu it takes a couple seconds for them to open.
9. Notice moving between menu items in the File or Edit menu it takes a long time for the highlight to catch up with the mouse point.
Results Expected
Safari should be as fast and responsive as it is after a reboot when running the integrated Intel GPU.
Actual Results
Safari is slow/choppy. Other system UI elements are slow
I previously reported the discrete AMD GPU was slow when coming out of sleep. That issue may have been fixed as I’m not seeing it anymore, but now the integrated Intel GPU is slowing down after sleep. Sierra didn’t have this problem.
Sometimes when coming out of sleep the graphics system WHEN USING THE INTEGRATED INTEL IRIS PRO seems to be in some sort of slow state that cuts the performance of Safari in particular, but also animations of the UI in general. It seems to happen when running a graphics intensive app that engages the discrete graphics chip (AMD Radeon R9 M370X), then quit it, then sleep. Coming out of sleep after a while when you go to http://www.icloud.com with the floating bubbles, everything is slow. It takes multiple seconds to drop down the File or Edit menu in Safari.
Steps: (Doesn’t happen all the time, but fairly frequently)
1. Run a graphics intensive application to engage the discreet AMD GPU.
2. Quit the graphics intensive application to engage the integrated INTEL GPU.
3. Put the computer to sleep
4. Wait for an hour or two
5. Wake the computer
6. Go to www.icloud.com
7. Notice the bubbles move very slowly, only a couple frames a second.
8. Notice when trying to open the File or Edit menu it takes a couple seconds for them to open.
9. Notice moving between menu items in the File or Edit menu it takes a long time for the highlight to catch up with the mouse point.
Results Expected
Safari should be as fast and responsive as it is after a reboot when running the integrated Intel GPU.
Actual Results
Safari is slow/choppy. Other system UI elements are slow
I previously reported the discrete AMD GPU was slow when coming out of sleep. That issue may have been fixed as I’m not seeing it anymore, but now the integrated Intel GPU is slowing down after sleep. Sierra didn’t have this problem.