Github messages for voidlinux
 help / color / mirror / Atom feed
From: adrian-bl <adrian-bl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Raspberry pi 5.x kernel missing memory cgroups
Date: Fri, 04 Sep 2020 12:24:03 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24657@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

New issue by adrian-bl on void-packages repository

https://github.com/void-linux/void-packages/issues/24657

Description:
### System

* xuname:  
Void 5.4.59_1 armv7l Unknown uptodate rFFFF

* package:  
rpi-kernel-5.4.59_1

### Expected behavior

The 5.4 *rbpi* kernel seems to lack support for memory cgroups: this makes it impossible to run any software which requires `/sys/fs/cgroup/memory` to be present.

This breaks nomad for me, but i suppose that docker would also be affected.

Note that the old 4.19.x kernel supported memory cgroups.

I suppose that adding

```
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_KMEM=y
```

to the kernel config would be sufficient (this is how the x86_64 kernel is configured).


### Steps to reproduce the behavior

```
$ grep cgroup/memory /proc/mounts | wc -l
0
```

### Expected behavior

```
grep cgroup/memory /proc/mounts
cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
```

             reply	other threads:[~2020-09-04 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 10:24 adrian-bl [this message]
2020-09-04 10:31 ` ericonr
2020-09-04 10:38 ` ericonr
2020-09-04 18:58 ` adrian-bl
2020-09-04 18:58 ` [ISSUE] [CLOSED] " adrian-bl
2020-09-04 19:01 ` ericonr
2020-09-04 19:08 ` adrian-bl
2020-09-04 19:41 ` ericonr
2020-09-05  7:38 ` adrian-bl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24657@inbox.vuxu.org \
    --to=adrian-bl@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).