-
Notifications
You must be signed in to change notification settings - Fork 5k
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
cgroups v1 no longer available in standard settings of kernel 6.12 #6396
Comments
Thanks. This could also have been expressed in the form of a pull request. |
Agreed, @pelwell, but I was unsure about your future rpi-kernel strategy vs. upstream re. cgroups, so no proposal on my side, just FYI. |
Understood. I guess I'm saying that we wouldn't consider a sensibly worded PR to be presumptuous - just efficient. |
pelwell
added a commit
to pelwell/linux
that referenced
this issue
Oct 3, 2024
As of 6.12, cgroups v1 is considered legacy, and must be enabled with CONFIG_CPUSETS_V1. Link: raspberrypi#6396 Signed-off-by: Phil Elwell <[email protected]>
See #6397. |
Thanks! |
pelwell
added a commit
that referenced
this issue
Oct 3, 2024
As of 6.12, cgroups v1 is considered legacy, and must be enabled with CONFIG_CPUSETS_V1. Link: #6396 Signed-off-by: Phil Elwell <[email protected]>
popcornmix
pushed a commit
that referenced
this issue
Oct 7, 2024
As of 6.12, cgroups v1 is considered legacy, and must be enabled with CONFIG_CPUSETS_V1. Link: #6396 Signed-off-by: Phil Elwell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Please remember that cgroups v1 is now only available via CONFIG_CPUSETS_V1, which is OFF by default in kernel 6.12 (v2 is always available).
So if you are using cpuset or alike, which still relies on cgroups v1, you need to switch it on explicitly in kernel configurations.
Steps to reproduce the behaviour
N/A
Device (s)
Other
System
All
Logs
N/A
Additional context
See also https://lore.kernel.org/lkml/[email protected]/T/
The text was updated successfully, but these errors were encountered: