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 .. 102 103 104 105 106 107 108 109 110 111 112 .. 308 Next › Last »

BS86 commented on 2016-10-22 12:39 (UTC)

No issues here with MuQSS on my piledriver. on 4.8.4-1 I am trying out some advanced amdgpu package, which checks for a specific config. Would it be much effort to include it, so that this check does not fail? Kernel 4.8.4-1-ck3-ck not supported CONFIG_DRM_AMDGPU_CIK is missing

graysky commented on 2016-10-22 11:24 (UTC)

Bump to v4.8.4-1 Changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.8.4 Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog Notes: I would like to get some feedback from AUR users around the stability with the MuQSS before I go building [repo-ck] packages with 4.8-ck3. Please test and report back good or bad.

<deleted-account> commented on 2016-10-22 08:56 (UTC)

Hello graysky, I use linux-ck with BFQ and MuQSS enabled since v106. It works very fine with my Skylake CPU. Performances and responsiveness are great with v114/115 :) Thank you for all!

graysky commented on 2016-10-22 07:01 (UTC)

Bump to v4.8.3-3 Changelog: Included 4.8-ck3 which uses MuQSS v0.115. Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog Notes: I would like to get some feedback from AUR users around the stability with the MuQSS before I go building [repo-ck] packages with 4.8-ck3. Please test and report back good or bad.

vishwin commented on 2016-10-22 03:21 (UTC) (edited on 2016-10-22 03:21 (UTC) by vishwin)

-ck3 just released, includes MuQSS v0.115 http://ck-hack.blogspot.com/2016/10/linux-48-ck3-muqss-version-0115.html

graysky commented on 2016-10-21 19:22 (UTC)

Bump to v4.8.3-2 Changelog: Included 4.8-ck2 which uses MuQSS v0.114. Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog Notes: I would like to get some feedback from AUR users around the stability with the MuQSS before I go building [repo-ck] packages with 4.8-ck2. Please test and report back good or bad.

graysky commented on 2016-10-21 13:21 (UTC)

Please post these details to ck's blog so he can assist. http://ck-hack.blogspot.com/2016/10/linux-48-ck2-muqss-version-0114.html#comment-form

xevrem commented on 2016-10-21 12:17 (UTC)

I'm experiencing a kernel panic shortly after boot. Currently I am using the linux-ck-piledriver kernel. from journalctl -k -b -1: Oct 21 07:03:49 vanir kernel: AMD-Vi: Completion-Wait loop timed out Oct 21 07:03:49 vanir kernel: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=07:00.0 address=0x000000040cfa2380] Oct 21 07:03:49 vanir kernel: AMD-Vi: Completion-Wait loop timed out in this log its complaining about device 07:00.0, but its complained about other devices as well that work perfectly fine in other kernels... I would do a dump of those dmesg logs if i could, but it appears journalctl didnt capture anything from those boot cycles... only that one and it never catchs the kernel stack trace dump >_< here is info about my CPU from /proc/cpuinfo if that helps: processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 101 model name : AMD FX-9800P RADEON R7, 12 COMPUTE CORES 4C+8G stepping : 1 microcode : 0x6006113 cpu MHz : 1400.000 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic overflow_recov bugs : fxsave_leak sysret_ss_attrs null_seg bogomips : 5392.44 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro acc_power [13] It should be said, i do not experience these issues with stock kernel nor the zen kernel. I've also tried the generic linux-ck kernel and experience similar issues... Any suggestions or additional info i can grab for you that would help, just let me know :)

Taijian commented on 2016-10-21 11:46 (UTC) (edited on 2016-10-21 14:26 (UTC) by Taijian)

I have a question regarding some modules I am missing when I try to compile the kernel locally. These modules also fail to load with the repo-ck 4.8.3 kernel. The 4.7.6 kernel from repo-ck still had them. Specifically, I have a Dell Inspiron laptop, so I am using i8kutils to get my temp-sensors and my fan to work. According to modprobed-db, this is pulling in the following modules: - dell_laptop - dell_smbios - dell_smm_hwmon - dell_wmi However, when trying to build the kernel, these modules are missing/nowhere to be found. Can anybody help point me in the right direction, where I can pull these in from?

ooo commented on 2016-10-21 10:56 (UTC)

@graysky, Fair enough. Altough The pending/ patches for bfs512 aren't really 'development' patches, but fixes to bugs that were discovered after bfs512/ck1 release. My understanding is that ck simply didn't want to make a new release, but still recommends adding the fixes. Since some people seem to be having issues with bfs512, it would make sense to me to apply those. I have no problems myself, but I guess anyone having issues with linux-ck-4.8* should try if adding the pending bfs512 patches helps.