Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 410
Popularity: 4.346297
First Submitted: 2011-07-22 14:51
Last Updated: 2019-07-14 10:53

Packages (2)

Latest Comments

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

graysky commented on 2019-01-17 00:50

@air-g4p - As well, your CFLAGS are not the Arch standard... drop -fstack-protector-strong per the new makepkg.conf in pacman-5.1.2-2.

graysky commented on 2019-01-16 21:07

@air-g4p - See the comments in the PKGBUILD and the discussion here in the AUR.

<h1>Note - the march=native option is unavailable by this method, use the nconfig and manually select it.</h1>

In short, I do not know how to allow the native option to get set via the method used for the other discretely defined options.

air-g4p commented on 2019-01-16 20:35


I'm running an i7 8550U.

Under both /etc/makepkg.conf and ~/chroot/root/etc/makepkg.conf, I have these identical settings:


CARCH="x86_64" CHOST="x86_64-pc-linux-gnu"

-- Compiler and Linker Flags

CPPFLAGS="-D_FORTIFY_SOURCE=2" CFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" CXXFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"

-- Make Flags: change this for DistCC/SMP systems


-- Debugging flags

DEBUG_CFLAGS="-g -fvar-tracking-assignments" DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

Is there anything you see in my setup that would drive:

'The build fails with hundreds of instances of:

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

that I mentioned when '_subarch=27' is set?

I normally build linux-ck in a clean chroot without issue, but this infinite loop issue disturbs me.

graysky commented on 2019-01-13 12:11

I remember looking at this a while ago and concluding it isn't possible... prove me wrong :)

air-g4p commented on 2019-01-13 09:37

Hi graysky,

I can confirm the build loop issue zoopp mentioned last month is still present in linux-ck 4.20.1-1.

With this PKGBUILD option set:

27. Native optimizations autodetected by GCC (MNATIVE)


The build fails with hundreds of instances of:

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

It appears to me that the only way out of this loop is crtl-c.

Of course, the build proceeds normally with any other appropriate subarch assigned.

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!