From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9926] systemd-resolved.service: Failed at step NAMESPACE (systemd 233)
Date: Fri, 02 Jun 2017 08:47:57 +0000 [thread overview]
Message-ID: <bug-9926-163-Rx75cSIilp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9926-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9926
--- Comment #1 from Michael Heinemann <posted@heine.so> ---
On the ML Mike points out that this might be Kernel related (for some reason
his response is not showing up on bugzilla).
I build my Kernel outside of buildroot. So I use an identical Kernel with both
buildroot versions. Of course this doesn't mean a kernel configuration might
not be the issue, but it wasn't an issue with BR 2017.02.2.
The cgroup configuration looks like this:
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_CGROUP_PIDS=y
# CONFIG_CGROUP_FREEZER is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CHECKPOINT_RESTORE is not set
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-06-02 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:35 [Buildroot] [Bug 9926] New: systemd-resolved.service: Failed at step NAMESPACE (systemd 233) bugzilla at busybox.net
2017-06-01 17:44 ` Mike Williams
2017-06-02 8:47 ` bugzilla at busybox.net [this message]
2017-06-02 8:52 ` [Buildroot] [Bug 9926] " bugzilla at busybox.net
2017-06-02 9:04 ` bugzilla at busybox.net
2017-06-04 9:40 ` bugzilla at busybox.net
2017-08-06 16:25 ` bugzilla at busybox.net
2017-09-08 7:07 ` bugzilla at busybox.net
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=bug-9926-163-Rx75cSIilp@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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