Package Details: linux-ck 6.12.1-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.24
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-23 13:58 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 111 112 113 114 115 116 117 118 119 120 121 .. 308 Next › Last »

graysky commented on 2016-09-14 13:14 (UTC)

Even though 4.7.4 is due out today, I have built and published 4.7.3-5 and all related packages to [repo-ck]. CONFIG_CGROUP_SCHED is enabled per CK's suggestion.

usuariopolivalen commented on 2016-09-13 22:55 (UTC)

@gravysky thanks for your work, both of you, I wish I could help more than testing packages, when you put the new version in the repo I will test for report the issues, but I think that the freezes will continue due to the other comment in the page.. @saren what is BTW? I have seen the journalctl with the hour of freezes and nothing.. the freeze make my computer to do nothing and repeat 2 last seconds of music more or less and the mosue to not move and the keyboard the same

graysky commented on 2016-09-13 19:40 (UTC)

Bump to v4.7.3-5 Changelog: update to ck4/bfs497 and reenable CONFIG_CGROUP_SCHED. Commit: https://wiki.archlinux.org/index.php?title=Linux-ck/Changelog Note: I am waiting to hear back from CK before I build the repo packages since he may suggest disabling CONFIG_CGROUP_SCHED. I like to think that the Arch community plays a large role in helping CK to refine bfs so AUR users please continue provide feedback to ck's blog as usual: http://ck-hack.blogspot.com/2016/09/bfs-497-linux-47-ck4.html

Saren commented on 2016-09-13 19:38 (UTC) (edited on 2016-09-13 19:40 (UTC) by Saren)

@agm28011997 Haswell-EP is the xeon version of Haswell cpus, linux-ck-haswell should be 100% compatible with it. I am downgrading once again from 4.7.2-2 to 4.7.2-1 because of your comment. :/ BTW, can confirm the lockup is kernel panic.

usuariopolivalen commented on 2016-09-13 19:30 (UTC)

@saren what is haswell-EP? my freezes starts at 4.7.2-2 with the bfs 472 patch, and other thing, post your problem in the ck blogspot of con kolivas https://ck-hack.blogspot.com.es/ @th3voic3 other like you it is me, if you want you can downgrade the version to 4.7.2-1 with patch bfs472 that is very stable for me @gravysky try to use cgroups enable if you want because for haswell desktop users there are too loockups for use this kernel, we'll wait until a solution

Saren commented on 2016-09-13 19:24 (UTC)

Haswell-EP user here, using linux-ck-haswell. Getting 3 random lockups already since 4.7.3. 2 of the lockups in the GPU Passthrough gaming, and the remaining one happened while watching youtube videos. I am downgrading to 4.7.2 as suggested by the comments and see if the issue will be going away.

th3voic3 commented on 2016-09-13 19:09 (UTC)

I'm using a Haswell cpu and a qemu vm with PCI passthrough. With the recent kernels my entire host would lockup as soon as I shutdown my VM. I just compiled the kernel with the new patch version and enabled CONFIG_CGROUP_SCHED. Just had a lockup again. Although I had lockups with or without CONFIG_CGROUP_SCHED. Haven't tested this patch yet with the option disabled. For now I'm using the mainline kernel. No issues there.

graysky commented on 2016-09-13 19:04 (UTC)

Just waiting to hear back from CK regarding his recommendation to or not to disable CONFIG_CGROUP_SCHED with ck4/bfs497. Will update once this happens.

puithove commented on 2016-09-13 18:50 (UTC)

I'm on a SandyBridge machine and using the SandyBridge package from the repo. I ended up having the same complete system freezes as well as KP on shutdown/reboot even after updating to 4.7.3-4 As of yesterday evening I rolled back to 4.7.2-1 and I seem to be stable again.