Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 405
Popularity: 5.699860
First Submitted: 2011-07-22 14:51
Last Updated: 2019-05-16 20:56

Packages (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

graysky commented on 2019-01-12 09:38

@artafinde - ck1 disables NUMA

artafinde commented on 2019-01-12 09:32

@vltr: try enabling NUMA on ck.

vltr commented on 2019-01-11 09:53

@marceliq ohhh ... I haven't seen that. And that's actually a real bummer :(

marceliq commented on 2019-01-11 09:46

In patch-4.20-ck1 there is:

@@ -896,6 +913,7 @@ config CGROUP_DEVICE

        bool "Simple CPU accounting controller"
+       depends on !SCHED_MUQSS
          Provides a simple controller for monitoring the
          total CPU consumed by the tasks in a cgroup.

which disable CPUACCT if SCHED_MUQSS is enabled :(

vltr commented on 2019-01-11 09:41

Thanks, @graysky! Yeah, I tried to revert some of the changes - docker stopped working after 4.19.4 or 4.19.5 (from repo-ck), but I just got some time to find the source of the error now. I thought it was CONFIG_CGROUP_CPUACCT at first because of error given by docker:

$ docker run --rm hello-world                        
docker: Error response from daemon: unable to find "cpuacct" in controller set: unknown.

That's just an example. Any other docker command (build, run, etc) would eventually ran into this issue (although the docker daemon seem to work normally).

This is something that doesn't happen in the stock kernel (and I make use of testing repositories as well). Anyway, I reverted not only that flag but some others as well (I actually did the diff myself earlier), but docker is still a no go. I'm not that expert in the kernel to go further and analyze what's wrong, unfortunately. I wanted to share my experience here in case anyone bumps into the same problem.

Would you mind providing me CK's blog so I can post there as well?

Thanks a lot!


Just found out the issue, pointed out by @marceliq and then CK's blog and comments regarding this issue as well as the forum post related. Thanks!

graysky commented on 2019-01-10 20:25

@vltr - It would appear the ck1 patchset does this, see here for a diff of the Arch config before and after simply patching with CK1:

Recommend you post to CK's blog referencing that diff and your problem. Might be that he did not mean to do that if I am correct.

vltr commented on 2019-01-10 11:28

Hello, @graysky! Just one question: is there any reason why the CONFIG_CGROUP_CPUACCT flag is not set anymore on linux-ck? Thanks a lot!

graysky commented on 2019-01-01 14:42

@saren - sorry about that... fixed now but did not bump the pkgver.

Saren commented on 2019-01-01 06:13

Hi, since 4.20-ck NUMA is disabled regardless of _NUMAdisable. $ numactl -s shows No NUMA support available on this system.

zoopp commented on 2018-12-27 12:46

I usually build with native optimisations detected by GCC however there's a problem if I assign anything to the _subarch variable. Early during the build this question pops up:

Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW)

.. which is answered with the value of _subarch variable (27 in my case).

Since this isn't an accepted answer, the question loops endlessly.

Not really a big issue but I thought I should mention it.