Kernel Panic on 16" i9 MBPwRD

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!

Quick update re: FeedbackAssistant case w/ Apple. I was finally able to reproduce this crash on my machine again, and have sent a complete sysdiagnose to Apple (with 4 profiles installed). So we probably don't need to collect/send more sysdiagnose reports after hitting this crash until Apple engineers reply. That said, if you want to send one to Apple, I'm still happy to relay the FBA#.

I also wanted to thank everybody here who posted their experience, tips and tricks! Because of this information, I was able to build a solid theory and I can now reproduce this bug more reliably. The trick was not just to enable power nap, but to also queue up a *lot* of work to be done while the computer is asleep with Power Nap enabled. Please note that I've hit this kernel panic even with power nap disabled, but it happens less frequently.

My first attempt failed (adding ~ 1 gig of RAW photos on my MBP and shooting ~50 photos from my iPhone). For some unknown reason, my MBP wouldn't upload or download any changes while asleep (despite having power nap enabled for both battery and wall power). It would only sync while Photos.app was open and the computer was awake.

My second attempt was to repair my Photos.app libarary, which causes resync'ing of all ~13k photos (~350gigs). After the initial repair phases (and getting back to the grid view), I closed the lid and came back 3 hours later to a warm laptop. I opened it up, and the screen was blank and the T2-controlled Touch Bar was in a very odd state. After ~5 minutes of closing/opening the lid and switching between battery and wall power, the login screen finally appeared, and then the usual crash reporter window popped up. Thankfully I decided to film my laptop during the wake-up phase, which I included in my FBA case.

Anyway, I'll be sure to keep this forum updated with any new information as soon as it becomes available!

You definitely need to have a lot of items in the queue to be synced (downloaded or uploaded). The crash happened in my case because I bought a new macbook and it was downloading 70GB of pictures in sleep and this caused it to crash after about a hour. Regular small syncs will probably not trigger the bug.

Mine just crashed again, after running for almost a week with App Nap completely disabled.

I wasn't doing anything resource intensive, the only apps open were Zoom, Firefox, Google Chat, Whatsapp, Fantastical and Mail.

Used "Feedback Assistant" to submit to Apple, and linked this thread in the description. My feedback ID: FB7677896

I am having this problem on the MacBook Pro I received two days ago. It happens overnight when the laptop is closed.

MacBook Pro (16-inch, 2019)

2.4 GHz 8-Core Intel Core i9

32 GB 2667 MHz DDR4

Intel UHD Graphics 630 1536 MB

I am turning off power nap per some of these suggestions, but the crash happened whether I was connected to a larger display or not. I would close the laptop and next morning it "restarted because of a problem" and the error report contained much the same info: Beginning of my crash report:

panic(cpu 2 caller 0xffffff8002816487): "AppleIntelFramebuffer::setPowerState(0xffffff834aa53000 : 0xffffff7f85dbcd88, 1 -> 0) timed out after 45963 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

I am replying in hopes Apple will fix this problem. I paid a lot for a souped up MacBook Pro to replace my 2014(?...don't have it in front of me) model, which worked, but couldn't be upgraded to Catalina. I'm wondering if it was a mistake to get the new MBP. Bit discouraged...I have only had this machine for two days and it has crashed every night since I got it!

This should be the ultimate solution, as has been confirmed by another blog: https://medium.com/@canartuc/kernel-panics-in-new-macbook-pro-16-solution-is-here-2ac1d88fada7.

Also, there's no need to reset neither NVRAM/SMC with this bug. Not only because they won't be able to solve the problem permanently, but also because they might make things more complex, sometimes bring you new errors...

It looks like the next Catalina (10.15.5) fixes it. I'm running the latest beta and have not been able to reproduce the bug so far. Since the latest iOS and tvOS were just released publicly, 10.15.5 can't be far behind.

i'm installing the new update now 1.15.5 i hope this works

macOS Catalina 10.15.5 Update   –– Restart Required

macOS Catalina 10.15.5 introduces battery health management in the Energy Saver settings for notebooks, an option to control automatic prominence of video tiles on Group FaceTime calls, and controls to fine-tune the built-in calibration of your Pro Display XDR. The update also improves the stability, reliability, and security of your Mac.

Battery Health Management

• Battery health management to help maximize battery lifespan for Mac notebooks
• Energy Saver preference pane now displays battery condition and recommends if the battery needs to be serviced
• Option to disable battery health management

For more information, please visit https://support.apple.com/kb/HT211094

FaceTime Prominence Preference

• Option to control automatic prominence on Group FaceTime calls so video tiles do not change size when a participant speaks

Calibration Fine-Tuning for Pro Display XDR

• Controls to fine-tune the built-in calibration of your Pro Display XDR by adjusting the white point and luminance for a precise match to your own display calibration target

This update also includes bug fixes and other improvements.

• Fixes an issue that may prevent Reminders from sending notifications for recurring reminders
• Addresses an issue that may prevent password entry on the login screen
• Fixes an issue where System Preferences would continue to show a notification badge even after installing an update
• Resolves an issue where the built-in camera may not be detected when trying to use it after using a video conferencing app
• Addresses an issue for Mac computers with the Apple T2 Security Chip where internal speakers may not appear as a sound output device in Sound preferences
• Fixes a stability issue with uploading and downloading media files from iCloud Photo Library while your Mac is asleep
• Resolves a stability issue when transferring large amounts of data to RAID volumes
• Fixes an issue where the Reduce Motion Accessibility preference did not reduce the speed of animations in a FaceTime group call

Some features may not be available for all regions, or on all Apple devices.

For more detailed information about this update, please visit: https://support.apple.com/kb/HT210642

For detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222

Actually, it *might* be under this one:

• Fixes a stability issue with uploading and downloading media files from iCloud Photo Library while your Mac is asleep

I can reliably reproduce thIs kernel panic by causing a large amount of data to be uploaded via iCloud photos while the computer is asleep (repairing the library does it for me every time). That said, my laptop has been at Apple for repair (unrelated coffee spill), so I won’t be able to verify until sometime tomorrow...

It’s *unbelievable* how many Catalina bugs I’ve encountered due to Photos. I’m just hoping they’ve also fixed the metadata bug introduced in 10.15.0, but despite all of my open support and FBA tickets, and SERIOUS data loss issues, NOBODY AT APPLE HAS FOLLOWED UP. I gave them steps to reproduce this bug; you’d think they’d at least tell me a fix was released like they promised to do...

Gotta say, I don’t feel entitled to anything special; but after doing so much work to just restore my photos and have a reliable machine, being brushed off by Apple like this is totally unacceptable. If the bugs were in open-source code, I wouldn’t complain, but I can’t keep supporting MacOS if the threat of losing data and functionality for a year or more is always looming. Anybody know how to bring up the larger issues of stability and support problems with Apple in a meaningful way? Like to a VP of engineering?

I have a 2019 16" MBP and started having the same problem which always occurs with an external monitor connected and the MB going into sleep mode. I've found a work around which prevents the crash but by no means fixes the core issue. While connected to an external monitor I disable sleep mode. During a day of use the computer will not go to sleep but rather the screen saver comes on after a set time and requires a password to log back in. When the MB is disconnected from the external monitor and I'm mobile I turn sleep mode back on. As stated this is not a fix but simply a workaround. Hope this helps.

Same Kernel Panic and Sleep issues here with my 16" Macbook Pro that I purchased in December of 2019. Apple final asked me to bring in for repair. The replaced the entire Logic Board. I have now gone 3 weeks without an issue. Looks like this model has a Logic Board issue and it's not software related.

Thats standard procedure. I did that: normal reinstall, clean install etc.

didn‘t change anything. Its a catalina problem.

powernap off.

Don't post your logs here. Make a Feedback:

https://www.apple.com/feedback/

Thats the only way to report this.

Apple don't care about these discussions...

Forgot to mention, that the error is always about "thunderbolt power on failed"