Kernel Panic on 16" i9 MBPwRD

I'm having this issue for the last a few days.

My configuration: MBP 2019 16" i9 2.3 GHz, 16 GB RAM

Steps to reproduce:

1. The mac is connected to an external monitor through a USB C-HDMI cable
2. The power is connected through an external USB-C hub
3. The MBP lid was open
4. I manually sent it to sleep by clicking the Sleep button using the top left Apple menu at night.
5. Used the keyboard and mouse to wake it up
6. After a while, the machine restarts instead of waking up.

I'm attaching the panic log from Console.

MBP has not went into panic after Sleep since the following actions for about 5 days (sleeping at least once daily):

1. Updated macOS Catalina 10.15.4 Supplemental Update https://support.apple.com/kb/DL2038?locale=en_US
2. Reset PRAM/VRAM and SMC
3. Disabled PowerNap in Energy Saver for Battery and Power Adapter

However, the MBP sadly just crashed again after awaking it from sleep mode.

panic(cpu 0 caller 0xffffff8019a91b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks.

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

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.

It is definitely the powernap option. I have an OWC Thunderbolt 3 dock with two external EIZO screens. Without powernap no Kernel Panic with powernap always Kernel Panic. As I do a timed restart all mornings 4:00 am I see the result right after login at 7:15am. Thanks for the tip with powernap.

I did not reset nvram nor smc.

I finally heard back from Apple support today. The rep acknowledged that Engineering is aware of this issue, and asked a series of questions (some quite general, so it seems they haven't made it very far debugging the issue).

I briefly perused the XNU source mentioned in the kernel Panics we're all getting; the logic is related to a fairly general IOKit abstraction that manages the power state transitions of the mentioned driver (AppleIntelFramebuffer) or a parent of that drive. This appears to be the same code path used by any driver that handles power state transitions (cf. IOService::ackTimerTick() in IOServicePM.cpp).

Given the the actual problem is that the Intel driver isn't changing it's state within 45 seconds (which seems beyond ample for these machines), I fear this may take some time for the worst of reasons. Unless apple actually has a license to the driver's source and/or detailed and accurate hardware specs from Intel, Apple engineers might be facing a binary blob that requires Intel engineers to actually address (and Apple to integrate into some future update). But I'm not blaming Intel either; the bad power state could easily have come from Apple missing their API. Regardless, we're likely going to have to wait for two companies to debug and oddly intermittent issue. FWIW, I opened FB7658531 and offered to give full access to my machine to help them diagnose, but it seems that Apple has an *insane* policy that prevents their engineers from working directly with customers.

I know this information is only useful to the most technical users, but hopefully it saves somebody some time. If I get any additional information or status updates from Apple, I'll be sure to share, but again because of an insane policy, they don't give any updates until *after* the fix is released.

Here's the relevant code from IOServicePM.cpp in the XNU kernel that led to the above conclusions:

bool IOService::ackTimerTick( void )
{
    IOPMinformee *      nextObject;
    bool                done = false;

    PM_ASSERT_IN_GATE();
    switch (fMachineState) {
        case kIOPM_OurChangeWaitForPowerSettle:
        case kIOPM_ParentChangeWaitForPowerSettle:
            // are we waiting for controlling driver to acknowledge?
            if ( fDriverTimer > 0 )
            {
                // yes, decrement timer tick
                fDriverTimer--;
                if ( fDriverTimer == 0 )
                {
                    // controlling driver is tardy
                    uint64_t nsec = computeTimeDeltaNS(&fDriverCallStartTime);
                    OUR_PMLog(kPMLogCtrlDriverTardy, 0, 0);
                    setProperty(kIOPMTardyAckSPSKey, kOSBooleanTrue);
                    PM_ERROR("%s::setPowerState(%p, %lu -> %lu) timed out after %d ms\n",
                        fName, OBFUSCATE(this), fCurrentPowerState, fHeadNotePowerState, NS_TO_MS(nsec));

// <snip>

if (gIOKitDebug & kIOLogDebugPower)
                    {
                        panic("%s::setPowerState(%p, %lu -> %lu) timed out after %d ms",
                            fName, this, fCurrentPowerState, fHeadNotePowerState, NS_TO_MS(nsec));

HTH...

NOTE: THIS ADVICE IS NOT FROM ME, I FOUND THIS FROM ANOTHER APPLE SUPPORT FORM. USE AT YOUR OWN RISK

Sleep issue are often sorted by

resetting the SMC https://support.apple.com/en-us/HT201295

If no resolve—

Try a SafeBoot https://support.apple.com/en-us/HT201262

Takes noticeable longer to get to the login screen, does a 5-15 minute disk repair before it fully boots up, and certain system caches get cleared and rebuilt, including dynamic loader cache, etc. Login and test. Reboot and test

This test will tell you if third party interference; extensions etc are not loaded in safe boot mode.

If you still need further assistance—

To get a good look at your System config. for conflicts or issues, you can run this trusted utility http://etrecheck.com

If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.

You can set its preference to "Allow full Disk Access", with this you get a digest of issues from the last 7 days that are saved in your system.

AppleSupportOntario wrote:

NOTE: THIS ADVICE IS NOT FROM ME, I FOUND THIS FROM ANOTHER APPLE SUPPORT FORM. USE AT YOUR OWN RISK

Sleep issue are often sorted by

resetting the SMC https://support.apple.com/en-us/HT201295

If no resolve—

Try a SafeBoot https://support.apple.com/en-us/HT201262

Takes noticeable longer to get to the login screen, does a 5-15 minute disk repair before it fully boots up, and certain system caches get cleared and rebuilt, including dynamic loader cache, etc. Login and test. Reboot and test

This test will tell you if third party interference; extensions etc are not loaded in safe boot mode.

If you still need further assistance—

To get a good look at your System config. for conflicts or issues, you can run this trusted utility http://etrecheck.com

If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.

You can set its preference to "Allow full Disk Access", with this you get a digest of issues from the last 7 days that are saved in your system.

I'd be curious to know this other " ANOTHER APPLE SUPPORT FORM." and if you could site the specific link.

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!

Hi there.

I have the exactly same error. Additionally, my MacBook Pro 2019 16'' i7 16GB is overheating every time to more than 70º C.

Any solution for this problem?.

panic(cpu 4 caller 0xffffff8009816487): "AppleIntelFramebuffer::setPowerState(0xffffff81b8997000 : 0xffffff7f8cdf3d88, 1 -> 0) timed out after 45960 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

Backtrace (CPU 4), Frame : Return Address

0xffffff922e563b40 : 0xffffff80091215cd 

Complete error is attached.

Hi all,

Same problem here (i9 / 32gb of ram / radeon 5500M 8gb)

Disabling power nap now, will report back. Did anyone manage to get anything from support? I have reset SMC and reinstalled completely...

Thanks and good luck!

I just spoke to Apple's support.

I said that in this discussion many users have the problem and it is well described where the problem is.

"It's just a discussion."

They don't seem to care.

They never look at Apple Discussion. They only way to reach out apple is via the following feedback link:

Product Feedback - Apple

They never look at Apple Discussion. They only way to reach out apple is via the following feedback link:

Product Feedback - Apple

Exactly.

This is a User to User tech support forum. It is not used for anything else. It is for users to help out with problems they can actually help out with.

If you have a problem that another user cannot solve, you need to call AppleCare or take your Mac to a Genius Bar or certified repair center.

If it is an actual bug in Apple's code, talking to Apple will get Apple's attention on the problem.

Posting a bunch of "me too's" here won't solve the problem or highlight it in any way to Apple.

Had the same issue again today after today's update (10.15.4 (19E287)).

So USB-C fix did not do anything about it, sadly :-/

panic(cpu 4 caller 0xffffff8008816487): "AppleIntelFramebuffer::setPowerState(0xffffff81b7ab0000 : 0xffffff7f8bdf9d88, 1 -> 0) timed out after 45964 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 4), Frame : Return Address
0xffffff81f9ed3b40 : 0xffffff80081215cd 
0xffffff81f9ed3b90 : 0xffffff800825a3c5 
0xffffff81f9ed3bd0 : 0xffffff800824bf7e 
0xffffff81f9ed3c20 : 0xffffff80080c7a40 
0xffffff81f9ed3c40 : 0xffffff8008120c97 
0xffffff81f9ed3d40 : 0xffffff8008121087 
0xffffff81f9ed3d90 : 0xffffff80088c2c7c 
0xffffff81f9ed3e00 : 0xffffff8008816487 
0xffffff81f9ed3e50 : 0xffffff8008815d69 
0xffffff81f9ed3e60 : 0xffffff800882d2fe 
0xffffff81f9ed3ea0 : 0xffffff8008814b18 
0xffffff81f9ed3ec0 : 0xffffff8008163545 
0xffffff81f9ed3f40 : 0xffffff8008163071 
0xffffff81f9ed3fa0 : 0xffffff80080c713e 

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:     0x0000000007e00000
Kernel text base: 0xffffff8008000000
__HIB  text base: 0xffffff8007f00000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO
System uptime in nanoseconds: 16793191502905
last loaded kext at 15588013917321: >usb.IOUSBHostHIDDevice	1.2 (addr 0xffffff7f8ca0f000, size 45056)
last unloaded kext at 4648926173899: >!AXsanScheme	3 (addr 0xffffff7f8bdcf000, size 32768)

There has been a Supplemental update to the macOS10.15.4

see if that resolves your issue:

Download macOS Catalina 10.15.4 Supplemental Update https://support.apple.com/kb/DL2038?locale=en_US

If no resolve.:The work around is to disable PowerNap in

>System Preferences>Energy Saver