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.22
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 .. 112 113 114 115 116 117 118 119 120 121 122 .. 308 Next › Last »

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.

usuariopolivalen commented on 2016-09-12 12:44 (UTC)

CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_FREEZER=y what means this lines with cgroups disabled??

usuariopolivalen commented on 2016-09-12 11:52 (UTC)

@gravysky after a few tests I have yet freeze problems while gaming browsing etc.. something wird because is a problem that affects haswell desktops only .. based on read forums and ck blog, I tried to use generic package of linux ck in the repotoo, but it has freezes too

pnehem commented on 2016-09-11 22:52 (UTC)

Thanks @graysky, running great so far!

usuariopolivalen commented on 2016-09-11 19:43 (UTC)

thanks @gravysky

graysky commented on 2016-09-11 14:47 (UTC)

Bump to v4.7.3-4 Changelog: Disable CONFIG_CGROUP_SCHED per CK's suggestion. Commit: https://wiki.archlinux.org/index.php?title=Linux-ck/Changelog

bacondropped commented on 2016-09-10 08:02 (UTC)

@QuartzDragon @pnehem @graysky I've recompiled the kernel without CONFIG_CGROUP_SCHED as well (GCC 6.2.1), and for me, it DOES seem to solve the persistent kernel oops. I'll try to test it more than just poking it with a stick, meanwhile, you can use this config patch (I know it's like sixty lines with context, shut up): https://gist.github.com/bacondropped/b96cbce0382babf6e9046e143fecfd43

QuartzDragon commented on 2016-09-10 00:43 (UTC)

I've disabled CONFIG_CGROUP_SCHED and am rebuilding to see if the problem persists.

bacondropped commented on 2016-09-09 23:28 (UTC) (edited on 2016-09-10 00:22 (UTC) by bacondropped)

@pnehem It seems to happen around the same time to me as well, specifically during Xorg launch sequence (I'm running KDE on Manjaro, so to me, it happens during/after the Plymouth splash). Another person reported an oops with a stack trace that looks almost like mine (sans maybe two entries in the middle): https://ck-hack.blogspot.ru/2016/09/bfs-490-linux-47-ck3.html?showComment=1473328786493#c6823661886449353973 Does your stack trace look like the one in that gist? I'm currently rebuilding the kernel with GCC 5.4.0 instead of 6.2.1 to eliminate the toolchain, I'll let you know how that goes. UPDATE: @graysky Do you think disabling cgroups might be worth considering? CK writes they're unstable and are known to cause problems/panics: https://ck-hack.blogspot.ru/2016/09/bfs-490-linux-47-ck3.html?showComment=1473438769973#c6466606596661012936 UPDATE: rebuilding with GCC 5.4.0 does NOT fix the problem (reminder, here's the problem I'm trying to fix, bug report not mine, but very similar stack trace: https://gist.github.com/pfactum/8c65b2c01f7182eb578dbd9b2ef8ffd3)

pnehem commented on 2016-09-09 20:34 (UTC) (edited on 2016-09-09 23:25 (UTC) by pnehem)

Hello, I'm getting a kernel panic as well, but I was trying to figure out if it where it was happening at because I can get to my login screen, just fine. But when I go to log in then it kernel panics and locks up the computer. I was just getting ready to start reading logs. --update: I updated my system but still getting a seg fault/kernel panic. I get to the login/sddm screen just fine, But the I try to go farther the screen goes black and I can see the cursor and nothing responds locks up the whole system sort of -I can do ctl-alt-F2 and login from the "command line" but I can't make heads or tails of the logs.