[systemd-bugs] [Bug 56971] New: kernel patched with bfs: "Failed to create cgroup cpu:/: No such file or directory"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=56971

          Priority: medium
            Bug ID: 56971
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: kernel patched with bfs: "Failed to create cgroup
                    cpu:/: No such file or directory"
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: minor
    Classification: Unclassified
                OS: Linux (All)
          Reporter: da_audiophile at yahoo.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 69888
  --> https://bugs.freedesktop.org/attachment.cgi?id=69888&action=edit
kernel config

As I read the cgroups vs cgroups article[1], one need only enable
"CONFIG_CGROUPS=y" to use systemd correctly.  My system running a bfs patched
kernel[2] that does in deed have that set:

$ zgrep CONFIG_CGROUPS=y /proc/config.gz
CONFIG_CGROUPS=y 

I do see a peculiar line in the journalctl and am wondering if it is a bug or
if I need to setup something else that I missed in the article.  Systemd seems
to function on my system just fine.  Thank you in advance for any insight into
this message.

Error message: "Failed to create cgroup cpu:/: No such file or directory"

I attached /proc/config.gz from the machine which is an older i686 but I get
this same message on my workstation which is an x86_64/Corei7.

[1]http://0pointer.de/blog/projects/cgroups-vs-cgroups.html
[2]http://ck.kolivas.org/patches/bfs

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20121111/a7e55ee0/attachment.html>