Kernel Panic on 16" i9 MBPwRD

There are two power nap options. one under battery and one under power adaptor. Just make sure both disable.

Did you disable power nap in both tabs in energy saver? As depicted in the image below?

?

Just reporting - I've gone 5 days without issues after disabling power nap for both battery and power adapter.

Powernap off. That solves it.

I have the exact same issue after 10.15.4. I'm currently trying to work with apple support as the kernel panics appear to be due to a timeout in the Intel graphics driver's power state handling. That said, I just noticed that both of us have the latest Universal Audio driver (I have a UAD Apollo Twin). That said, I haven't actually connected any device in several days, and I've had at least 4 identical crashes since the update...

I've lost faith in Apple Support being able to work with engineering to resolve issues that go beyond the basic script of steps. I've had 15 tickets opened for various iOS and MacOS issues (I lost ~1k photos, 20GB iCloud Drive, missing iMessages and SMS on my iPhone, missing vCards, and other horrible problems). I've wasted >100 hours on the phone, and so far I only have 3 RTAs (none of which have been fixed in the latest updates), and Creative Media decided an appeasement would be easier than recovering my photos (or even figuring out why I'm experiencing so many iCloud issues)... But I digress, and apologies for the rant.

I'll try to uninstall the. UA drivers and post back here if there's any consistency. In the mean time, if anybody else is experiencing this same crash in AppleIntelFramebuffer::setPowerState(), could you post if you do or do not have the UAD audio interface driver installed?

Here's my latest crash log -- HTH!

Just to follow up, I removed the Universal Audio software and kexts from my system, but it had no impact on this bug.

So far, I’ve tried everything support has suggested (reboot to safe mode, reinstall macOS), but obviously this had no impact on the bug introduced in 10.15.4.

I also submitted sysdiagnose data 3 days ago, but can’t get my Sr. Advisor (or anybody at Apple) to follow up. They’ve missed 2 callbacks, and I wasted 1.5 hours on the phone trying to get an update. Every rep I’ve talked to (except the first one) has denied this is a known issue, and claimed I’m the first one they’ve talked to about this problem.

I really wish Apple would at least acknowledge this issue so others don’t have to waste so much time eliminating variables. That said, I think it’s still worth calling support to report the problem and ask them to escalate it so they know it’s impacting everybody (or most people). I’m on my 3rd 16” MBP i9 w/ 2TB SSD since December.

Best of luck to everybody...

If you have a way of engaging apple support to get there attention, I would love to hear your suggestions.

I already told you how. You report a problem with your Mac to AppleCare or a Genius Bar. That is the only way they will identify the problem. When you get garbage responses from the AppleCare people, you ask to talk to a supervisor. And, you keep asking to elevate the problem. You tell them that you have already erased the drive and reinstalled the OS. Nothing else is installed and the problem persists. If you actually still have AppleCare, then you make them repair it.

After some days without any problems and quit heavy using I think the problem could be solved under certain circumstances:

• MBP 16" with the lowest available configuration. No special graphic adjustments or special software in using, just the standards for office. Power nap is still on. Using with power plug in and without. Multiple times closing and opening the MBP. Sometimes with longer breaks.

After the known kernel panics with opening the book I have done the following steps, which were helpful, apparently at least:

1. SMC/VRAM-Reset
2. Turning of the Mac, waiting a view minutes, turning on.

It seems the low profile MBP 16" (probably the graphic unit) haven't has such a deep problem. Especially these steps helps although the power nap feature is on.

Of course I can't say that it helps anybody with the same kind of MBP 16" but in my case the problem is really solved.

Good luck to anybody!

Thanks, that’s definitely the same crash... There’s one common thing I’m noticing in *way* more of these crash reports than I would expect, which is the presence of kext’s from Universal Audio. I also have the latest UAD software installed, but I still hit this bug while the software was uninstalled *and* I had removed every non-Apple kext (verified w/ kextutil)... I suppose it’s possible that the sleep image in /private/var/vm is retaining a cached version, but Apple has obfuscated virtually every user-facing logging/debug utility over the past 2 years. I have a theory I’d like to verify:

To all users hitting this Panic: could you please post here if you do or do not have software from Universal Audio installed on your system (regardless of whether or not it’s ever been used or attached to hardware)? Also, if you’ve tried disabling power nap, could you post whether or not this stopped the crashes?

My theory isn’t specific to Universal Audio drivers; it has more to do with the driver depending on a user space process which depends on a graphics driver. So I’d also be curious if this bug is impacting any users who may have hardware that’s tightly integrated with OS software (or still have drivers for any such device).

If we can confirm this theory, it’s possible we could ask companies like Universal Audio to help identify a work-around. Any info greatly appreciated!

I just got a 2 new 16" provided by Apple and with same config - only ms office, what's app desktop. nothing else. 1 enable nap and another with disable. I keep getting reboot with the one enable nap. While the one I disable, no occurrence for the last 48 hrs. no external devices connect.

> Any advice is highly appreciated.

I've turned off "app nap" on mine (look in System Preference > Energy Saver), and haven't had any crashes in a couple of days. This is a workaround while Apple hopefully looks into the issue.

Have you read the excellent write up that @ClassicII posed above? Here's the link again: https://mrmacintosh.com/10-15-4-update-wake-from-sleep-kernel-panic-in-16-mbpro-2019/

I have had this issue since I purchased the 16" MacBook Pro back in Feb. but only now getting around to finding a resolution. I see that this issue was first reported back in Dec. 2019. I will open a support call as well and see if I can get an update on when the fix will be delivered.

For now, I will try disabling the Power Nap option and reset SMC and NVRAM and let that run for while to see if I still see daily crashes. I do not have any USB devices connected besides the power cable.

Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. 

MacBook Pro 16" 2019

2.6 GHz 6-Core Intel Core i7

16 GB 2667 MHz DDR4

Intel UHD Graphics 630 1536 MB

Catalina 10.15.4

I spoke again yesterday with a higher employee of Apple, not Tech Supervisor Level 2, who looked at the status of this powernap problem. Looks like Apple is aware of this problem, they are working on it. Could possibly come with the next update.

Regarding prioritization he said. You should report the case via phone/chat. And not via feedback form.

Since this logically causes more work, i.e. more costs in the end. This means that the problem is also prioritized higher. Because Apple wants to keep the costs for support as low as possible.

I hope we see an update soon.

@Vonstrovsky: I don’t mean to offend, but I wanted to point out there are quite a few factual errors in that article. Nothing indicates a power design or GPU switching issue — the screenshot “proving” it just points to the word panic (an old term for an unrecoverable OS error), and the fact that the Radeon kext was loaded at the time. Nothing indicates that kext was actually in use at the time of the crash). The author’s description of how GPUs work in general (and with external displays) appears incorrect; not really sure what to make of it. Apologies if that sounds harsh; just trying help mitigate misinformation.

There’s a great write up of this bug on the Mr. Macintosh blog (mentioned previously in this thread): https://mrmacintosh.com/10-15-4-update-wake-from-sleep-kernel-panic-in-16-mbpro-2019/

The author provides a great (and accurate) description of the bug, and keeps the article updated (it was just updated 2 days ago to note this bug appears to be fixed in the latest 10.15.5 beta). I’ve found other articles on that site very informative; the author(s?) seems very proficient, eloquent and motivated to help others. It’s rare to find that level of quality on a blog, IMHO.

HTH!

Just got a response from opened apple support ticket: We know about this problem with MBP 16" and you should wait for the next Catalina update in order to check if the KP problems stopped.

I really like apple products and I'm also a heavy user (macbook, iphone, airpods, etc), but this kind of thing is really frustrating and i'm very sad with that situation :(