System log: (SMCAMDProcessor) <compose failure [UUID]>
radianttap opened this issue · 4 comments
In the system.log, I found a series of identical entries.
Not sure what it could be:
2021-10-22 12:09:48.412029+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412030+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412032+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412034+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412035+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412066+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
2021-10-22 12:09:48.412068+0200 localhost kernel[0]: (SMCAMDProcessor) <compose failure [UUID]>
Using kexts from release 0.7
me too
opencore 0.74 realse
Interesting, I never noticed this!
But after a quick Google it seems that many kext have similar issue.
I'll do some more research on why is this log being triggered but for the mean time I think it is not a major issue as long as it doesn't cause things to crash.
Interesting, I never noticed this! But after a quick Google it seems that many kext have similar issue.
I'll do some more research on why is this log being triggered but for the mean time I think it is not a major issue as long as it doesn't cause things to crash.
Yes, I tried to block the problematic kext, but I will still report an error. It should be an opencore problem. I also submitted it to the opencore developer.
Interesting, I never noticed this! But after a quick Google it seems that many kext have similar issue.
I'll do some more research on why is this log being triggered but for the mean time I think it is not a major issue as long as it doesn't cause things to crash.
Haha, I found this log accidentally. Although it will not cause the system to crash, it will accumulate a lot of warning logs.
maybe because this?
https://eclecticlight.co/2018/08/16/working-around-a-bug-recently-introduced-into-mojave-when-signposts-point-the-wrong-way/