EDIT: None of the changes below are relevant. System froze just now, after more than 2 days of uptime... ![Frown :( :(](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
--------
Left aside the sleep/wake issue, I've crosschecked some changes I've made to hope resolve the random freeze/KP we're having with @AnaktuvGod for our R6E motherboard when uptime reaches ~15h.
For that I have compared two system profiles I have, one for which I know I'm getting these random freeze/KP, and the second one which I'm still using and currently have a decent uptime with no freeze/KP. Hopefully that can give us some clues about what could be wrong with our config.
Before (KP/SystemFreeze occurring after ~15h of uptime):
- System using APFS filesystem (small noticeable lags, slow boot, and other misc issues when the system is running)
- System was upgraded to 10.13.3 (17D2047) from a manual upgrade procedure from 10.13.2 (17C88)
- Clover r4380
- Using OsxAptioFix3Drv-64.efi (instead of AptioMemoryFix.efi) which can be found in drivers64UEFI folder
- Compiled FakeSMC's interferenc patched version from
https://github.com/interferenc/HWSensors
- Placed the following FakeSMC kexts in "Other" Clover folder:
ACPISensors.kext
CPUSensors.kext
FakeSMC.kext
GPUSensors.kext
LPCSensors.kext
- SSD Trim Enabler patch enabled
After (current uptime: 1d 16h and still running):
- System using HFS+ filesystem (resolved APFS related issues, see above)
- System was upgraded to 10.13.3 (17D2047) from a fresh 10.3.2 (17C2120) install and used migration assistant to restore data from previous APFS system
- Clover r4392, as a consequence of the upgrade from r4380 the following drivers64UEFI files have been upgraded:
AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleUITheme-64.efi
CsmVideoDxe-64.efi
DataHubDxe-64.efi
FirmwareVolume-64.efi
FSInject-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi
- Compiled latest AptioMemoryFix.efi (instead of OsxAptioFix3Drv-64.efi) and placed it in Clover's drivers64UEFI folder
- Compiled and Patched (to have per Core multiplier and frequency) the latest FakeSMC from
https://github.com/kozlek/HWSensors
- Placed the following FakeSMC kexts in "Other" Clover folder:
(Removed ACPISensors.kext from Clover's Other folder)
CPUSensors.kext
FakeSMC.kext
GPUSensors.kext
LPCSensors.kext
- DSDT replacements switched to disabled (were previously enabled):
SL05 -> GFX0 from KGP (disabled) --> disabled because not found on R6E
_OSI -> XOSI from KGP (disabled) --> Should in fact be enabled, cf
#4654
H_EC -> EC__ from KGP (disabled) --> disabled because not found on R6E
GBE1 -> ETH0 from KGP (disabled) --> disabled because not relevant
RP05 -> ETH1 from Thireus (disabled) --> disabled because not relevant
IDER -> MEID from KGP (disabled) --> found in DSDT.aml, probably relevant to enable this
SLOC -> ARPT from KGP (disabled) --> disabled because not found on R6E
SL01 -> UPSB from KGP (disabled) --> found in DSDT.aml, probably relevant to enable this
_DSM -> XDSM from KGP (disabled) --> Should in fact be enabled, cf
#4654
- SSD Trim Enabler patch disabled
-------------------
Above are all the changes I've made that seem to have resolved the random KP issue. Now
@AnaktuvGod is getting the same random KPs, and from what we know about his config we can eliminate some of the above changes (i.e. he did a fresh install from 10.3.2 (17C2120), used HFS+, doesn't have any DSDT replacements, doesn't use ACPISensors.kext). So from the list of changes that could have contributed to resolving the issue we can mark the following as potential contributing factors to check:
- Clover r4392
- Compiled latest AptioMemoryFix.efi (instead of OsxAptioFix3Drv-64.efi) and placed it in Clover's drivers64UEFI folder
- Compiled and Patched (to have per Core multiplier and frequency) the latest FakeSMC from https://github.com/kozlek/HWSensors
- SSD Trim Enabler patch disabled
I believe what should be checked first is to upgrade CLover to r4392. I don't think SSD Trim Enabler is relevant. The other 2 changes remain to be validated.
Hope this helps. I'm still currently monitoring my uptime. It's not impossible that within a few hours I get a system freeze which would prove that none of the above changes solved anything. But so far, I've never been able to run my system for more than 24h, so I'm confident.
EDIT: Added more accurate info to DSDT changes.