Bad news...problem reappeared today when I decided to check Unigine Heaven before leaving work. It took longer to appear but it looks like the issue is still there 
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
I've ben having a similar issue. The dGPU turns on but feels throttled after a long sleep. Restarting fixes the issue. For me, performance is normal but extremely choppy. So I will get 60 fps in a game but there is a noticeable stutter. I thought it was related to the CPU not fully waking? Almost like its multicore bottle necked...
I don't think it's the CPU. I first noticed there was a problem while running Cinebench GPU test.
There's a thread about it in the Apple support forums: https://discussions.apple.com/message/32549936?ac_cid=tw123456#32549936
Well at least we're not the only ones. Hard to imagine how such a widespread issue hasn't been fixed yet considering the problems it creates.
I've now installed 10.13.2 beta 2 and, as with jeh72, I'm still experiencing the issue. It's exactly the same for me in terms of timing, etc.
I've now installed 10.13.2 beta 2 and, as with jeh72, I'm still experiencing the issue. It's exactly the same for me in terms of timing, etc.
I'll save you the trouble of checking: the bug's still there in 10.13.2 beta 3.
No, it doesn't. I suspect this issue isn't getting fixed any time soon, which is very frustrating. Maybe they're too busy working on driver support for the upcoming iMac Pros and have all but forgotten about us MacBook Pro users... (although it's probably just that there are so many core bugs in High Sierra that need fixing that it's just taking a long time to get to this one, which is likely in the graphics driver and therefore probably something that AMD has to help them with)
Very. Annoying.
Very. Annoying.
[doublepost=1511899987][/doublepost]- Do users with intel GPUs see this problem? (Iris Pro, Iris Plus, HD 6000, HD 615, etc). YES
I'm on it right now, and happy to try (this is the first I've seen this thread). But is it really necessary to wait an hour in order to reproduce?
Sometimes it takes a half hour, sometimes several hours. I’m going to try it too.
I have the same issue on a 2015 MBP 15" with a AMD Radeon R9 M370X. I've had both the Intel Iris Pro and AMD Radeon go into this low power, 25% speed state coming out of sleep. I've been running the beta's and haven't seen a fix yet.
What I am having luck with is turning off Automatic graphics switching in Energy Saver. Seems if I'm always using the Radeon it maintains high speed/power. Is turning off Automatic graphics switching an option in the 2017's?
Of course this doesn't help battery life.
What I am having luck with is turning off Automatic graphics switching in Energy Saver. Seems if I'm always using the Radeon it maintains high speed/power. Is turning off Automatic graphics switching an option in the 2017's?
Of course this doesn't help battery life.
It is still an option on 2017's, but as you said it is not convenient if you use your laptop away from the charger often.
I didn't know that this issue affected non-Polaris GPU's. That's interesting. I wonder why Apple didn't catch this in QA testing if it is so widespread?
Not fixed on 2016 MBP either. I'll be interested to see if the graphics driver version changes at all in upcoming betas/releases... (it hasn't recently)
As suspected, still not fixed in the 10.13.2 release on the 2015 MBP 15". I now have resorted to setting up an elaborate combination of sleepwatcher and gfxCardStatusCLI to force the discrete GPU on right before sleep and set it back to automatic switching on wakeup. This actually worked for the entire time I had beta 6 installed.
I'm starting to doubt that Apple knows this bug even exists, or maybe they can't replicate it for some reason. It could also be that the problem lies squarely with software written by AMD, and they are horrible about fixing bugs in a timely manner.