-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/sys/kernel/debug/sched/latency_ns: Permission denied Error when starting systemd unit #1
Comments
Most likely. I think there should be an entry in journald when it happens. |
I've installed SELinux Troubleshooter and yeah, my guess was correct.
Don't know is it something actionable here though. |
I wonder if there is a Does not look like SELinux allow that. |
It works but only for until reboot. I need to look deeper in to this issue. I need to find a way to ship selinux policy with package. |
Ok. I think I found a solution. The script should be placed in to the |
I published version 1.2.0 with the fix. (moving script to @soal would you mind giving it a test. (also remove previous workarounds beforehand) I tested in a VM. |
1.2 fixed the issue, many thanks! |
Weird, I'm still having the same issue here, even with 1.2.0. Are there any extra steps I need to do after installing it? |
I've tested on Fedora 35. Removed SELinux module with workaround, rebooted to check that systemd unit from 1.1.1 fails, installed 1.2, rebooted again and everything works fine. No extra steps.... |
Weird, here I just installed and enabled the systemd service and both before and after rebooting it fails only when setting the latency. |
What do you mean? What is your journalctl output? Did you apply any fixes beforehand? |
Pretty much this:
Nope, I was just following the issue waiting for an official fix before installing it on my system. |
Do you get any lines about SELinux? What is your Fedora version? Can you do |
Pretty much stock Fedora 35, and at least nothing related shows up in journalctl.
system_u:object_r:bin_t:s0 /usr/sbin/set-cfs-zen-tweaks.bash |
Try Also try running the script directly with |
|
Try running the script directly with sudo and see if you get the error. I am going to do fresh install of fedora in VM to see if there will be error. |
Same thing, unfortunately. |
When there is some issue with This is what I have:
|
Looks like it's pretty much the same here, unless I'm missing something:
|
Can you read/write manually to those values? |
Apparently not, getting the same "Operation not permitted" error when trying to do so. |
Then there is definitely something wrong/unusual with your setup. Sorry I can't help more than that. Maybe you have a custom kernel installed that uses some other scheduler... (fedora silverblue maybe?) |
Fedora 35, kernel
5.14.16-301.fc35.x86_64
,cfs-zen-tweaks
installed via RPM from release page.Interestingly, when I execute
/usr/lib/cfs-zen-tweaks/script.sh
or setting latency manually (echo 16000000 | tee /sys/kernel/debug/sched/latency_ns
), no errors occured.Wild guess: something selinux-related?
The text was updated successfully, but these errors were encountered: