<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - kernel patched with bfs: "Failed to create cgroup cpu:/: No such file or directory"" href="https://bugs.freedesktop.org/show_bug.cgi?id=56971#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - kernel patched with bfs: "Failed to create cgroup cpu:/: No such file or directory"" href="https://bugs.freedesktop.org/show_bug.cgi?id=56971">bug 56971</a> from <a class="email" href="mailto:support@pbcomp.com.au" title="Peter Bowey <support@pbcomp.com.au>"> Peter Bowey</a> <pre>I can also confirm this problem report. The "systemd" logged error is: "systemd[1]: Failed to create cgroup cpu:/: No such file or directory" Despite the documentation at <a href="http://0pointer.de/blog/projects/cgroups-vs-cgroups.html">http://0pointer.de/blog/projects/cgroups-vs-cgroups.html</a> stating that "(B) you may disable all of the latter options while enabling "CONFIG_CGROUPS=y", if you want to run systemd on your system.", it now appear to be true that this is not enough, or has been changed in the later kernel release and/or systemd? The above logged 'error' occurs on every boot instance [with the kernel options = "CONFIG_CGROUPS=y" + "CONFIG_CGROUP_CPUACCT=y". The *tested solution* [with Linux 3.8.8+] is to compile the kernel with the additional "CONFIG_CGROUP_SCHED=y"! [no official doc's on that yet?]. Another reportor of this [same] issue was seen at "<a href="http://lists.freedesktop.org/archives/systemd-devel/2012-June/005500.html">http://lists.freedesktop.org/archives/systemd-devel/2012-June/005500.html</a>" - 10 months ago. Some updated documentation would be good. [via systemd and the kernel relationship]...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>