Skip to content
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

Bug Report: kernel.perf_event_paranoid setting #338

Closed
3 tasks done
wimb0 opened this issue Nov 7, 2023 · 3 comments
Closed
3 tasks done

Bug Report: kernel.perf_event_paranoid setting #338

wimb0 opened this issue Nov 7, 2023 · 3 comments
Labels
bug Something isn't working stale

Comments

@wimb0
Copy link

wimb0 commented Nov 7, 2023

OS Version

Debian GNU/Linux 12 (bookworm)

System Information

Linux optiplex 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux

What happened?

Supervisor was updated to allow addons to use CAP_BPF and CAP_PERFMON.
(home-assistant/supervisor#4130)
Addons that use these capabilities, such as the latest Frigate Beta, do not work correctly on Supervised installs on Debian.
This seems to be because HAOS has a default kernel.perf_event_paranoid=2 setting while Debian 11 and Debian 12 have a default of kernel.perf_event_paranoid=3.

I think that it would be great to add sysctl kernel.perf_event_paranoid=2 to the supervised installer script.

Machine Type

generic-x86-64

Installer output

No response

Relevant log output

No response

ADR

  • I have read through the ADR and have confirmed that my system is compliant with the requirements
  • I understand that if my system is found to not be compliant, my issue will be closed immediately without further investigation

Code of Conduct

@wimb0 wimb0 added the bug Something isn't working label Nov 7, 2023
Copy link

github-actions bot commented Jan 6, 2024

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 6, 2024
@wimb0
Copy link
Author

wimb0 commented Jan 11, 2024

Does not seem to be relevant anymore.

@wimb0 wimb0 closed this as completed Jan 11, 2024
@marcgarciamarti
Copy link

Does not seem to be relevant anymore.

For me change the value to 2, did indeed do the trick! I'm glad I bumped into this!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

2 participants