Package Details: linux-ck 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.132423
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Dependencies (14)

Required by (7)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 308 Next › Last »

artafinde commented on 2021-05-27 14:06 (UTC)

I suspect your issues has something to do with cgroups v2. Try to replicate the issue after setting (temporarily) systemd.unified_cgroup_hierarchy=0 as a kernel param which forces the cgroup v1 behavior.

GAZ082 commented on 2021-05-27 13:46 (UTC)

@snack had your issue and also a system freeze with the latest release. First time after almost a year of using CK. Went back to Zen.

snack commented on 2021-05-27 06:38 (UTC)

@zerophase I'm not sure. For sure it's something inside the CK patchset (since the stock and many other patched kernels work fine), and it's not MuQSS (see e.g. the comment by Steven Barret on CK's blog stating that Liquorix with MuQSS works fine). I'd need to understand if there is some hope for this to be fixed, otherwise I'll have to ditch linux-ck.

zerophase commented on 2021-05-27 02:30 (UTC)

@snack It has been a bug for awhile. I tried reporting it about a year ago, when trying to author a custom arch install disk, and got some explanation from a guy that this is not a CK issue. (Wasn't CK)

snack commented on 2021-05-26 06:04 (UTC) (edited on 2021-05-26 06:05 (UTC) by snack)

I cannot start docker containers when using the current (5.12) linux-ck-skylake kernel. I get this error:

$ docker run --rm -it -p 80:80 ckulka/baikal:nginx
docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: load program: invalid argument: unknown.

With the stock Arch kernel it works, and seemingly also with other patched kernels like Liquorix (although I didn't try by myself).

I know that it is usually suggested to post to CK's blog for this kind of issue, and in fact I did it but from there I got the advice to post to AUR...

vp1981 commented on 2021-05-19 05:45 (UTC)

graysky> GCC 11 reorders things and since GCC 11 is in [core], I updated the PKGBUILD.

That was a culprit! I updated PKGBUILD, rebuild the package (linux-ck-sandybridge) and was able to boot with linux-ck-sandybridge kernel.

elektorronikci commented on 2021-05-18 18:47 (UTC) (edited on 2021-05-18 18:47 (UTC) by elektorronikci)

@graysky, thanks for your suggestion. There is not any problem for me, I had already corrected it when I saw it on nconfig. I mentioned about it just to inform.

graysky commented on 2021-05-18 17:43 (UTC)

@graysky, no it is GCC 10.2

Right, define an updated mirror and update your system :D

elektorronikci commented on 2021-05-18 17:02 (UTC)

@graysky, no it is GCC 10.2

thaewrapt commented on 2021-05-18 16:05 (UTC)

It could also happen on automation level, where the build system is still using old IDs. I'm building for Skylake right now so I can check if it's actually built for Skylake in the end.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 308 Next › Last »