SO Frustrating.... This is the strong it shows me when I come back..
panic(cpu 0 caller 0xffffff8003c16487): "AppleIntelFramebuffer::setPowerState(0xffffff81b2f11000 : 0xffffff7f871a8d88, 1 -> 0) timed out after 45962 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffff820158bb40 : 0xffffff80035215cd
0xffffff820158bb90 : 0xffffff800365a3c5
0xffffff820158bbd0 : 0xffffff800364bf7e
0xffffff820158bc20 : 0xffffff80034c7a40
0xffffff820158bc40 : 0xffffff8003520c97
0xffffff820158bd40 : 0xffffff8003521087
0xffffff820158bd90 : 0xffffff8003cc2c7c
0xffffff820158be00 : 0xffffff8003c16487
0xffffff820158be50 : 0xffffff8003c15d69
0xffffff820158be60 : 0xffffff8003c2d2fe
0xffffff820158bea0 : 0xffffff8003c14b18
0xffffff820158bec0 : 0xffffff8003563545
0xffffff820158bf40 : 0xffffff8003563071
0xffffff820158bfa0 : 0xffffff80034c713e
BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
[automerge]1589333777[/automerge]
This is a known issue affecting Macs with the T2 chip. This error was introduced with 10.5.4 and hopefully there will be a fix in 10.5.5.
You can try to reset the SMC, or/and disable the power nap feature when on a/c power. The latter of course is just a workaround, but it‘s better than nothing.
I disabled power nap - lets see if that fixes it...
[automerge]1589333819[/automerge]
Is your OSX current? After one of the recent updates this issue completely stopped happening for me.
Yes it is..
[automerge]1589333870[/automerge]
It's the kernel panic error most likely. I had it after I updated the 16" to 10.15.4 by mistake - I reset the machine and 10.15.4 loaded instead of 10.15.3. Oddly enough, I only had the error if I charged the MBP while sleeping. It didn't happen otherwise. Then I noticed that if I only plugged in the charger on the right side, I could charge it while sleeping without a panic error occurring. I was sending it back anyway, so I didn't dig deep into it.
There's a huge thread that encompasses the kernel panic errors plus a few other not-so-huge threads in this sub. Those should offer some various ways to hopefully resolve the issue.
Thank you - will dig on those.
[automerge]1589333883[/automerge]
Numerous similar complaints here, so the search idea is a good one.
I should have started there.. Thanks.