MacOS Catalina 10.15.3 - crash panic(cpu 0 caller 0xffffff801faa2d1c): Sleep transition timed out after 180 seconds while calling power state change

[pingchp]

Had the same Problem an solved it by not using HDMI adaptor any longer to connect to the external monitor. Instead I use thunderbolt adaptor.

in many cases the users don’t post their config of used accessories, so it is hard to find the source causing this...

I'm using direct cable USB-C to DisplayPort. Problem still persists.

 

[sclowbird]

I tried with DisplayPort -> USB-C and HDMI -> USB-C Adapter. I also tried it with two different external displays. Same behavior.

 

[Graphically]

Same here. Connections aren't the issue.

 

[vondy]

Figured I'd share my experience with this. Looked back at my install and crash logs. 10.15.5 was installed May 30 and my first Panic Log occurred June 1 and everyday since.

I have not determined if it only happens when connected to my Caldigit TS3 hub yet or if on battery power. The hub is connected to:

Display via Display Port
2 USB 3 External Drives
Apple Keyboard

Computer:
MacBook Pro (16-inch, 2019)
2.6 GHz 6-Core Intel Core i7
32 GB 2667 MHz DDR4
AMD Radeon Pro 5300M

 

[xgman]

anyone try 10/15/6 beta yet?

 

[DavidW101]

Ordered an Apple Thunderbolt to HDMI adapter to connect the Dell monitor instead of the non-Apple docking station, Left everything connected with the lid closed last night and this morning it has woken up perfectly. That seems to have solved the problem for me.

 

[Graphically]

Hmmmm. Just crashed in mirror mode for the first time. Only difference, is an installation of Little Snitch, which I had initially uninstalled as it appeared high in the crash logs.

 

[pingchp]

Installed Amphetamine to keep your mac awake (only when with power). No more crash. Problem solved.

 

[Graphically]

Hasn't worked for me.

 

[Cyprino]

I have a brand new off-the-shelf i5/16GB/512GB 13-inch MacBook Pro and get the same sleep kernel panics as discussed here.

No external devices attached, no third party apps installed, occurs whether plugged in or on battery. Updating to 10.15.5 did nothing. Tried turning off power nap and power saving options. Still no joy.

Same here but config-to-order with i7. Had 10.15.5 installed out of the box. Mine crashes every time it goes to sleep... Not happy so far...

 

[tommiy]

There is a user thread here that suggests that the KP due to IOGraphicsFamily and external monitors could be worked around by trying different resolutions. Look for Nelsons reply but the statement:

'Changing the “Resolution: Scaled” setting for both of my monitors from “2560 x 1440” to “3008 x 1692” seems to have fixed my sleep/wake problems with a closed lid.'

 

[blithe35]

I am getting this issue as well. Have you guys find any working solution?

 

[tommiy]

There are some reports on the apple community regarding needing to purchase new monitors and that fixes the issue. This solution is not for every one obviously. Other than that not aware of anything that will address the mess other than never having upgraded to Catalina to start with. If you have tried Catalina you can never return to stability because of the firmware changes accoprding to the Apple community thread. Peoples experiences of working hadware and after upgrade KP and no monitors and then downgrading to be met with the same problems. I suspected this back at 10.15.1 when my issues with external monitors started by testing Catalina on a external SSD. From that date I have ceased doing upgrades as there is no way to roll the firmware changes back.

 

[vondy]

After several days I agree it's monitor related. Only time it does it is when my monitor is plugged in. I've even tested with nothing but the monitor plugged in and it occurs. Every other configuration is fine.

Apple needs to fix with an update soon.

 

[tommiy]

Reports in other threads that there is no difference with 10.15.6 beta 2. I still think its going to be 10.16 some thing maybe before this gets sorted.

 

[kave]

It happened today with my 16" left alone with just power and ethernet adapter plugged in. Dead after 1 hour.

 

[quirozson]

Will keep an eye on it, but I was having "Sleep transition timed out after 180 seconds while calling power state change" problems and found a fix that has made my computer more stable so far...

First what I tried before I tried this:

1. PRAM Reset
2. SMC Reset
3. Recover Mode Disk Utility Repair
4. Recovery Mode Re-Install of OSX

Finally went into recovery mode and used Disk Utility to completely erase HD. Reinstalled OS X. Logged in as a new computer. Used time machine to install backup. Had a bunch of permissions and iCloud keychain problems, so this final step may not be necessary - Created new Admin user to use as my new personal account. Migrated all important files and data into that account. Removed my old user account (kept old account folder for backup). So far computer has not restarted. Will post back if the bug reappears.

 

[kave]

I updated to 10.15.6B2 since a few days. No kernel panic when sleeping anymore.

 

[rvinci]

Same Here. Using Catalina 10.15.5. on a MBPr mid-2012.
Message is "panic(cpu 0 caller 0xffffff7f8aa33677): pmLock: waited too long, held by 3@0xffffff800744c7e9"

 

[ZHANG Liang]

I thought it might be the hardware problem of my MacBook Pro Mid 2012. But it seems not. I connected my MacBook Pro Mid 2012 to the external Apple Thunderbolt Display (not mirror) and three external hard drivers with the thunderbolt2 port. The crash report is as follows:

panic(cpu 0 caller 0xffffff802c29167c): Wake transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOThunderboltFamily. Thread 0x193c4.
Failure code:: 0x00000004 00000027

In order to save my poor computer, I unchecked the following options:

1. Automatic graphics switching
2. Put hard disks to sleep when possible (both Battery and Power Adapter)
3. Wake for network access (both Battery and Power Adapter)
4. Enable Power Nap while plugged into a power adapter (both Battery and Power Adapter)
5. Besides, I also unchecked all the schedule settings in Energy Saver.

But this machine still crashed, just in front of me, when I was reading this post.

The MacBook Pro that I'm using:

MacBook Pro (Retina, Mid 2012)
15.4-inch (2880 x 1800)
macOS Catalina 10.15.5
2.6 GHz Quad-Core Intel Core i7
8 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 1 GB
Intel HD Graphics 4000 1536 MB

Apple Thunderbolt Display connected:

27-inch (2560 x 1440)

[automerge]1592280273[/automerge]

I updated to 10.15.6B2 since a few days. No kernel panic when sleeping anymore.

Hope this fix will work.

 

[ZHANG Liang]

I just unplugged one of the thunderbolt2 adapters that connected to my second MacBook Pro. And by now everything looks fine. I will check this out again tonight.

 

[Alexander5673]

BTW, I also see one or two other USB related panics like:
panic(cpu 1 caller 0xffffff7f9a752399): "DSB0(iMac19,1): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.100.21/IOPCIBridge.cpp:1398

Anybody else, too?

 

[ZHANG Liang]

Well, it's confirmed. everything is fine, when I unplugged one of the thunderbolt2 adapter that connected two MacBook Pro.

 

[yeah3x]

I thought this bug was fixed on my Macbook Pro 16 inch (ordered in May) but this last week it's happening every time I shut my computer. Reporting every one to Apple hoping we can get a fix finally.

Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x502c.

 

[Chris.J]

I've had issues since upgrading from a 2015 MBP to the 2019 16". I'm getting all sorts of weird sleep wake problems as follows:

- Kernel panics on wake
- Losing 40% battery when lid closed overnight
- Laptop getting warm when closed, as a result of the above
- Built-in keyboard & trackpad not working after wake
- Display not turning on when lid opened

I've been experimenting with pmset settings to find a fix and I think I found something that works, which might be worth a try for you guys. Set tcpkeepalive, proximitywake and ttyskeepawake all to 0 (sudo pmset -a ___ 0).

2 days now and no issues. Of course, it could just be a coincidence, but I'm hoping this is a temporary fix until Apple release 10.15.6.