Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I think here lies the problem with this discussion in that there is no clear message from you as to what the pattern to the 'anomoly' is and people are wrongly assuming GB5 reporting errors is a sign of logic board failures. Or at least that is how I read your reply I've quoted above.

Simply getting hardware errors and restart error messages in console is not an indication of people having your original issue and needing a new logic board. Currently with the 16" MBP and OS 10.15.3 when running GB5's metal compute test on the Intel 630 GPU, console reports these errors on all machines and is probably down to software/drivers.

As I think (?) I understand it, your original 'anomoly' was computer crashes and restarts and it was found GB5's metal test could replicate conditions to encourage this behaviour forcing a crash and total system restart. Upon restart, crash log's reported GPU panic's and Apple advised you had a faulty logic Board.

So.......

  • GB5 Metal test of Intel GPU - Console reoporting hardware errors, restarts, time outs etc is normal (if normal means not working very well).
  • GB5 Metal test on intel GPU - Computer crashes, restarts and crash log reports show 'Panic' errors then you possibly have an issue.
Does this sound correct?

First, I have to agree to disagree with you about me not being clear. Please see my responses in #1, #6, #46, #55, and #119. They are very consistent and pretty clear from my perspective.

As for correct... your first bullet point is correct. Second one needs altering. If you GPU panic with GB5 Metal test on intel GPU and "Powerplay failed to resume" or "Powerplay failed to initialize", and its consistent, then you DO have the issue, not maybe.
 
First, I have to agree to disagree with you about me not being clear. Please see my responses in #1, #6, #46, #55, and #119. They are very consistent and pretty clear from my perspective.

As for correct... your first bullet point is correct. Second one needs altering. If you GPU panic with GB5 Metal test on intel GPU and "Powerplay failed to resume" or "Powerplay failed to initialize", and its consistent, then you DO have the issue, not maybe.
I’m on your side but just don’t think you’re explaining it very well with constant referencing to GB5 which I personally think is a red herring. If we fully understood you we wouldn’t be getting our knickers in a twist over GB5 console errors.

My post above is not an attack but hopefully a reference to newcomers as to when they actually need to worry about logic board replacements and pay less attention to GB5 results.
 
I’m on your side but just don’t think you’re explaining it very well with constant referencing to GB5 which I personally think is a red herring. If we fully understood you we wouldn’t be getting our knickers in a twist over GB5 console errors.

My post above is not an attack but hopefully a reference to newcomers as to when they actually need to worry about logic board replacements and pay less attention to GB5 results.

Not taken as an attack. I just wanted to say I have been clear on it. :)

Geekbench was just a way to reproduce that panic faithfully. No more. As to why it reproduces it I have no idea. But it works as a way to determine if you have the bug.
 
Thank you for your reply.
Does this mean that it is not a hardware issue?

That I can't say. Its certainly not the same panic message I had. But if it becomes a regular issue and happens often, then you definitely have cause for alarm and probably should go to Apple. But if it happens rarely, its likely software and will hopefully be fixed in future releases. Catalina was a train wreck and Apple is bug patching it like crazy.
 
@StolenPhone:
This has nothing to do with the panic report: how is the sound on your MBP 16"? Mine sounds just like the 13" I had before this. Flat, with hardly any bass. Nowhere near Apple's description of room filling sound. You can tell it bothers me after paying so much money and having all this happen.
 
Is there a terminal command that can search the logs for the "PowerPlay Failed" string? Also, where in Console can I find the a log that I send to Apple when the crash dialog reporter comes up?
 
@StolenPhone:
This has nothing to do with the panic report: how is the sound on your MBP 16"? Mine sounds just like the 13" I had before this. Flat, with hardly any bass. Nowhere near Apple's description of room filling sound. You can tell it bothers me after paying so much money and having all this happen.

Mine sounds good. Better than any laptop I have owned. Sounds like an Alexa v3 Echo.
[automerge]1583856490[/automerge]
Is there a terminal command that can search the logs for the "PowerPlay Failed" string? Also, where in Console can I find the a log that I send to Apple when the crash dialog reporter comes up?

There is, but I would follow my instructions earlier. If its not in Console, then you don't have one.

Either way, here is the terminal string:

Code:
sudo grep macOSPanicString /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge/* | grep -i "PowerPlay Failed"
 
Last edited:
I got only 2185 points for the iGPU GB5 Metal benchmark.
Does it mean I have faulty hardware? Can someone else post their scores here? Specially the ones who got a replacement already.
 
There is, but I would follow my instructions earlier. If its not in Console, then you don't have one.

Either way, here is the terminal string:

Code:
sudo grep macOSPanicString /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge/* | grep -i "PowerPlay Failed"

Well there are literally hundreds of error logs in the Console, so I'm not going to sit there and try and find it, thanks.
 
Guess I'm ok, but I have an early January build so hopefully they figured it out by then.

I've not had any regular or repeated serious panics.
 
Well there are literally hundreds of error logs in the Console, so I'm not going to sit there and try and find it, thanks.

You were not only given the grep commandline command as requested, but you may want to spend 2 minutes learning how to use the Console app as its probably even faster than using the command line grep:

 
Yes, but nothing has changed
Thanks for the update. Even though I’ve not been effected it would be nice if they addressed the GPU power consumption issues with external displays and this GPU switching bug causing hangs with the Intel GPU.

Seems like we’ll have to wait for 10.15.5 betas. :(
 
I hadn't used GB5 much as my workflow was enough to trigger it. Still waiting for my proper replacement to arrive now. I've been told by apple it will be from the 2020 batch so will check that.

My workflow as a web developer is coding in text editor, issuing commands to terminal to run localhost servers, run VirtualBox VMs of emulated devices to do cross browser testing, open creative software like Adobe for image editing and Final Cut Pro X/Resolve for editing video. This all gets done at once with all these apps open at the same time (except when rendering video) so I can get it all put together quite quickly.

On my dual-core 8gb ram entry model mbp 2016 13" no touch bar (10.15.4), the above is all smooth and yes I can run it all at the same time, no freezes, no restarts, walking to and from the machine as needed. No crashes during sleep. Months without a restart, and then it's me that did it anyway cause it needs a break.

I noticed the apps aren't as quick to open and switch between anymore, and wanted to not have to go to my desktop for heavier effects rendering when on the move.

So that's where my upgrade to the macbook pro 2019 16" came in to play.

The above mentioned workflow on that machine isn't possible. VMs freeze it, creative software freezes it, large text files opened in an array of text editors freezes it. Making apps in Unity freezes it. Even Xcode occasionally. To go from a machine that in comparison is extremely underpowered to this new one, but to face constant freezes almost hourly, and be crossing my fingers that I'm not about to lose 40mins of work with the next app open (and having to go back to all open apps before that and hit save just in case adds SO much more time)...is crazy.

When that's the behaviour of the new machine ON SALE then maybe that sale date should have been pushed back.

One behaviour I did spot on my original machine with 4 logicboard replacements was sometimes if it froze I could close the lid and open again to escape the freeze, except after doing that the machine appeared to be stuck using the amd gpu even with everything closed and it left to 'settle' a bit. I would have to manually make it switch back to integrated. With no freeze, it would switch back and forth until it froze.

Oh and the speaker popping issue with 10.15.1? The pop was very loud, but so were my speakers. Filled the room with bass, like a mini sound system. 10.15.2 onwards, speaker pop is supposedly gone. But put your ear right next to the speaker in the middle of the night and you can hear the 'pop' very faintly when starting/stopping apps playing audio or switching between them...and that room filling bass? Gone. So what's the bet the speakers have had less power routed to them to 'allievate a bad design issue'.

Another issue - macOS that is supposed to be 'one of the most secure' has bypassed Windows 10 for most amount of zero day exploits since Catalina's release. The things you make viruses & malware with. You can probably blame your low GB5 intel CPU score on this particular exploit. Up to a 20% loss in CPU performance for 9th gen and below since it has to be applied at the OS level, only 10th gen onward have a hardware fix for this.

Unsure why everyone keeps toting that each new OS version is going to fix this mess. People have been saying that since 10.15.1 and every 10.15.x has been the exact same clusterphuck as the first revision the machine shipped with.

Keep in mind this machine was released November 2019 and we're now approaching April 2020. Once that new 2020 macbook with mini-LED screen is released you can bet this issue will be swept under the rug. Just ask 2018 15" mbp owners who like to plug usb-c devices in their machines. Due to the certain configuration of hardware and particular T2 chip revision used in those machines, those users have had the 'bad magic' bug a lot worse than other machines. For two years now.

And no:
Screen Shot 2020-03-19 at 12.19.23 am.png


This is not fine. Don't tell me to disable the gpu, or turn this off, or uninstall that. Tell apple to fix their **** up.
 
Last edited:
  • Like
Reactions: gazwas
Just had my first.
Came back to a login screen after some hours in idle. Typed in password and then it restarted with fans going full for a few seconds. Is this hardware issue also?


panic(cpu 0 caller 0xfffffff00f054350): PUP PANIC - deserialize: saved state does not match current state. serialization cursor 0x2ca2c - pup-workloop(1)


deserialize: saved state does not match current state. serialization cursor 0x2ca2c
 
Just had my first.
Came back to a login screen after some hours in idle. Typed in password and then it restarted with fans going full for a few seconds. Is this hardware issue also?


panic(cpu 0 caller 0xfffffff00f054350): PUP PANIC - deserialize: saved state does not match current state. serialization cursor 0x2ca2c - pup-workloop(1)


deserialize: saved state does not match current state. serialization cursor 0x2ca2c


:rolleyes: are you using Bootcamp with a paid version of Windows?

This also released the day apple received my faulty macbook, hopefully they have time to get the replacement back to me now with all the closures:
Untitled-1 copy.png
 
:rolleyes: are you using Bootcamp with a paid version of Windows?

This also released the day apple received my faulty macbook, hopefully they have time to get the replacement back to me now with all the closures:
View attachment 900416
No I had it running windows, the free version with an external monitor hooked up. Is there a difference between paid and free except for not being able to change the background/theme?
 
  • Haha
Reactions: insited
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.