M1 Macbook panic after sleep in 11.2

Are you connecting your M1 MBP to any sort of dock by chance?

I'm at wit's end with this exact wake-from-sleep kernel panic. I thought it was originally related to using my M1 MBP with a CalDigit TS3+ Thunderbolt Dock, but it just happened when I reconnected my MBP to a Thunderbolt Display on one TB3 port and to an OWC USB-C travel dock on the other (2 SanDisk Ultra flash drives were connected to the dock).

I've completely reinitialized my machine via DFU restore and set it up from scratch (i.e. I did not migrate from a backup), and this is still happening. I've even filed a feedback report: FB8969561.

This has been happening since I received the M1 MBP in mid-December, Mac OS 11.1. It checks out fine using the built-in diagnostics. I haven't experienced this degree of instability since the pre-OS X days.

Once again it appears that Apple's hardware is ahead of its software. I would really appreciate it if Apple could fix these kernel panics.

Yep - it looks like the issue likely involves putting it to sleep when connected to the display.

You may want to try opening a case with Apple Support directly on the issue:

Contact - Official Apple Support

Has anyone found a solution to this yet? I have the same issue on a 2018 i9 connected to an A1407 monitor so it's NOT an M1 only related issue. Crash/restart after waking up happening randommly. I have reinstalled the OS, SMC reset, NVRAM, etc. This only STARTED after updating to Big Sur! The error log is:

I'm facing same issue after update to Big Sur (MacBook Pro Retina 13-inch Mid 2014).

I didn't connect to anything, not even power source. I just close the lid after every use, but next day when I open the lid, the screen won't light up, until I press power button... After it boot up it shows me "You shutdown your computer because of a problem" but I didn't...

It happened 3 times already... Never encounter this issue before update to Big Sur.

I don't want to come across as rude, but since the title of this thread is "M1 Macbook panic after sleep in 11.2," your kernel panics should be discussed elsewhere because the cause is likely different.

The key panic log string is:

Sleep transition timed out after 35 seconds while calling power state change callbacks. Suspected bundle: com.apple.driver.AppleThunderboltNHI.

I've seen reports of this sleep transition timeout on Intel Macs, but the 35 second specification seems unique to M1s.

By the way, I don't have high hopes for Apple Support finding a solution. I've provided sysdiag logs and other documentation, and "engineering" found some sort of sync error therein and requests that I disable all of my sync utilities (Dropbox, Google Backup & Sync, and Arq -- used by millions) and that I reproduce the problem and provide logs again!

Blaming a wake transition kernel panic on sync makes no sense whatsoever, especially when it appears closely related to the Apple Thunderbolt Display.

It's still worth filing a report, though. The more there are, the greater the chance that this problem will attract attention.

I actually posted this (and been submitting error reports as well as get it to them directly in an open case) because I don't feel like they have a handle on it yet and more people posting will let them see there is an actual issue in Big Sur. Agreed, this is definitely not a sync problem and one that ONLY appeared after I upgraded to Big Sur. They'll patch it eventually...

If you post your panic.log file here, someone here should be able to check it for obvious issues.

Yes, but without the balance of the panic.log it's impossible to diagnose this any further.

Gladly.

At first glance it looks like the Thunderbolt kext that may be having issues - do you have anything plugged into it? Docks? Displays? Mouse/Keyboard?

Yes, indeed. An Apple Thunderbolt Display. And I don't have any problems if I don't connect it to the M1 -- and the panics are intermittent.

Actually, they happen when I connect the display to the M1 after using the M1 without anything attached.

I'm already in contact with Apple Support about this.

As a workaround, you could try disabling sleep on your Mac.