Kernel panics, brand new MBP 13

[Cyprino]

So I took delivery of my new MBP 13" 2020 just 2 days ago, and I have kernel panic crashes when it goes to sleep. Current OS ver 10.15.5

Approx 35 seconds after the screen dims & switches off, the fan spins up to 100% for a split second and then the Macbook restarts.
Error log screenshot below...


Fixes attempted so far:
Went on chat with apple support, they suggested resetting SMC and NVRAM. No fix.
Booted in safe mode. Error didn't occur.
Restarted normally. Error occurred as described above.
Removed login items from users & groups preferences. Only one was a dropbox client. Restarted MacBook, same error after it goes to sleep.

Frustrated doesn't cut it when this is a brand new £2k machine, only dispatched from the factory a week ago... Next step is a reinstall of macOS I think, unless anyone has any bright ideas?!

 

[Taz Mangus]

Yep, there is a thread about this already. The Bridge OS crashed.

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

 

[Ben J.]

There are lots of reports about this.
The immediate fix is: Prevent sleep in system preferences!
IHTH

 

[quirozson]

2017 13" MacBook Pro W/ Touchbar

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.

 

[Taz Mangus]

Booted in safe mode. Error didn't occur.
Restarted normally. Error occurred as described above.

Interesting that the issue did not happen in Safe Mode. This tells me that maybe something you have installed is causing the issue for you. It would require some patience to figure out what you installed or migrated that could be causing the issue. One thing you could do is create a new APFS container (along with a new Volume in the new Container) and clean install Catalina to the new Volume. Boot to the clean install and use the computer without migrating any of your old user data or install any third party apps. See if the issue is the OS or something you have installed or migrated over.

 

[tommiy]

Unfortunately there are also alot of Apple kernel extensions that are not loaded in safe mode. Hence working safe mode does not necessarily mean that the problem is with a user application. For instance apple blocks apples own AppleThunderboltEDMService.kext extension which can result in thunderbolt devices not working. If that extension has an issue then safe mode would run fine. There is an inherent assumption in safe mode which is that all the core Apple extensions are bugless and hence that means its a user application. Unfortunately that assumption may not always be true.

Catalina safe mode no longer checks the filesystem by the looks. Or if it does it does not log the fact. Run disk utility prior to safe mode first I would suggest.

 

[quirozson]

... delete

 

[matram]

There are known issues with externally connected equipment via thunderbolt waking up from sleep. Try to run in normal mode but without externally connected stuff.

In the log (further down) you may find clues in the form of panic reason or kernel extension in backtrace, if you share the full log it would be easier to comment.

The log seem to say that the CPU has been externally reset. The T2 chip acts as a watchdog. The watchdog will be regularily ”kicked” by the CPU and if the CPU fails to do this, typically because the kernel is hung waiting, the watchdog is resetting the CPU. People are blaming the T2 chip / bridge os but this is working as designed, the root cause is that something is hanging the kernel, the trick is to identify what.