Kernel Panic on 16" i9 MBPwRD

> 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/

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... :)

> I'm wondering: Can a "not crashing while app nap is off" rule out a hardware defect

Yeah, given that so many of us are experiencing the same kernel panic while sleeping after updating to 10.15.4 - it's almost 100% going to be a software rather than hardware issue.

If your machine is brand new, and you don't mind reinstalling, perhaps try downgrade to 10.15.3 and report back if that fixes the issue too?

As others have stated, this is definitely a software/firmware/BridgeOS bug that we have to wait for Apple to fix and release. None of the suggested work-arounds helped my MBP 16,1 either. Unfortunately the only solution I’ve found is to revert to 10.15.3, but that’s not feasible for me (and I wouldn’t recommend it for anybody, given there was at least one RCE security exploit in 10.15.3).

For what it’s worth, after 20 days with Apple support, I finally received another reply stating engineering is still investigating this bug. I’m not sure why anybody at Apple would suggest a hardware replacement instead of escalating to engineering first, but for what it’s worth, I just received the following response from Apple regarding the kernel panic in AppleIntelFramebuffer::setPowerState():

Thanks for your patience. I have received a response from our engineering team. This issue is still under investigation. It is recommended to stay up to date with the latest Firmware and Software for your Mac. If I receive any additional updates I will contact you directly. Thanks for all your time and efforts to help get this issue resolved. 

Sorry I don’t have any solutions (aside from never letting your laptop sleep), but hope this is of some help. Best of luck to everybody!

@vrtx0

Are you confirming that reverting back to 10.15.3 fixes the issue? I totally get how that is not a good solution but that information could help others that might want to revert back if they can!

[Edited by Moderator]

@ClassicII

I did not experience a kernel panic during sleep while I was back on 10.15.3. Unfortunately I only ran it for ~24 hours, though it did sleep 3-4 times. After going back to 10.15.4 (with supplemental update), I encountered the panic second time the computer went to sleep (uptime ~5 hours).

Wish I had a better datapoint for you — really appreciate all the effort you put into your site! If time permits, I’ll try the latest public beta and post any results w/ crash logs.

Thanks, this sure gives me some peace of mind :)

BTW: With power nap turned off it woke up just fine this morning. If that fixes the issue for the time being I‘d rather not go through the hassle of downgrading to be honest.

Very helpful - brand new MacBook Pro fresh out of the box, no external devices and updated to latest showing the same problem - the default 'power nap' option is on under the power adapter settings - turning that off has so far stopped it.

So, I finally got a (rather infuriating) reply from Apple on the Feedback Assistant case I opened on April 9th. I already collected and sent sysdiagnose data via support, and even referenced the support ticket number in my feedback case. The last response I got from support stated they had enough data to work on this bug, but I’ll go ahead and collect/send this data *again*, unless anybody has heard they already have enough data...

Does everybody have to go through this nonsensical back-and-forth with Apple when you find a bug, or is it just me? Here’s what I just received:

“We need additional information in order to continue investigating this bug. We need sysdiagnose output collected immediately following reboot to recover from panic in order to trige this.”

Yep, and confirmed it still crashes with power nap disabled on both battery and wall power sources (it’s disabled by default on battery). FWIW, it didn’t seem to change the frequency of crashes for me at first, but after methodically testing ~10 different settings in system prefs, I reset all energy settings to default, disabled power nap again, and went ~4 days without a crash. A few days ago, the panics kicked back up, and while it’s still a bit early to draw a conclusion, it does still seem to happen more often with power nap enabled...

Thanks for checking though — I definitely recommend others try it exactly as you outlined, especially as several people have reported success in this thread.

vrtx0 wrote:

So, I finally got a (rather infuriating) reply from Apple on the Feedback Assistant case I opened on April 9th. I already collected and sent sysdiagnose data via support, and even referenced the support ticket number in my feedback case. The last response I got from support stated they had enough data to work on this bug, but I’ll go ahead and collect/send this data *again*, unless anybody has heard they already have enough data...

Does everybody have to go through this nonsensical back-and-forth with Apple when you find a bug, or is it just me? Here’s what I just received:

“We need additional information in order to continue investigating this bug. We need sysdiagnose output collected immediately following reboot to recover from panic in order to trige this.”

If you filed a bug report then you where selected to help sort it out; It is not always the case.

You do no have to reply if you are worn out.

Thank you for your service.

FWIW, Automatic graphic switching didn’t have a measurable impact on frequency in my tests.

I’m actually trying to reproduce the bug right now so I can submit verbose logs and sysdiagnose to Apple. Even w/ power nap enabled (when on battery and plugged in), I’ve had no crashes in ~48 hours. Does anybody know of a way to reproduce this bug more frequently (or reliably)?

To anybody who encounters this bug, please run a sysdiagnose (press Cmd + Ctrl + Option + Shift + . (Period) at the same time) as soon as you log in (immediately after hitting the bug). Once complete, a Finder window will pop up with the sysdiagnose file. Please open up a ticket via Apple’s Feedback Assistant (feedbackassistant.apple.com), attach the sysdiagnose file, mention FB7658531, and then post/send your FBA ticket number so I can alert them.

Also, Apple didn’t ask me to install any specific profiles, but they did include this link:

https://developer.apple.com/bug-reporting/profiles-and-logs/

I installed a few that I thought *might* be helpful, but I’m also trying to get >6 unrelated bugs fixed. So most people shouldn’t worry about installing a profile — only if you feel comfortable/experienced with installing/removing profiles.

Any/all help appreciated! Hopefully we can get engineering on this sooner rather than later!

Rozak my reboot when sleep did not come back after re-enabling power nap.

I have been running for 7 days with intense use and with Power Nap re-enabled without any problems at all. 10.15.4

So I can’t reproduce.

Just to add on to what everyone is saying and to supply some new data, I upgraded to 10.15.4 whenever it came out but I did not experience any issues until two days ago when I imported around 40GB worth of photos from my iPhone to the Mac Photos app, which shouldn't be a problem for the computer to do. I reset my SMC yesterday after the crash happened but it happened again, but then I found this thread so I disabled the power nap functionality to see if that resolves the issue. I called Apple and they want me to wipe everything off my computer and reinstall as new to see if the problem still persists, but I would rather not have to do that.