Radeon GPU issue in 2017 15" MBP

[truthiness]

I just bought a new 2017 15" MBP in the base config with 16MB RAM/256MB SSD with the Radeon 555 GPU. I set it all up and ran a Cinebench benchmark and was only getting 24fps which baffled me because when I was doing my research I was seeing Cinebench fps performance in the high 70+ range. As it turns out I have since found out that with High Sierra there seems to be an issue that the Radeoon GPU remains in low power mode after the MBP goes to sleep and can only be 'woken up' out of low power mode by doing a hard restart on the machine.

Is there any urgency on Apple's part to get this fixed with a software update? Is this a widespread issue or should I be taking my MBP back and exchanging it within my return period?

Thanks in advance for feedback and guidance!

 

[Honza1]

It happens to me also. I have 2017 MBP with Radeon Pro 560 and after reboot I get ~86fps and after sleep I get ~31fps. So this must be common issue. I did not clock it before, but can verify it now. This is ugly. Report it to Apple! I will also, if they have enough reports, it should be fixed. Assuming they can fix it and it's not hardware issue...

 

[green86]

I can confirm that this is happening as well...

 

[BoomerJay]

Holy ****! this happend to me too! i contacted apple support and i tried everything they told me to do. After i did everything nothing worked. They said it couldnt be the software but a hardware problem. I went to a certified apple repair shop but couldnt afford to lose my macbook 7 working days, so i downgraded back to Sierra and everything is fine. Everything works as it did before High Sierra.

 

[Honza1]

Hm... Stating the obvious, but if it is not in Sierra but is High Sierra, it is NOT hardware problem.

That said, simple sleep during my work time has not provoked this, so it has to be hibernate which causes it.

 

[BoomerJay]

Hm... Stating the obvious, but if it is not in Sierra but is High Sierra, it is NOT hardware problem.

That said, simple sleep during my work time has not provoked this, so it has to be hibernate which causes it.

yes, when it goes in to sleep and you wake it, it happens. Everything lags and doest work proper. They said high sierra would accelerate the gpu performance but only got worse.
[doublepost=1509573418][/doublepost]

Hm... Stating the obvious, but if it is not in Sierra but is High Sierra, it is NOT hardware problem.

That said, simple sleep during my work time has not provoked this, so it has to be hibernate which causes it.

yes, when it goes in to sleep and you wake it it happens. Everything lags and doest work proper. They said high sierra would

 

[tibrowyko]

Also some more cases: https://forums.macrumors.com/thread...ot-work-after-resume-from-long-sleep.2076334/

 

[0837990]

Happens to me with a 2017/i7/560 too. It happened in both 10.13.0 and 10.13.1.
This issue was NOT present in 10.12.6, which I wish I never upgraded from, and currently are considering downgrading to 10.12.6 to fix it.

 

[BoomerJay]

Happens to me with a 2017/i7/560 too. It happened in both 10.13.0 and 10.13.1.
This issue was NOT present in 10.12.6, which I wish I never upgraded from, and currently are considering downgrading to 10.12.6 to fix it.

Only option to fix it is to downgrade back to 10.12.6. Paying 3300 euros for a laptop that doesnt even work proparly frustrates me very much.

 

[0837990]

Only option to fix it is to downgrade back to 10.12.6. Paying 3300 euros for a laptop that doesnt even work proparly frustrates me very much.

Yeah I know. It sucks. Reverting to Sierra isn't straight-forward either, especially with several external HDD's that have been converted to APFS that needs to be reconstructed at HFS+ volumes again... UGH!

I could live with this bug in 10.13.0 but I assumed it would be fixed for 10.13.1. It's not even fixed in 10.13.2 beta, which means it'll probably take 3-6 months more at least before a non-beta release that contains a fix for it is available, which is just not acceptable.

I use the 560 GPU to do video rendering with FCPX all the time, as well as play some games, and use Capture One Pro with DGPU accelleration also. I can notice the 70% performance hit very easily all the time... And rebooting the computer every time I'm gonna use it is unacceptable!!!
[doublepost=1509622006][/doublepost]I encourage everyone that's experiencing this issue to report it to Apple at their macOS feedback page: [URL]https://www.apple.com/feedback/macos.html[/URL]

 

[green86]

Yeah I know. It sucks. Reverting to Sierra isn't straight-forward either, especially with several external HDD's that have been converted to APFS that needs to be reconstructed at HFS+ volumes again... UGH!

I could live with this bug in 10.13.0 but I assumed it would be fixed for 10.13.1. It's not even fixed in 10.13.2 beta, which means it'll probably take 3-6 months more at least before a non-beta release that contains a fix for it is available, which is just not acceptable.

I use the 560 GPU to do video rendering with FCPX all the time, as well as play some games, and use Capture One Pro with DGPU accelleration also. I can notice the 70% performance hit very easily all the time... And rebooting the computer every time I'm gonna use it is unacceptable!!!
[doublepost=1509622006][/doublepost]I encourage everyone that's experiencing this issue to report it to Apple at their macOS feedback page: https://www.apple.com/feedback/macos.html

Just submitted feedback. Thank you.

 

[Fishrrman]

0837990 wrote:
"Reverting to Sierra isn't straight-forward either, especially with several external HDD's that have been converted to APFS that needs to be reconstructed at HFS+ volumes again... UGH!"

Perhaps it's just me, but I fail to understand why so many took a blind leap to APFS, which at this point in Apple history remains "untested technology".

I'm sticking with HFS+ and have no plans to move beyond it, for at least two or three years yet...

 

[green86]

0837990 wrote:
"Reverting to Sierra isn't straight-forward either, especially with several external HDD's that have been converted to APFS that needs to be reconstructed at HFS+ volumes again... UGH!"

Perhaps it's just me, but I fail to understand why so many took a blind leap to APFS, which at this point in Apple history remains "untested technology".

I'm sticking with HFS+ and have no plans to move beyond it, for at least two or three years yet...

It wasn't untested. Months of Beta. And all iOS devices had it since 10.3, a transition that went smoothly. Of course using the file system on a Mac is different, but like I said, there was months of beta there. It wasn't untested, but it wasn't 30+ years old either. I remember reformatting my Power Mac 6500/275 in HFS in 1996... it is insanity that the file system really hasn't changed much since then. I say good riddance. Also... this problem has nothing to do APFS, so I'm not sure why your pointing out your shock.

 

[0837990]

0837990 wrote:
"Reverting to Sierra isn't straight-forward either, especially with several external HDD's that have been converted to APFS that needs to be reconstructed at HFS+ volumes again... UGH!"

Perhaps it's just me, but I fail to understand why so many took a blind leap to APFS, which at this point in Apple history remains "untested technology".

I'm sticking with HFS+ and have no plans to move beyond it, for at least two or three years yet...

I switched to APFS simply because I've never had as many partitions go corrupt has I've had with HFS+ over the years (compared to Ext2, Ext3, ReiserFS, NTFS and even Fat32!). HFS+ has been extremely unreliable, especially when encrypted (which for me is a must). If a HFS+ volume becomes corrupt and it's encrypted there's basically NO WAY to fix it.

 

[nekton1]

Report this to Apple using Feedback Assistant–the more reports the sooner it will be fixed.

 

[Brammy]

Having the same issue on my late 2016 15".

Debated rolling back, but that's more of a hassle than rebooting when I want to play a game.

 

[friednoodles]

For the sake of anyone who might be following this thread or for anyone in the future, at least for late 2016/2017 MBPs with Radeon GPUs, this issue looks like it's now resolved as of 10.13.3 beta 3. See the other thread about it here: https://forums.macrumors.com/thread...ot-work-after-resume-from-long-sleep.2076334/