Instant wake up after sleep

zk2004mb

New member
Original poster
Jun 7, 2020
19
3
3
Here is the result from wake up log:

2021-01-23 04:12:52.869925-0500 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11


2021-01-23 04:12:52.869927-0500 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11


Did anyone know what's the reason behind it?

Thanks!
 

baronerosso

Donator
Donator
Sep 29, 2020
47
5
8
Italy
I have the same problem.
Sleep was OK only at first reboot after BigSur installation, and next .. instant wake
 

AudioGod

Guru
Guru
Nov 7, 2020
325
143
43
London U.K.
Here is the result from wake up log:

2021-01-23 04:12:52.869925-0500 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11


2021-01-23 04:12:52.869927-0500 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11


Did anyone know what's the reason behind it?

Thanks!
Hi,
If either of you are using a AIO like a Corsair H100i etc etc etc that needs a usb internal header connection then you need to use this patch to fix sleep properly.


Or you can just disconnect the Internal USB Connection to the AIO to test it out before you apply the patch.
 

zk2004mb

New member
Original poster
Jun 7, 2020
19
3
3
Hi,
If either of you are using a AIO like a Corsair H100i etc etc etc that needs a usb internal header connection then you need to use this patch to fix sleep properly.


Or you can just disconnect the Internal USB Connection to the AIO to test it out before you apply the patch.
It didn't seem to be the same problem as stated in the fix.
I checked the cause of wake up and it did not match what's in the guidance.


2021-01-23 12:49:20 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 45 secs


2021-01-23 12:50:05 -0500 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 23 secs


2021-01-23 12:50:28 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 46 secs


2021-01-23 12:51:14 -0500 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 61 secs


2021-01-23 12:52:15 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 4 secs


2021-01-23 12:52:19 -0500 Wake DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)

I'm using a NZXT internal fan hub though. I guess it might cause the problem but I do have USB map to cover the internal usb2.0 port.
 

AudioGod

Guru
Guru
Nov 7, 2020
325
143
43
London U.K.
It didn't seem to be the same problem as stated in the fix.
I checked the cause of wake up and it did not match what's in the guidance.


2021-01-23 12:49:20 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 45 secs


2021-01-23 12:50:05 -0500 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 23 secs


2021-01-23 12:50:28 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 46 secs


2021-01-23 12:51:14 -0500 Sleep Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 61 secs


2021-01-23 12:52:15 -0500 DarkWake DarkWake from Normal Sleep [CDN] : due to GPP2 GPP3 GPP4 GPP5 GPP6 GPP7 GPP9 X162 GPPA GPPB GPPC GPPD GPPE GPPF GP10 GP11/ Using AC (Charge:0%) 4 secs


2021-01-23 12:52:19 -0500 Wake DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)

I'm using a NZXT internal fan hub though. I guess it might cause the problem but I do have USB map to cover the internal usb2.0 port.
Try disconnecting it and see if it makes a difference, it takes two seconds too try buddy.
If your using T919 combo card then they break sleep under big sur too.
I don’t know if you do or don’t have one, I’m just throwing it out there for you.
 

zk2004mb

New member
Original poster
Jun 7, 2020
19
3
3
Try disconnecting it and see if it makes a difference, it takes two seconds too try buddy.
If your using T919 combo card then they break sleep under big sur too.
I don’t know if you do or don’t have one, I’m just throwing it out there for you.
Really appreciate your help! I'm gonna try it tomorrow. It's a SFF build with custom loop. So open the case and remove the hub might be a little bit harder than you expected lollll. I actually hid the hub behind some fittings for cable management.
 

baronerosso

Donator
Donator
Sep 29, 2020
47
5
8
Italy
I have fenvi t919 and I did the test.

With Fenvi t919: instant wake up after sleep.
With Fenvi 1200: instant wake up after sleep.
Removing all with only video card in PCI: instant wake up after sleep.
 

AudioGod

Guru
Guru
Nov 7, 2020
325
143
43
London U.K.
Really appreciate your help! I'm gonna try it tomorrow. It's a SFF build with custom loop. So open the case and remove the hub might be a little bit harder than you expected lollll. I actually hid the hub behind some fittings for cable management.
As I’m sure you already know and as Annoying as it is sometimes the best way to fault find is to strip back to bare bones and test from there just so you can write off any other devices being part of the problem.