* Why would cpu cgroup get disabled by the kernel?
@ 2016-09-02 9:12 Sverd Johnsen
[not found] ` <CAGmahrS4P7kS6_5MOhHA=ge6mcq0C2f85iN9S3z5dgi+qsEh9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 6+ messages in thread
From: Sverd Johnsen @ 2016-09-02 9:12 UTC (permalink / raw)
To: cgroups-u79uwXL29TY76Z2rM5mHXA
Hi! I'am on 4.4.19 (arm) and seem to have all requirements for CPU
cgroups build into the kernel:
# zgrep -P "CGROUP|GROUP|FAIR" /proc/config.gz
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_FREEZER is not set
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_PERF is not set
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
# CONFIG_SCHED_AUTOGROUP is not set
CONFIG_CFQ_GROUP_IOSCHED=y
# CONFIG_NET_CLS_CGROUP is not set
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
Other cgroups also work:
# findmnt -a
TARGET SOURCE
FSTYPE OPTIONS
|-/sys sysfs
sysfs rw,nosuid,nodev,noexec,relatime
| |-/sys/kernel/security securityfs
securityfs rw,nosuid,nodev,noexec,relatime
| |-/sys/fs/cgroup tmpfs
tmpfs ro,nosuid,nodev,noexec,mode=755
| | |-/sys/fs/cgroup/systemd cgroup
cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
| | |-/sys/fs/cgroup/devices cgroup
cgroup rw,nosuid,nodev,noexec,relatime,devices
| | |-/sys/fs/cgroup/blkio cgroup
cgroup rw,nosuid,nodev,noexec,relatime,blkio
| | |-/sys/fs/cgroup/pids cgroup
cgroup rw,nosuid,nodev,noexec,relatime,pids
| | `-/sys/fs/cgroup/cpuacct cgroup
cgroup rw,nosuid,nodev,noexec,relatime,cpuacct
However I get this:
# dmesg | egrep "cgroup|control group"
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.001242] Disabling cpu control group subsystem
[ 0.001263] Initializing cgroup subsys io
[ 0.001289] Initializing cgroup subsys devices
[ 0.001304] Initializing cgroup subsys pids
# column -t /proc/cgroups
#subsys_name hierarchy num_cgroups enabled
cpu 0 1 0
cpuacct 5 59 1
blkio 3 9 1
devices 2 56 1
pids 4 64 1
Why? really weird. I control the boot process (systemd 231)
and nothing there apparently disables it. When I try to mount cpu
cgroup manually I just
get ENOENT
^ permalink raw reply [flat|nested] 6+ messages in thread[parent not found: <CAGmahrS4P7kS6_5MOhHA=ge6mcq0C2f85iN9S3z5dgi+qsEh9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* RE: Why would cpu cgroup get disabled by the kernel? [not found] ` <CAGmahrS4P7kS6_5MOhHA=ge6mcq0C2f85iN9S3z5dgi+qsEh9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2016-09-02 9:44 ` Rosen, Rami [not found] ` <9B0331B6EBBD0E4684FBFAEDA55776F92CE0E032-cNwSTNrqBuVnIh7sxsoRyrfspsVTdybXVpNB7YpNyf8@public.gmane.org> 2016-09-02 9:54 ` Zefan Li 1 sibling, 1 reply; 6+ messages in thread From: Rosen, Rami @ 2016-09-02 9:44 UTC (permalink / raw) To: Sverd Johnsen, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Hi, Sverd, Could it be that you are using the cgroup_nov1=all kernel option (or include cpu in cgroup_nov1=... bitmask)? What does cat /proc/cmdline show ? Regards, Rami Rosen -----Original Message----- From: cgroups-owner@vger.kernel.org [mailto:cgroups-owner@vger.kernel.org] On Behalf Of Sverd Johnsen Sent: Friday, September 02, 2016 12:13 To: cgroups@vger.kernel.org Subject: Why would cpu cgroup get disabled by the kernel? Hi! I'am on 4.4.19 (arm) and seem to have all requirements for CPU cgroups build into the kernel: # zgrep -P "CGROUP|GROUP|FAIR" /proc/config.gz CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set # CONFIG_CGROUP_FREEZER is not set CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_DEVICE=y CONFIG_CGROUP_CPUACCT=y # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set # CONFIG_SCHED_AUTOGROUP is not set CONFIG_CFQ_GROUP_IOSCHED=y # CONFIG_NET_CLS_CGROUP is not set # CONFIG_CGROUP_NET_PRIO is not set # CONFIG_CGROUP_NET_CLASSID is not set # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_GOV_FAIR_SHARE is not set Other cgroups also work: # findmnt -a TARGET SOURCE FSTYPE OPTIONS |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | `-/sys/fs/cgroup/cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuacct However I get this: # dmesg | egrep "cgroup|control group" [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.001242] Disabling cpu control group subsystem [ 0.001263] Initializing cgroup subsys io [ 0.001289] Initializing cgroup subsys devices [ 0.001304] Initializing cgroup subsys pids # column -t /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpu 0 1 0 cpuacct 5 59 1 blkio 3 9 1 devices 2 56 1 pids 4 64 1 Why? really weird. I control the boot process (systemd 231) and nothing there apparently disables it. When I try to mount cpu cgroup manually I just get ENOENT -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <9B0331B6EBBD0E4684FBFAEDA55776F92CE0E032-cNwSTNrqBuVnIh7sxsoRyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>]
* Re: Why would cpu cgroup get disabled by the kernel? [not found] ` <9B0331B6EBBD0E4684FBFAEDA55776F92CE0E032-cNwSTNrqBuVnIh7sxsoRyrfspsVTdybXVpNB7YpNyf8@public.gmane.org> @ 2016-09-02 9:59 ` Zefan Li [not found] ` <57C94D7E.4090204-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> 0 siblings, 1 reply; 6+ messages in thread From: Zefan Li @ 2016-09-02 9:59 UTC (permalink / raw) To: Rosen, Rami, Sverd Johnsen, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On 2016/9/2 17:44, Rosen, Rami wrote: > Hi, Sverd, > > Could it be that you are using the cgroup_nov1=all kernel option (or include cpu in cgroup_nov1=... bitmask)? > What does cat /proc/cmdline show ? > If the kernel is valinna 4.4.19, there's no cgroup_nov1 option, and I think the only possibility is cgroup_disable=cpu kernel option. > Regards, > Rami Rosen > > > -----Original Message----- > From: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] On Behalf Of Sverd Johnsen > Sent: Friday, September 02, 2016 12:13 > To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > Subject: Why would cpu cgroup get disabled by the kernel? > > Hi! I'am on 4.4.19 (arm) and seem to have all requirements for CPU cgroups build into the kernel: > > # zgrep -P "CGROUP|GROUP|FAIR" /proc/config.gz CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set # CONFIG_CGROUP_FREEZER is not set CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_DEVICE=y CONFIG_CGROUP_CPUACCT=y # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set # CONFIG_SCHED_AUTOGROUP is not set CONFIG_CFQ_GROUP_IOSCHED=y # CONFIG_NET_CLS_CGROUP is not set # CONFIG_CGROUP_NET_PRIO is not set # CONFIG_CGROUP_NET_CLASSID is not set # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_GOV_FAIR_SHARE is not set > > Other cgroups also work: > > # findmnt -a > TARGET SOURCE > FSTYPE OPTIONS > |-/sys sysfs > sysfs rw,nosuid,nodev,noexec,relatime > | |-/sys/kernel/security securityfs > securityfs rw,nosuid,nodev,noexec,relatime > | |-/sys/fs/cgroup tmpfs > tmpfs ro,nosuid,nodev,noexec,mode=755 > | | |-/sys/fs/cgroup/systemd cgroup > cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd > | | |-/sys/fs/cgroup/devices cgroup > cgroup rw,nosuid,nodev,noexec,relatime,devices > | | |-/sys/fs/cgroup/blkio cgroup > cgroup rw,nosuid,nodev,noexec,relatime,blkio > | | |-/sys/fs/cgroup/pids cgroup > cgroup rw,nosuid,nodev,noexec,relatime,pids > | | `-/sys/fs/cgroup/cpuacct cgroup > cgroup rw,nosuid,nodev,noexec,relatime,cpuacct > > However I get this: > > # dmesg | egrep "cgroup|control group" > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Initializing cgroup subsys cpuacct > [ 0.001242] Disabling cpu control group subsystem > [ 0.001263] Initializing cgroup subsys io > [ 0.001289] Initializing cgroup subsys devices > [ 0.001304] Initializing cgroup subsys pids > > # column -t /proc/cgroups > #subsys_name hierarchy num_cgroups enabled > cpu 0 1 0 > cpuacct 5 59 1 > blkio 3 9 1 > devices 2 56 1 > pids 4 64 1 > > Why? really weird. I control the boot process (systemd 231) and nothing there apparently disables it. When I try to mount cpu cgroup manually I just get ENOENT > -- > To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html > \x13��칻\x1c�&�~�&�\x18��+-��ݶ\x17��w��˛���m� ����)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥ > ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <57C94D7E.4090204-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>]
* Re: Why would cpu cgroup get disabled by the kernel? [not found] ` <57C94D7E.4090204-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> @ 2016-09-02 11:49 ` Sverd Johnsen [not found] ` <CAGmahrTwRC3cr72S2sJC9pzCxuGmYeWHe-iprz9D20DDDvU7MA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 6+ messages in thread From: Sverd Johnsen @ 2016-09-02 11:49 UTC (permalink / raw) To: Zefan Li; +Cc: Rosen, Rami, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org /proc/cmdline and CONFIG_CMDLINE are just the standard options (root console etc.), nothing regarging cgroups. cgroup_disable does not get used anywhere..dont you think I would have thought of that. On 2 September 2016 at 11:59, Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> wrote: > On 2016/9/2 17:44, Rosen, Rami wrote: >> Hi, Sverd, >> >> Could it be that you are using the cgroup_nov1=all kernel option (or include cpu in cgroup_nov1=... bitmask)? >> What does cat /proc/cmdline show ? >> > > If the kernel is valinna 4.4.19, there's no cgroup_nov1 option, and I think the only > possibility is cgroup_disable=cpu kernel option. > >> Regards, >> Rami Rosen >> >> >> -----Original Message----- >> From: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:cgroups-owner-u79uwXL29TaqPxH82wqD4g@public.gmane.orgg] On Behalf Of Sverd Johnsen >> Sent: Friday, September 02, 2016 12:13 >> To: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org >> Subject: Why would cpu cgroup get disabled by the kernel? >> >> Hi! I'am on 4.4.19 (arm) and seem to have all requirements for CPU cgroups build into the kernel: >> >> # zgrep -P "CGROUP|GROUP|FAIR" /proc/config.gz CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set # CONFIG_CGROUP_FREEZER is not set CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_DEVICE=y CONFIG_CGROUP_CPUACCT=y # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set # CONFIG_SCHED_AUTOGROUP is not set CONFIG_CFQ_GROUP_IOSCHED=y # CONFIG_NET_CLS_CGROUP is not set # CONFIG_CGROUP_NET_PRIO is not set # CONFIG_CGROUP_NET_CLASSID is not set # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set # CONFIG_THERMAL_GOV_FAIR_SHARE is not set >> >> Other cgroups also work: >> >> # findmnt -a >> TARGET SOURCE >> FSTYPE OPTIONS >> |-/sys sysfs >> sysfs rw,nosuid,nodev,noexec,relatime >> | |-/sys/kernel/security securityfs >> securityfs rw,nosuid,nodev,noexec,relatime >> | |-/sys/fs/cgroup tmpfs >> tmpfs ro,nosuid,nodev,noexec,mode=755 >> | | |-/sys/fs/cgroup/systemd cgroup >> cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd >> | | |-/sys/fs/cgroup/devices cgroup >> cgroup rw,nosuid,nodev,noexec,relatime,devices >> | | |-/sys/fs/cgroup/blkio cgroup >> cgroup rw,nosuid,nodev,noexec,relatime,blkio >> | | |-/sys/fs/cgroup/pids cgroup >> cgroup rw,nosuid,nodev,noexec,relatime,pids >> | | `-/sys/fs/cgroup/cpuacct cgroup >> cgroup rw,nosuid,nodev,noexec,relatime,cpuacct >> >> However I get this: >> >> # dmesg | egrep "cgroup|control group" >> [ 0.000000] Initializing cgroup subsys cpu >> [ 0.000000] Initializing cgroup subsys cpuacct >> [ 0.001242] Disabling cpu control group subsystem >> [ 0.001263] Initializing cgroup subsys io >> [ 0.001289] Initializing cgroup subsys devices >> [ 0.001304] Initializing cgroup subsys pids >> >> # column -t /proc/cgroups >> #subsys_name hierarchy num_cgroups enabled >> cpu 0 1 0 >> cpuacct 5 59 1 >> blkio 3 9 1 >> devices 2 56 1 >> pids 4 64 1 >> >> Why? really weird. I control the boot process (systemd 231) and nothing there apparently disables it. When I try to mount cpu cgroup manually I just get ENOENT >> -- >> To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html >> ��칻 �&�~�&� ��+-��ݶ ��w��˛���m� ����)���w* jg��� �����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a�� �� �G���h� �j:+v���w�٥ >> > ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <CAGmahrTwRC3cr72S2sJC9pzCxuGmYeWHe-iprz9D20DDDvU7MA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Why would cpu cgroup get disabled by the kernel? [not found] ` <CAGmahrTwRC3cr72S2sJC9pzCxuGmYeWHe-iprz9D20DDDvU7MA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2016-09-02 13:29 ` Tejun Heo 0 siblings, 0 replies; 6+ messages in thread From: Tejun Heo @ 2016-09-02 13:29 UTC (permalink / raw) To: Sverd Johnsen Cc: Zefan Li, Rosen, Rami, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Fri, Sep 02, 2016 at 01:49:44PM +0200, Sverd Johnsen wrote: > /proc/cmdline and CONFIG_CMDLINE are just the standard options (root > console etc.), nothing regarging cgroups. cgroup_disable does not get > used anywhere..dont you think I would have thought of that. Everyone makes silly mistakes and your reputation of immunity isn't a general knoweldge. Don't be snippy with people trying to help you. Li is right that that message can only be triggered by cgroup_disable_mask which can only be set through "cgroup_disable=" kernel boot parameter. * Attach full dmesg after a problematic boot. * If you can, add printk of cgroup_disable_mask in cgroup_init() and see what the value is. -- tejun ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Why would cpu cgroup get disabled by the kernel? [not found] ` <CAGmahrS4P7kS6_5MOhHA=ge6mcq0C2f85iN9S3z5dgi+qsEh9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-09-02 9:44 ` Rosen, Rami @ 2016-09-02 9:54 ` Zefan Li 1 sibling, 0 replies; 6+ messages in thread From: Zefan Li @ 2016-09-02 9:54 UTC (permalink / raw) To: Sverd Johnsen, cgroups-u79uwXL29TY76Z2rM5mHXA On 2016/9/2 17:12, Sverd Johnsen wrote: > Hi! I'am on 4.4.19 (arm) and seem to have all requirements for CPU > cgroups build into the kernel: > > # zgrep -P "CGROUP|GROUP|FAIR" /proc/config.gz > CONFIG_CGROUPS=y > # CONFIG_CGROUP_DEBUG is not set > # CONFIG_CGROUP_FREEZER is not set > CONFIG_CGROUP_PIDS=y > CONFIG_CGROUP_DEVICE=y > CONFIG_CGROUP_CPUACCT=y > # CONFIG_CGROUP_PERF is not set > CONFIG_CGROUP_SCHED=y > CONFIG_FAIR_GROUP_SCHED=y > CONFIG_RT_GROUP_SCHED=y > CONFIG_BLK_CGROUP=y > # CONFIG_DEBUG_BLK_CGROUP is not set > # CONFIG_SCHED_AUTOGROUP is not set > CONFIG_CFQ_GROUP_IOSCHED=y > # CONFIG_NET_CLS_CGROUP is not set > # CONFIG_CGROUP_NET_PRIO is not set > # CONFIG_CGROUP_NET_CLASSID is not set > # CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set > # CONFIG_THERMAL_GOV_FAIR_SHARE is not set > > Other cgroups also work: > > # findmnt -a > TARGET SOURCE > FSTYPE OPTIONS > |-/sys sysfs > sysfs rw,nosuid,nodev,noexec,relatime > | |-/sys/kernel/security securityfs > securityfs rw,nosuid,nodev,noexec,relatime > | |-/sys/fs/cgroup tmpfs > tmpfs ro,nosuid,nodev,noexec,mode=755 > | | |-/sys/fs/cgroup/systemd cgroup > cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd > | | |-/sys/fs/cgroup/devices cgroup > cgroup rw,nosuid,nodev,noexec,relatime,devices > | | |-/sys/fs/cgroup/blkio cgroup > cgroup rw,nosuid,nodev,noexec,relatime,blkio > | | |-/sys/fs/cgroup/pids cgroup > cgroup rw,nosuid,nodev,noexec,relatime,pids > | | `-/sys/fs/cgroup/cpuacct cgroup > cgroup rw,nosuid,nodev,noexec,relatime,cpuacct > > However I get this: > > # dmesg | egrep "cgroup|control group" > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Initializing cgroup subsys cpuacct > [ 0.001242] Disabling cpu control group subsystem dmesg | grep "Command line", and then I guess we'll get to know why. > [ 0.001263] Initializing cgroup subsys io > [ 0.001289] Initializing cgroup subsys devices > [ 0.001304] Initializing cgroup subsys pids > > # column -t /proc/cgroups > #subsys_name hierarchy num_cgroups enabled > cpu 0 1 0 > cpuacct 5 59 1 > blkio 3 9 1 > devices 2 56 1 > pids 4 64 1 > > Why? really weird. I control the boot process (systemd 231) > and nothing there apparently disables it. When I try to mount cpu > cgroup manually I just > get ENOENT ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-09-02 13:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-02 9:12 Why would cpu cgroup get disabled by the kernel? Sverd Johnsen
[not found] ` <CAGmahrS4P7kS6_5MOhHA=ge6mcq0C2f85iN9S3z5dgi+qsEh9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-02 9:44 ` Rosen, Rami
[not found] ` <9B0331B6EBBD0E4684FBFAEDA55776F92CE0E032-cNwSTNrqBuVnIh7sxsoRyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-09-02 9:59 ` Zefan Li
[not found] ` <57C94D7E.4090204-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-09-02 11:49 ` Sverd Johnsen
[not found] ` <CAGmahrTwRC3cr72S2sJC9pzCxuGmYeWHe-iprz9D20DDDvU7MA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-02 13:29 ` Tejun Heo
2016-09-02 9:54 ` Zefan Li
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.