search

OnePlusOSS / android_kernel_oneplus_sm8350

Other
64 stars 50 forks source link

E/SchedAssist : ofbSetSfMsgTrans failed with error=Permission denied #21

Open blinoff82 opened 1 year ago

blinoff82 commented 1 year ago

OnePlus 9rt, OOS 13.1 Build number: MT2111_13.1.0.500(EX01) Kernel: 5.4.210-qgki-g7faff7b28df2

Logcat is completely occupied by thousands of identical lines: 06-12 18:04:52.843 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.851 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.868 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.876 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.884 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.892 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.900 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.909 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied 06-12 18:04:52.917 E/SchedAssist( 1549): ofbSetSfMsgTrans pid(1549) failed with error=Permission denied

OnePlusOSSAdmin commented 1 year ago

The log point would be invokded frequently in SurfaceFlinger. It seems that the process doesn't get right permission. Could you close selinux temporarily to check whether these logs would appear again?

blinoff82 commented 1 year ago

Yes, admin. I set "setenforce 0" via Termux and the error is gone. Maybe sepolicy, maybe we need to chown for sched assist nodes (if I'm not mistaken, this is your addition to CAF perf)

fanf commented 1 year ago

I confirm both the log overflow and the change when disabling selinux with setenforce 0

min38514 commented 1 year ago

I have the same problem and I don't know why this error occurs. Is it because of magisk?

blinoff82 commented 1 year ago

No.

min38514 commented 11 months ago

Only setenforce 0 is solution?

Validbit commented 7 months ago

Could this be brought to attention, or how to identify what process/app is triggering this? I had this on my non-oneplus device (RMX3311) three updates back (several months) and it may've gorten worse (as if the severe spamming wasn't bad enough)