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

Macbook Pro 16" reboots in every standby

J

Joeinger

macrumors newbie
Original poster
May 9, 2019
27
7
Hi there guys,

I own the new macbook pro 16" since december. After a rough start with problems with touchid and icloud-stuff the book ran flawless for weeks. Since the last update I experience a while with every standby.
The macbook is connected to a 34" display via usb-c which simultanous charches it.

It went to sleep somewhere at 19:00 and did this log entries several times. At 22:03 I opened it and it booted :/

Mar 30 20:54:26 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Mar 30 20:54:45 --- last message repeated 1 time ---
Mar 30 20:54:45 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 30 20:55:03 --- last message repeated 1 time ---
Mar 30 20:55:03 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.CloudDocs.MobileDocumentsFileProvider[916]): Service exited due to SIGKILL | sent by launchd[1]
Mar 30 20:55:06 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 30 20:55:17 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 2 seconds. Pushing respawn out by 8 seconds.
Mar 30 20:55:37 --- last message repeated 1 time ---
Mar 30 20:55:37 Macbook-Pro-Joe com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Mar 30 22:03:07 localhost bootlog[0]: BOOT_TIME 1585598587 568664
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.cdscheduler" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.install" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.callhistory.asl.conf" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.authd" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.eventmonitor" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.mail" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Mar 30 22:03:15 localhost syslogd[109]: Configuration Notice:
ASL Module "com.apple.performance" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.


Any suggestions?
 
10.15.4 finally fixed the problems I was having with the machine. Zero crashes since.

Used to never wake from sleep, every time it connected to my external monitor it would revert to max brightness... Constant issues.
 
Same thing happens when connected to external display; here's a panic dump:

Code: 
panic(cpu 2 caller 0xffffff801f616487): "AppleIntelFramebuffer::setPowerState(0xffffff81ce829000 : 0xffffff7fa2c06d88, 1 -> 0) timed out after 45928 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 2), Frame : Return Address
0xffffff8210e53b40 : 0xffffff801ef215cd
0xffffff8210e53b90 : 0xffffff801f05a3c5
0xffffff8210e53bd0 : 0xffffff801f04bf7e
0xffffff8210e53c20 : 0xffffff801eec7a40
0xffffff8210e53c40 : 0xffffff801ef20c97
0xffffff8210e53d40 : 0xffffff801ef21087
0xffffff8210e53d90 : 0xffffff801f6c2c7c
0xffffff8210e53e00 : 0xffffff801f616487
0xffffff8210e53e50 : 0xffffff801f615d69
0xffffff8210e53e60 : 0xffffff801f62d2fe
0xffffff8210e53ea0 : 0xffffff801f614b18
0xffffff8210e53ec0 : 0xffffff801ef63545
0xffffff8210e53f40 : 0xffffff801ef63071
0xffffff8210e53fa0 : 0xffffff801eec713e

Started happening after 10.15.4 for me too.
 
My 2 day old refurb is doing the same thing. Every time I shut the lid and leave it for a bit when I open it back up it boots and gives me the restart error. Contacted Apple support today and they suggested safe mode... currently leaving it alone to see if safe mode fixes it (which doesn’t seem likely to me..).
 
nrvna76 said:
My 2 day old refurb is doing the same thing. Every time I shut the lid and leave it for a bit when I open it back up it boots and gives me the restart error. Contacted Apple support today and they suggested safe mode... currently leaving it alone to see if safe mode fixes it (which doesn’t seem likely to me..).
Click to expand...
I'm pretty sure only a patch is going to fix this problem.
 
mikethebigo said:
I'm pretty sure only a patch is going to fix this problem.
Click to expand...

So would it be something you’d return over? I guess as long as it’s a software fix I shouldn’t worry too much. I’ve got 12 days to decide. Lol
 
nrvna76 said:
So would it be something you’d return over? I guess as long as it’s a software fix I shouldn’t worry too much. I’ve got 12 days to decide. Lol
Click to expand...
I wouldn't. There are many reports of the same bug on this forum. It really got bad after the last OS update. It's almost certainly a software problem, you'd inherit the same issue if you replaced it with another.
 
  • Like
Reactions: nrvna76
Yea, after safe mode did not help they have me reinstalling macOS. They say if that doesn’t work they suggest a replacement. I asked if there are any more reports of this issue and they didn’t answer that question. lol
 
My wife got a very similar macbook pro 16", just 16gb more ram and the smaller gfx. She has a complete different software set and has absolute the same error :/

Sadly calling the apple-support is absolutely useless, because we all just need to reinstall the whole ****, like every time.
I'm having a master in computer science and working with unix servers all day, but even if you have more knowledge about macos than the hotline-dudes, you get handled like an stupid idiot. The last guy got angry, insulted me and hang up, wow. This is the support which I'm expecting after buying a machine about 4000 bucks...

So lets hope that this gets fixed in the next patch. Otherwise I will exchange the machine every half a year. Lets see how long this takes...
 
What a piece of junk. Having this BridgeOS and adding more modules to the T2 was probably a step that went to far and for last 2 years people are seeing these crashes and sound bugs. They added all this complication to the chip and then just unleashed it on users without giving it a proper long test before releasing it.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back