After Big Sur 11.6.4 update iMac Pro shuts down while in sleep mode (Sleep Wake failure in EFI Failure code:: 0x00000000 0x0000001)

[nkl984]

After Big Sur 11.6.4 update iMac Pro shuts down while in sleep mode.

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time: 2022-02-15 20:28:21.769 +0200
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 32

Data Source: Stackshots
Shared Cache: 1D800E79-F93F-3FEF-9658-B168A649E2E4 slid base address 0x7fff203aa000, slide 0x3aa000

Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 12s



Process: swd [353]
Architecture: x86_64
Footprint: 460 KB
Time Since Fork: 1s
Num samples: 1 (1)

Thread 0xc61 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 1 (libdyld.dylib + 89917) [0x7fff206d3f3d] 1
1 ??? [0x103023454] 1
1 ??? [0x1030231e8] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 146934) [0x7fff206a5df6] 1
*1 ??? [0xffffff80002311f6] 1
*1 ??? [0xffffff800093ed0e] 1
*1 ??? [0xffffff8000848e71] 1
*1 ??? [0xffffff80002544ff] 1
*1 ??? [0xffffff800028ba8d] (running) 1

Binary Images:
0x7fff20682000 - 0x7fff206b1fff libsystem_kernel.dylib (7195.141.19) <FDF07FB0-42C8-3732-8868-1E9518FB99B3> /usr/lib/system/libsystem_kernel.dylib
0x7fff206be000 - 0x7fff206f9fff libdyld.dylib (852.2) <5FBD0E1A-ACCE-36DB-B11C-622F26C85132> /usr/lib/system/libdyld.dylib
Model: iMacPro1,1, BootROM 1715.81.2.0.0 (iBridge: 19.16.10744.0.0,0), 8 processors, 8-Core Intel Xeon W, 3,2 GHz, 32 GB, SMC
Graphics: kHW_AMDRadeonProVega56Item, Radeon Pro Vega 56, spdisplays_pcie_device, 8 GB
Memory Module: NODE 1/CPU1_DIMM_A0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK
Memory Module: NODE 1/CPU1_DIMM_B0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK
Memory Module: NODE 1/CPU1_DIMM_C0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK
Memory Module: NODE 1/CPU1_DIMM_D0, 8 GB, DDR4, 2666 MHz, Hynix, HMA81GR7AFR8N-VK
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Aug 10 2021 19:55:28 version 9.30.444.18.32.5.71 FWID 01-93db3422
Bluetooth: Version 8.0.5d7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
USB Device: USB 3.0 Bus
USB Device: 4-Port USB 3.0 Hub
USB Device: Card Reader
USB Device: 4-Port USB 3.0 Hub
USB Device: 4-Port USB 2.0 Hub
USB Device: Launchkey MK3 37
USB Device: 4-Port USB 2.0 Hub
USB Device: iPad
USB Device: Portable SSD T5
USB Device: Apple T2 Bus
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: iMac Pro, Apple Inc., 41.5
Thunderbolt Bus: iMac Pro, Apple Inc., 41.5

 

[cfm56d7b]

I just upgraded to Big Sur 11.6.4. The same problem but with a different root cause based on the message below. Initiating sleep and kernel panic occurs about 2 hours after sleep mode started.

panic(cpu 0 caller 0xffffff8012c6041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0x4f8c5.

 

[nkl984]

I just upgraded to Big Sur 11.6.4. The same problem but with a different root cause based on the message below. Initiating sleep and kernel panic occurs about 2 hours after sleep mode started.

panic(cpu 0 caller 0xffffff8012c6041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0x4f8c5.

Please report it!

 

[Hombre53]

You have a backup right? Revert back to 11.6.3 until Apple fixes this...

 

[NeonIbis]

I just upgraded to Big Sur 11.6.4. The same problem but with a different root cause based on the message below. Initiating sleep and kernel panic occurs about 2 hours after sleep mode started.

panic(cpu 0 caller 0xffffff8012c6041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0x4f8c5.

I got this too but on 11.6.3. My error message was almost identical:

panic(cpu 0 caller 0xffffff801326041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0xa01b.

I reported it from the error dialogue, then updated to 11.6.4, but that doesn't seem to fix anything.

 

[NeonIbis]

I got this too but on 11.6.3. My error message was almost identical:

panic(cpu 0 caller 0xffffff801326041a): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleIntelICLLPGraphicsFramebuffer. Thread 0xa01b.

I reported it from the error dialogue, then updated to 11.6.4, but that doesn't seem to fix anything.

... And I can now confirm the same error on 11.6.4 😞

 

[cfm56d7b]

Initiated Sleep mode yesterday and computer crashed within 20 minutes with the same error. Plan to shut down the computer overnight instead of Sleep.

 

[cfm56d7b]

Initiated Sleep mode yesterday and computer crashed within 20 minutes with the same error. Plan to shut down the computer overnight instead of Sleep.

Tried Sleep function again yesterday. At least Big Sur 11.6.4 is consistent: the system crashed again with the same error. The report was sent to Apple.

However, after restarting the search in Outlook for Mac stopped working. Restarted the system again. Thankfully, the search in Outlook for Mac began to work again (which tells me when the system crashed overnight something happened to Spotlight).

 

[cfm56d7b]

Hopefully this may be helpful. Will try it tonight.

From https://discussions.apple.com/thread/251441676

I too was extremely frustrated by this (MBP would crash every time it went to sleep while connected to a dock) until I came across another thread here which fixed the issue for me and others. Go into System Preferences -> Notifications -> Do Not Disturb -> Turn on Do Not Disturb and check "When the display is sleeping." This will prevent the OS from showing notifications while your computer is sleeping, which is causing major problems when an external monitor is hooked up. Who wants this feature anyway. It's silly, and it's especially silly that it's causing people's computers to kernel panic.

 

[cfm56d7b]

Hopefully this may be helpful. Will try it tonight.

From https://discussions.apple.com/thread/251441676

I too was extremely frustrated by this (MBP would crash every time it went to sleep while connected to a dock) until I came across another thread here which fixed the issue for me and others. Go into System Preferences -> Notifications -> Do Not Disturb -> Turn on Do Not Disturb and check "When the display is sleeping." This will prevent the OS from showing notifications while your computer is sleeping, which is causing major problems when an external monitor is hooked up. Who wants this feature anyway. It's silly, and it's especially silly that it's causing people's computers to kernel panic.

Sharing an update after following above instructions and initiating Sleep cycle.

The system did not crash overnight. It's only one but encouraging data point.

If turning on Do Not Disturb when the Display in Sleeping (in Notifications) is indeed the solution, then Apple engineers need to return to the university they graduated from and retake a few computer science classes.

The hardware state - no display available because computer is sleeping - is a higher level condition that the software must honor (unless there is another condition present, i.e. Can Wake Up the Computer If The Notification is Critical).

Pseudo code for Apple engineers (simplified):

1. Trigger notification
2. Is the computer allowed to wake up? No - then queue notification
4. If the computer IS allowed to wake up because notification is critical: wake it up, activate displays, display current and queued notifications
5. Return to Sleep after specified interval

Please correct this error and I will be the first in line to give B- grade, reflecting a discount for the original defect and lack of integrated testing because the entire team has been working on Universal Control instead.

 

[cfm56d7b]

Sharing an update after following above instructions and initiating Sleep cycle.

The system did not crash overnight. It's only one but encouraging data point.

If turning on Do Not Disturb when the Display in Sleeping (in Notifications) is indeed the solution, then Apple engineers need to return to the university they graduated from and retake a few computer science classes.

The hardware state - no display available because computer is sleeping - is a higher level condition that the software must honor (unless there is another condition present, i.e. Can Wake Up the Computer If The Notification is Critical).

Pseudo code for Apple engineers (simplified):

1. Trigger notification
2. Is the computer allowed to wake up? No - then queue notification
4. If the computer IS allowed to wake up because notification is critical: wake it up, activate displays, display current and queued notifications
5. Return to Sleep after specified interval

Please correct this error and I will be the first in line to give B- grade, reflecting a discount for the original defect and lack of integrated testing because the entire team has been working on Universal Control instead.

Second night and no crashes while in Sleep mode. Encouraging.

 

[toiletofsadness]

I've been suffering these same kernel panics from wake around the time I upgraded my MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) to OS 11.6.3 earlier in the month. I even took it into a repair center because I assumed the hardware was failing. They did a logic board replacement but the repaired system continued to panic after reinstalling Big Sur and restoring from my Time Machine backup.

Took it in a second time and the tech suggested I do a clean OS install and not restore from the backup. Still didn't help, but I found this thread and tried some of the suggestions here. Those were also not effective (I think I was still panicking at least once a day after trying the Do Not Disturb settings change).

The only thing that's working for me was upgrading to Monterrey. Installed that after wiping the hard drive on Sunday. No panics all week.

 

[macmeews]

I've been suffering these same kernel panics from wake around the time I upgraded my MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) to OS 11.6.3 earlier in the month. I even took it into a repair center because I assumed the hardware was failing. They did a logic board replacement but the repaired system continued to panic after reinstalling Big Sur and restoring from my Time Machine backup.

Took it in a second time and the tech suggested I do a clean OS install and not restore from the backup. Still didn't help, but I found this thread and tried some of the suggestions here. Those were also not effective (I think I was still panicking at least once a day after trying the Do Not Disturb settings change).

The only thing that's working for me was upgrading to Monterrey. Installed that after wiping the hard drive on Sunday. No panics all week.

@toiletofsadness Just checking-in... still no panics with Monterrey?

 

[toiletofsadness]

@toiletofsadness Just checking-in... still no panics with Monterrey?

Yeah, Monterrey has been stable for me. Seems 11.6.3 must have shipped a broken driver or something? 🤷‍♂️

 

[Allyance]

Having same problem on new iMac, now running Monterey 12.2.1 (up to date). Second time this AM. I have been using sleep mode and usually just move mouse to wake up. Now computer is not responding to Power Button and have to disconnect power to restart. No error messages or notifications of any problems. I will now shut down at night until I hear what the problem is.

 

[macmeews]

I believe there are many flavors of this, but specific to this thread...

• Panics during sleep mode
• "suspected bundle" = AppleIntelICLLPGraphicsFramebuffer
• After upgrade to 11.6.3

I agree Monterrey fixes it.

 

[j4lambert]

On March 20, 2023, I received this report about 1 hour or so after I put my macbook to hibernation. This is the same macbook that had caused the x86 cpu caterr detected kernel panics back in January, and the cause of those happened to be the power supply.

Sleep Wake failure in EFI

Failure code:: 0x00000000 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time: 2023-03-20 22:16:48.181 -0400
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 40
Incident Identifier: 2669D4F9-A1D5-421F-BE85-5FBF7A8FD9ED

Data Source: Stackshots
Shared Cache: 57815A20-AF2C-3B56-9006-23ABDE7962B0 slid base address 0x7ff809aaf000, slide 0x9aaf000 (System Primary)
Shared Cache: E1E267C5-FE0B-3ED9-86BE-E4F329F01460 slid base address 0x7ff817d44000, slide 0x17d44000 (DriverKit)

Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1

Time Awake Since Boot: 19s



Process: swd [340]
Shared Cache: 57815A20-AF2C-3B56-9006-23ABDE7962B0 slid base address 0x7ff809aaf000, slide 0x9aaf000 (System Primary)
Architecture: x86_64
Footprint: 456 KB
Time Since Fork: 2s
Num samples: 1 (1)

Thread 0x980 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 2432 (dyld + 25360) [0x7ff809b49310] 1
1 ??? [0x1081aa5ce] 1
1 ??? [0x1081aa362] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 50058) [0x7ff809e4838a] 1
*1 ??? [0xffffff8000385d96] 1
*1 ??? [0xffffff8000a5545b] 1
*1 ??? [0xffffff800094605b] 1
*1 ??? [0xffffff80003a8d9e] 1
*1 ??? [0xffffff80003a856a] 1
*1 ??? [0xffffff80003eb66d] (running) 1

Binary Images:
0x7ff809b43000 - 0x7ff809bd7caf dyld (1042.1) <BBA77709-6CAD-3592-AB03-09D0F7B8610E> /usr/lib/dyld
0x7ff809e3c000 - 0x7ff809e75ff7 libsystem_kernel.dylib (8792.81.3) <87FF381C-4D30-3087-BAB7-A5A53D232C00> /usr/lib/system/libsystem_kernel.dylib

I performed a hard reboot and SMC reset shortly after the error was encountered, and then I let it sleep on battery power (which temporarily fixed the issue). The following morning, I entered the terminal command to disable standby mode and am planning to turn off the computer more frequently (shut down every single night).

My mac is around 3.3 years old, and I am expected to replace it with an apple silicon mac in approximately 12 to 18 months, as macos 14 is speculated to be the last version of the system to support Intel-based apps.