MBP 16" 2019 CRASHES WHILE SLEEPING

If i connect this issue to the kernel_task process that keeps on stealing over 1000% of my cpu cycles without a given reason (even after boot, with no app running and no kext drivers...), i can only say - with sorrow - that this premium hardware (and price) deserves more, a lot more... Hope these issues will be solved in days, not months!

I also have too much work to do to erase everything and start over with no guarantee it will work.

As long as I keep my lid open when connected to an external monitor it does not crash.

I have not noticed it crashing when I am just working on the laptop alone but will find out next week when I am traveling.

Apple, I hope you are reading all these and put out a solution. As noted earlier, I had no problem until probably 6 weeks ago.

Thanks

The crash appears to be in the graphics system. I have the lid closed and it is connected to an external monitor. This is happening every single time the computer sleeps. I'm getting concerned about file corruption.

panic(cpu 2 caller 0xffffff800229167c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2d21.

Backtracing specified thread

Backtrace (CPU 2), Frame : Return Address

0xffffff81fd1f3900 : 0xffffff8001c458f8 

0xffffff92268d3bc0 : 0xffffff8001b413f1 

0xffffff92268d3c30 : 0xffffff8001b3fc2f 

0xffffff92268d3c80 : 0xffffff8001c429f9 

0xffffff92268d3cc0 : 0xffffff8001c4225b 

0xffffff92268d3cf0 : 0xffffff7f857b2ced 

0xffffff92268d3d20 : 0xffffff7f857cbf93 

0xffffff92268d3d30 : 0xffffff7f857b5cb9 

0xffffff92268d3dc0 : 0xffffff7f857c1edc 

0xffffff92268d3e00 : 0xffffff8002214d8a 

0xffffff92268d3ea0 : 0xffffff80022146b4 

0xffffff92268d3ec0 : 0xffffff8001b61565 

0xffffff92268d3f40 : 0xffffff8001b61091 

0xffffff92268d3fa0 : 0xffffff8001ac513e 

      Kernel Extensions in backtrace:

         com.apple.iokit.IOGraphicsFamily(576.1)[B1C0006F-E1F5-37D9-9548-5F918E92B422]@0xffffff7f857aa000->0xffffff7f857fafff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[BE052F4D-9B80-3FCD-B36D-BACB7DEE0DF2]@0xffffff7f82512000

BSD process name corresponding to current thread: kernel_task

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

panic(cpu 0 caller 0xffffff7f9533ecae): "Failed to complete supporting devices Sleep in first sleep/wake(1/0), M8 was avaliable\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedOSSupport/AppleEmbeddedOSSupport-153.60.1/Source/Drivers/AppleEmbeddedOSSupportHost/AppleEmbeddedOSSupportHost.cpp:455

Backtrace (CPU 0), Frame : Return Address

0xffffff8202ffbb70 : 0xffffff80105215cd

0xffffff8202ffbbc0 : 0xffffff801065a3c5

0xffffff8202ffbc00 : 0xffffff801064bf7e

0xffffff8202ffbc50 : 0xffffff80104c7a40

0xffffff8202ffbc70 : 0xffffff8010520c97

0xffffff8202ffbd70 : 0xffffff8010521087

0xffffff8202ffbdc0 : 0xffffff8010cc2c7c

0xffffff8202ffbe30 : 0xffffff7f9533ecae

0xffffff8202ffbe70 : 0xffffff7f9533d8b9

0xffffff8202ffbec0 : 0xffffff8010563545

0xffffff8202ffbf40 : 0xffffff8010563071

0xffffff8202ffbfa0 : 0xffffff80104c713e

Kernel Extensions in backtrace:

com.apple.driver.AppleEmbeddedOSSupportHost(1.0)[D6FEBDA5-42DA-3745-A027-5A2F35A6F56F]@0xffffff7f9533c000->0xffffff7f95341fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f912a1000

dependency: com.apple.driver.AppleSMC(3.1.9)[601E041E-0A5C-3B6A-A4E6-45ECC7F48A2B]@0xffffff7f912f2000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

19E287

Friend of mine and I, both have a MBP 16 with Catalina 10.15.5.

Friend's MBP 16 does not have any issue, he has no external monitor, just the original external power supply.

My MBP ist mostly connected to the LG Ultrafine 5K external monitor (sold by Apple) and is powered by Thunderbolt from the monitor - no issue. When I connect the MBP in another office to the original external powersupply and to an Eizo EV2750 it crashes every time the MBP goes to sleep...

???

Did all the recent updates. Still crashes. No external monitors connected. Now it restarts, I load a program, then it freezes and crashes and restarts again. It’s been happening since first week of may

interesting discussions - I have the crashes with an external BenQ SW271 using USB-C cable. I I knew it would work with A2119 it would be some kind of fix, still I hope this will be solved with an update.

Btw, is there any evidence that apple follows this thread and is trying to fix these issues?

Yes I have tried the clean install. Backed everything up and wiped everything. ReLoaded OS did all the resets. Still nothing. I was on phones with tech support 3 different times trying to figure this out and nothing helped. They said the new update would fix it but it just made it worse

It’s the external monitor connected through a thunderbolt hub, like for my Benq.

It’s a week that before going to bed, I disconnect the external and put it to sleep with no problems. When the external is connected, 100% crash.

Using the external as a second monitor (not as the only one) I even solved a big problem of performance: I do not get anymore that 1300% cpu occupied by kernel_task with no apparent reason.

Anyhow... Catalina 10.15.5 is quite buggy... hope the 15.6 will solve...

Are you using a TB3 hub? The reason I'm asking is I'm actually using my old OWC TB2 hub via a TB3->TB2 adapter.

I'm wondering if that has anything to do with it.

I agree about 10.15.5. Very disappointing.

Yeah, this happens to me one or several times a day on my new Mabook 16", it also happened on my old 13" now and then but not as much. It seems like it happens mostly when the lid is closed.

I have several colleagues reporting the same issue and we're all running the latest version of OSX 10.15.5. I will try resetting the SMC but I will probably not be reinstalling the OS since I don't have time for this currently.

This is ridiculous. I'm having the same issue - at least with external monitor with a dongle. And the fans are loud all the time - I really thought that a new Macbook Pro would perform better than this joke of a machine.

I'm hopeful that the issue is resolved, and while I know software/hardware is hard and never perfect, there are two takeaways FOR ME; (1) the fact that this significant an issue passed quality testing on a $3,000+ laptop that is Apple's flagship notebook, considered a 'premium' product, and (2) the fact that it took nearly 4 months to get a fix.

If you market yourself as a 'premium' brand and charge 'premium' prices, then you need to deliver a 'premium' product AND 'premium' support. When inevitable mistakes are made, they need to be addressed immediately.

A BASE 16 MBP is $3k (easily can add thousands more in upgrades); add in a second Apple monitor $5k (not to mention the necessary appendages (aka adapters) required to connect anything) and you're looking at a BASE $8k system that would crash constantly for 4 months until a fix was issued.

FOR ME, that is unacceptable.

I agree with this completely. It’s frustrating enough that Apple does not offer a native docking solution given that it is such a common thing to do, but to have a critical issue that renders the computer almost unusable at a desk workstation for PRO users and then to leave it unaddressed through several patches is very frustrating.

So far 10.15.6 has fixed the issue for me.

2019 16” MBP

2.3 GHz 8 core i9

16GB RAM

5500M 4GB

Connected to Razer Core with a PowerColor 5700 XT Red Devil

My issue WAS that every time I would lock the computer and walk away - literally every time - I would come back to a kernel panic and a restart. Sometimes it only took 5 minutes, sometimes it took a few hours to happen (I know because it would reset the RGB on my keyboard when it finally happened). I tried everything. I prevented the Mac from going to sleep, messed with all of the energy saving settings... nothing.

This patch fixed that. I have been able to put the Mac to sleep, walk away for a day or two, come back and it wakes up, turns both monitors on and chugs on without issues.