[Solved] MacOS 10.13.3 update broke sleep

[qubiczek]

Hey, was wondering if anyone encountered the same issue.
Was running 10.13.2 that was fully functional, sleep was working flawlessly. When going to sleep the drives were turned off as did the display, all fans were stopped. Unfortunately after upgrading to 10.13.3 sleep stopped working. When I try to put my hack to sleep, it turns off the display and hangs, all of the fans keep turning. I updated clover to 4392, changed
CFG_FB_LIMIT to 5 (it became 0 after the update), no joy.
Here are the last few lines of the system.log:

Jan 25 16:00:35 MacName com.apple.xpc.launchd[1] (com.apple.mdworker.single.06000000-0000-0000-0000-000000000000): Service only ran for 6 seconds. Pushing respa
wn out by 4 seconds.
Jan 25 16:00:35 MacName com.apple.xpc.launchd[1] (com.apple.mdworker.single.01000000-0000-0000-0000-000000000000): Service only ran for 4 seconds. Pushing respa
wn out by 6 seconds.
Jan 25 16:00:35 MacName com.apple.xpc.launchd[1] (com.apple.mdworker.single.07000000-0000-0000-0000-000000000000): Service only ran for 3 seconds. Pushing respa
wn out by 7 seconds.
Jan 25 16:00:36 MacName com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit
Jan 25 16:00:47 --- last message repeated 1 time ---
Jan 25 16:00:47 MacName gamed[556]: BUG in libdispatch client: kevent[mach_recv] monitored resource vanished before the source cancel handler was invoked
——————————
Jan 25 18:47:41 localhost bootlog[0]: BOOT_TIME 1516902461 0

Did anyone of you notice similar issue after the update? Any ideas on how to fix it?
Cheers!

 

[qubiczek]

For those of you interested - I was on the right track, the CFG_FB_LIMIT change was the solution, sleep started to work after I reset/repaired permissions on the KEXT caches.

 

[zedoc]

Same problem for me, but i don't have any AMD card, i have GTX660Ti.
should i change the CFG_FB_LIMIT anyway?

EDIT: SOLVED
cupsd was preventing sleep, reset printer solved the problem