Still having a (at least one of the multiple different) kernel panic during sleep:
panic(cpu 0 caller 0xffffff801e29169c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2754.
Ever since moving to a brand new 16" MBP there isn't a day that passes wihout me being welcomed by the crash report dialog…
I managed to eliminate (or at least majorly reduce) kernel panics by disabling Power Nap. I've since re-enabled it to see if this is any more stable.
Kind of a joke really, this isn't a brand new model, nor is it using any cutting edge components. I thought we'd worked out sleep mode a long time ago.
Oh damnit, damnit. I've been having those on 10.15.4 too, was really hoping they'd fixed it on this one. It's really profoundly upsetting to spend $3,500 on a brand new computer by the most reliable major manufacturer in the industry and still have daily damn kernel panics.
I have had too many bad experiences with Lenovo business class desktops and servers to hope that one product line from them is somehow exempt from reliability issues.
Also a product long past it’s glory days. Ditched my less than year old X1 Carbon to get a 16” MacBook Pro because it was randomly dying while purporting to have 25% battery left.
I have the same. Every day. I've done a lot of searching, and some people think that certain external monitors might be "the issue"--which I use. It didn't seem to be an issue before Catalina though.
Hmm, same for me perhaps. New MBP 16 and Catalina connected to a external monitor via USB-C (a HP Z27 4K UHD).
If I leave it to sleep for a long duration, then it panics when waking from sleep and just black screens for a good few minutes, then turns on the fans full blast for like 2 seconds and reboots.
I've taken to just shutting down completely when finishing work and not letting sleep.
I have the same monitor and connect over usb-c with a 2018 13' MBP running 10.15.4. I have not experienced any such issue, even though Catalina broke several other things.
In my case, if I use the usb-c port of the monitor to connect the ethernet adaptor, it works for a few minutes and then drops all the packets. This was never an issue before Catalina or with a windows machine.
Another weird issue that I have with this monitor and Mac OS (not only Catalina) is related to the Microsoft sculpt ergonomic keyboard receiver, when plugged to one of the USB ports of the monitor. If I unplug a the MBP and connect a windows machine to the monitor, when I connect the MBP again, there is a >50% chance the receiver will not be recognised. Plugging and unplugging does not work. I have to do a restart of the MBP.
The above make it very annoying when I have to switch laptops. Sometimes I have to work on 3 machines at the same time, which by coincidence run 3 different operating systems (Win 10, ubuntu and mac). The reason I got this monitor is mostly for the build in hub. If it worked properly, I would just plug everything on the monitor and I would only need to plug the usb-C to the laptop and be ready to go.
Sometimes it does work and I feel like I am in the future, using a dock that can support every device, with just one universal cable. Now I often have to plug and plug things directly at the laptops.
One last thing for people who might consider a similar set up. Due to USB limitations, if you plug any storage device on the monitor and the monitor is at 4k@60Hz, you are limited to USB2 speeds.
Same here on my late 2013 15". Other than a few weird moments back in the 10.9 days when I tried installing Xcode on an external drive, it's run like a champ, upgrades and all. I was nervous about putting Mojave on it, but it's run surprisingly well, albeit a bit slow, although that's expected at this stage of the game.
The same can't be said for the machine it replaced, which began life on 10.5 but was brought to its knees by the combination of an 8600M GT and the 10.7 upgrade.
Right now, I'm waiting until things settle down - because COVID 19 - before pulling the trigger on a 13" Pro.
Read a user somewhere reporting that leaving his iPhone plugged into his Mac caused this problem to occur almost daily. After charging it with a wall charger, and not having it plugged in, the problem went away. After resetting PRAM and SMC too. Hope the issue gets resolved for you someday!
Glad to hear I'm not the only one. I've started getting these in the last week. It coincided with a screen replacement but sounds like that might be a coincidence based on your report.
For anyone else having this issue, the fix for most people seems to be disabling Power Nap[1], which is enabled by default when you're on AC power. Can confirm that this worked for me personally. Disappointed to see no mention of fixing this bug in these release notes, however.
FWIW I've ran into this too with a new 16" MBP and what largely fixed it for me (happened once in two weeks vs. every time the computer went to sleep) was to disable "Power Nap while plugged into a power adaptor" in the "Energy Saver" system preferences.
(I'm aware that this might not be applicable to your situation, since you might not even use a power adaptor when the crashes happen, just wanted to point this out in case it helps someone else)
Are you using an external TB3 dock? That's what's causing KPs for me. If the MBP goes to sleep, it goes into endless reboot cycles. Currently keeping it running 24/7.
panic(cpu 0 caller 0xffffff801e29169c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2754.
Ever since moving to a brand new 16" MBP there isn't a day that passes wihout me being welcomed by the crash report dialog…