mac wont wake from sleep after Catalina upgrade

I am very curious to try this out as a possible fix/workaround. I have a client who's having the same issue, and he actually uses a J5create Dock (Trigger5Core.kext is one of their extensions). The dock no longer allows more than one external monitor, and their website actually cautions against upgrading to Catalina until they have updated their own drivers.

For others having the issue, if you happen to use J5create docks, or have used them in the past, the above location of the extensions is a little off. If you plan on looking for these extensions, they'll be here instead:

Macintosh HD > Library > Extensions.

You may find Trigger5Core.kext, MCTTrigger6USB.kext, MCTTriggerGraphics.plugin, and DJTVirtualDisplayDriver.kext.

These are all part of the J5create drivers. At least for the dock series that we're running.

They may be a little different, but if they start with MCT, it's usually a good sign they're from J5create.

I'm gonna see if he'll let me try this out and I'll post my findings if he does. He's gettin' ornery and we're probably going to have to downgrade him instead, but it'd be cool if this was all it needed to make things right. He can survive without the dock for a while.

I have an 18 MBP 15 that is rebooting when sleeping after moving to Catalina. Happens EVERY TIME.

I have tried an SMC reset. Will try again.

db

Issue report content ========================================

panic(cpu 8 caller 0xffffff7f9239cad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 140 seconds

service: com.apple.logd, total successful checkins since load (63361 seconds ago): 6337, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since load (63331 seconds ago): 6313, last successful checkin: 140 seconds ago

Backtrace (CPU 8), Frame : Return Address

0xffffffa4059d3820 : 0xffffff801193f98b

0xffffffa4059d3870 : 0xffffff8011a76c15

0xffffffa4059d38b0 : 0xffffff8011a6861e

0xffffffa4059d3900 : 0xffffff80118e6a40

0xffffffa4059d3920 : 0xffffff801193f077

0xffffffa4059d3a20 : 0xffffff801193f45b

0xffffffa4059d3a70 : 0xffffff80120d2e05

0xffffffa4059d3ae0 : 0xffffff7f9239cad5

0xffffffa4059d3af0 : 0xffffff7f9239c7e6

0xffffffa4059d3b10 : 0xffffff8012067adb

0xffffffa4059d3b60 : 0xffffff8012070a73

0xffffffa4059d3ca0 : 0xffffff8011a26672

0xffffffa4059d3db0 : 0xffffff80119457f8

0xffffffa4059d3e10 : 0xffffff801191c515

0xffffffa4059d3e70 : 0xffffff8011932f75

0xffffffa4059d3f00 : 0xffffff8011a4eaf5

0xffffffa4059d3fa0 : 0xffffff80118e7226

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[58392D62-D9E8-3022-85C1-B78AC93B9167]@0xffffff7f9239b000->0xffffff7f923a3fff

BSD process name corresponding to current thread: watchdogd

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:

19A602

Kernel version:

Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64

Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160

Kernel slide: 0x0000000011600000

Kernel text base: 0xffffff8011800000

__HIB text base: 0xffffff8011700000

System model name: MacBookPro15,3 (Mac-1E7E29AD0135F9BC)

System shutdown begun: NO

System uptime in nanoseconds: 63372167333173

last loaded kext at 61105424247082: net.tunnelblick.tun 5300.3 (addr 0xffffff7f95850000, size 36864)

last unloaded kext at 311747128122: @filesystems.msdosfs 1.10 (addr 0xffffff7f95ccb000, size 61440)

loaded kexts:

net.tunnelblick.tun 5300.3

org.virtualbox.kext.VBoxNetAdp 6.0.6

org.virtualbox.kext.VBoxNetFlt 6.0.6

org.virtualbox.kext.VBoxUSB 6.0.6

com.malwarebytes.ncep.rtprotection 3.9.16

org.virtualbox.kext.VBoxDrv 6.0.6

com.displaylink.driver.DisplayLinkDriver 5.2 (48)

One work around is to go to System Preference then Energy Saver. Change your "go to sleep time" from whatever yours is set at and lower it to 1 minute. That has "fixed" my iMac and made it possible to wake it up no matter how long it goes to sleep.

I was told that a fix is coming - 10.15.1. I refused to reset the NVRAM/PRAM that is offered as a work around. This work-around changes time zones and a whole lot of other time sensitive stuff.

How in the world did this Catalina upgrade pass the testing??

I HAVE THE FIX.....so far. After spending 2 hours on a chat with Apple support this is what worked.

Go to Finder > Go > Go to folder. Type in Library/Extensions and once there, find and delete any of these that may show up there, in order.

MCTTriggerGraphics.plugin

Trigger5Core.kext

MCTTrigger6USB.kext

MCTTrigger2.kext

DJTVirtualDisplayDriver.kext

Then go to /Library/LaunchDaemons and find and delete tw.com.mct.TriggerDriver.plist

Then go to /Library/LaunchAgents and find and delete tw.com.mct.TriggerDriver.plist

Then empty trash and restart the computer.

There have been several things that have worked for some ppl, just read through this support thread and see if they’ll work. A lot of ppl have had success with removing trigger.kext files. Didn’t for me, so my temp fix has been to not let my Mac go to sleep and remove the password requirement. If apple doesn’t fix soon I’ll try erase and reinstall.

Yes...I have a J5create HDMI adaptor. After being on with Apple again for the sleep issue..we went through NRRAM reset again...we ended up reinstalling Catalina and then my monitors were not working...Called J5Create had to delete drivers and after going through 3 different driver installs my monitor finally came on. I ended up changing my energy saver to 3 hours so computer would not go to sleep. Only work around so far to keep computer from sleeping and me having to reboot and keep my monitors working. Apple said they are working on an update.

Hi, I've tried what Tony Jeffree posted, but I only deleted the files in the Extensions folder which created in 2019. I didn't disable the automatic graphics switching. I have heavy load with my computer: I run parallels desktop and opened 50+ Safari tabs, and using Photos simultaneously, and my computer can wake up correctly/instantly. (But sometimes my computer did go into safe sleep so a single click of the power button is required, but no work loss, all apps/tabs are fine.)

Hope you can solve it!

Rain

Try safe mode and have your Mac go to sleep a few ways then restart, this worked for me after trying the steps above.

chris

On settings, go to security and disable the requirement for password on waking. This assumes that you have your Mac in a secure and private place.

Just chalk it up to a bad decision to upgrade. Apple should of at least scanned the drive and sent notifications to users before destroying workflow with this upgrade. Poorly managed release.

Here is what you do....Download Mojave and do a fresh reinstall. Best 1.25 hours you will spend this week. Only way of getting back to productivity.

revisit Catalina in the spring of 2020.

After reset EFI and reinstall mojave 10.14.6 the problem happened again.

MBP going in sleep after time out (was connected to the power supply), after more or less 20 minutes appeared the "?" folder.

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9ca84b30): nvme: "Fatal error occurred.
...
...
...

Did you migrate anything from an older OS version?

EtreCheck is a simple little app to display the important details of your system configuration and allow you to copy that information to the Clipboard. It is meant to be used with Apple Support Communities to help people help you with your Mac.

http://www.etresoft.com/etrecheck

Pastebin is a good place to paste the whole report if you capture the URL while there…

https://pastebin.com/

Yes...deleted the trigger extension from my library.

Have you installed any third party drivers?