Kernel Panic on 16" i9 MBPwRD

I bought my MBP 16" on May 6 with Catalina 10.15.3.

I experienced a lot of KP when it goes to sleep (with or without external monitor).

After update to 10.15.4, I experienced KPs each 5 days, normally during the late night.

After update to 10.15.5 (19F96), just lock my computer and wait for the screen gets off with an external monitor connected causes a KP.

I just updated to 10.15.5 19F101 and seems that it does not happen anymore.

Let's see in a long term if the recurrent KP problems with a brand new MBP 16" finally gets resolved.

Thanks all for sharing with the community. I've been having this issue for a long time with my 16" MBP and applecare has been awful. I sent the machine in, they claimed they couldn't reproduce, sent it back, spent hours on the phone with them and finally they agreed to escalate the ticket to a product engineer. A few days later, they came back saying "PE thinks it's a hardware defect, please ship to us again to replace logic board." At this point I have 0 confidence AC knows how to fix, even after escalating to a leadership level contact I have from friends there. The good news is, it sounds like this might be fixed in an upcoming software update, let's keep our fingers crossed for 10.15.6. I can confirm, like others, that 10.15.5 + Supplemental Update have not addressed it.

It might be turning off and turning on "Power Nap" might be the temporary solution?

Unfortunately, I can confirm the issue persists in 10.15.4.

I have the MacBook Pro 16 2019 i9 16GB 1TB w/ this exact issue. I also posted my bug report a little while ago.

I hope an Apple engineer see this post too and can fix this issue in 10.15.5.

I have the exact same problem with sleep. Mine just started with the "upgrade" to 10.15.4 though and wasn't an issue before. MBP 16" 16GB, 1TB, i9. Purchased December 2019. I did contact Official Apple Support. The only advice I received was to reinstall MacOS. I'll try the SMB trick first before I go to the last resort. Especially since this just started with 10.15.4, and I doubt reinstalling the same OS will have any effect.

Hi All,

I hope the automatic graphics switching and/or power nap settings help others, but I wanted to mention they didn’t impact the crashes on my particular system (16” MBP w/ 8GB 5500M GPU, 2TB, 32GB).

Disabling automatic graphics switching may have made the crashes slightly less frequent, but nothing dramatic. I’ve tried enabling power nap, but didn’t notice a difference on my system (so I keep it disabled).

FWIW, I usually leave my MBP plugged into power, and I *think* the crashes tend to happen about 1-4 hours after sleep. My MBP has occasionally spuriously woken up from sleep (my Apple Watch notifies me it has authenticated my MBP login, but the laptop screen doesn’t turn on). The last time this happened, I noticed the crash appeared in the system logs About an hour after the Apple Watch notification. My MBP is ~5 feet away from my bed, so I would have noticed the display turning on...

Anyway, hope this helps!

P.S. Apple support was supposed to call back with an update ~3-4 days ago, but as seems to be the norm these days, nobody calls back no matter how many voicemails I leave for my Sr. Advisor.

Yeah. Same here... Every morning the same. its annoying. Especially with a 4000+ $ Notebook.

And the usual standard support procedure does not help:

– SMC Reset

– PRAM Reset

– Different users

– Reinstall Catalina without deleting

– Cleaninstall via Net Recovery (with no use of backup)

Last week i spent over 8 hours in support calls with various technical supervisors. they just talking about Clean install among other things nobody could help me etc etc.

I asked them several times to involve the technical engineers in the whole process. Also with the request that this thread as a collection of users with the latest $3000+ flagship hardware have the same problem.

Instead of every user reporting the same thing and making standard procedures pointless, they would rather listen to the users and fix the problem, which is 100% Apple's fault, namely a bug in Catalina 10.15.4, or maybe even AMD Graphics drivers.

But unfortunately they only seem to know standard procedures and don't give a **** about the users.

The only way to put some pressure on them is to post in many independent Apple forums and to write to various news sites.

Sad, actually. You have users who have the most expensive Apple flagship notebooks and free bug reports and nobody at Apple is interested.

Apparently the only way to get the attention of the public is to get their fingers out of their *****.

Agreed with jsima — my case has been escalated to engineering for ~10 days now with no action at all. Most support reps still deny they’ve ever run into this bug.

Along those lines... If most of what’s involved in this bug is open source, we *might* be able to find a fix or work-around ourselves. Does anybody know if it’s possible to build your own XNU kernel for Catalina? Or are we locked out of loading custom kernels (e.g. from T2, Secure Enclave, etc.)?

Since the power state timeout functionality is in the XNU kernel (which is still open source), there may be something we can change. That said, I’m fairly sure the Intel video driver is closed source, so there’s no guarantee of a fix/work-around via custom XNU kernel...

I’ll take a closer look at the referenced XNU source lines in the panic when time permits, and any relevant debug symbols for the Intel kext that are public... Any tips/current links to custom kernel builds would be greatly appreciated!

Fair enough... and thanks for looking into it. Let's hope someone will see this thread and help from their side. Disabling powenap has been a lot better for me so far as others mentioned if it helps your investigation. Cheers.

It's happened to me twice in the last two days, and I was just about to say I had "Prevent computer from sleeping [etc.]" turned on in Settings (under Power Adapter) but realized I didn't. So I assume that would "fix" it as well.

I push my machine pretty hard with multiple VM's (16" i9, 32GB RAM, 1TB) and dev tools and frequently do leave it awake for long periods. Does Panic! At the Kernel only happen when plugged in or has it happened to anyone on battery? (I know it's unusual to leave power nap enabled on battery power but I used to do it for some reason.)

Thanks for being there in these challenging times!

Is UAudio a Kext from UAD? I noticed in my own log the following:

last unloaded kext at 3036456155703: >!UAudio 322.2 (addr 0xffffff7f93c48000, size 434176)

I do own UAD hardware. However, I have never installed UAD software on this macbook nor have I ever connected my UAD hardware to this macbook. Could UAudio be referring to something else here, besides Universal Audio?

Listing non apple kext:

Just chiming in to say I've experienced the same issues on a 2016 i9 after opening the lid / waking from sleep:

panic(cpu 0 caller 0xffffff8001616487): "AppleIntelFramebuffer::setPowerState(0xffffff86965ed000 : 0xffffff7f84b01d88, 1 -> 0) timed out after 45909 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffff8738cabb40 : 0xffffff8000f215cd 
0xffffff8738cabb90 : 0xffffff800105a3c5 
0xffffff8738cabbd0 : 0xffffff800104bf7e 
0xffffff8738cabc20 : 0xffffff8000ec7a40 
0xffffff8738cabc40 : 0xffffff8000f20c97 
0xffffff8738cabd40 : 0xffffff8000f21087 
0xffffff8738cabd90 : 0xffffff80016c2c7c 
0xffffff8738cabe00 : 0xffffff8001616487 
0xffffff8738cabe50 : 0xffffff8001615d69 
0xffffff8738cabe60 : 0xffffff800162d2fe 
0xffffff8738cabea0 : 0xffffff8001614b18 
0xffffff8738cabec0 : 0xffffff8000f63545 
0xffffff8738cabf40 : 0xffffff8000f63071 
0xffffff8738cabfa0 : 0xffffff8000ec713e 

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide:     0x0000000000c00000
Kernel text base: 0xffffff8000e00000
__HIB  text base: 0xffffff8000d00000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO

System uptime in nanoseconds: 106986123069622
last loaded kext at 106710472243982: >usb.IOUSBHostHIDDevice	1.2 (addr 0xffffff7f84ade000, size 45056)
last unloaded kext at 105722513202990: >!UAudio	322.2 (addr 0xffffff7f88294000, size 434176)

I have the exact same issue on my i9 16", with possibly the same smoking gun?

last unloaded kext at 105722513202990: >!UAudio	322.2 (addr 0xffffff7f88294000, size 434176)

Mine is a bog-standard system, no third-party kext's:

~                                                                                                                                                                                                                          
▶ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

~                                                                                                                                                                                                                          
▶

Yes, @ClassicII 's write up is fantastic and actually was the start of my whole research and my need to contribute. Turned app nap off after the last crash, forgot to mention that, sorry. Let's see how it goes.

I'm wondering: Can a "not crashing while app nap is off" rule out a hardware defect or may this just mask an underlying issue? I'm quite an amateur in regards to hard-/software so, sorry if this may sound like a silly question... :)