Package Details: linux-ck 4.12.8-2

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Package Base: linux-ck
Description: The Linux-ck kernel and modules with the ck2 patchset featuring MuQSS CPU scheduler v0.160
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL2
Provides: linux-ck=4.12.8
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 365
Popularity: 2.221666
First Submitted: 2011-07-22 14:51
Last Updated: 2017-08-20 10:53

Latest Comments

Tharbad commented on 2017-08-22 19:00

It's appears that there's a conflict between scsi_mod.use_blk_mq=0 and any of the multi queue I/O schedulers. So either set scsi_mod.use_blk_mq to 1 or use the "none" scheduler.
Choosing option n2 makes this kernel worthless.
I haven't tried it yet.

Found it here: https://bbs.archlinux.org/viewtopic.php?pid=1730573#p1730573

vp1981 commented on 2017-08-22 12:21

@hotty, @Tharbad, guys would you mind to provide more details? For example, your system configuration (HDD/SSD, FS), kernel cmdline, what queue scheduler do you use and etc. And don't forget that graysky only build the kernel with CK patches, so report any problems to CK, https://ck-hack.blogspot.com/.

Tharbad commented on 2017-08-22 12:08

System freezes sometime during the graphical login. CPU is at 100%.
ctrl+alt+F# and magic keys don't work.

hotty commented on 2017-08-20 21:23

Still got a non-bootable kernel, both from here or from repo-ck freezes at boot since version 4.12.7. Normal arch kernel boots without any issues. Just a blinking cursor and after 2 minutes it shows "Triggering uevents" but thats it.

graysky commented on 2017-08-17 19:13

I bumped to 4.12.8-1 but will hold on building for [repo-ck] until CK verifies the recent merges (github) will not be released to ck3 any time soon.

mrkline commented on 2017-08-15 21:38

@graysky: See https://groups.google.com/forum/#!msg/bfq-iosched/j4QUK4IPOhw/CY1LmmhcAwAJ, as previously mentioned - apparently other kernel devs have removed compile-time scheduler defaults.

I've been able to "fix" it for now with a udev rule, slightly modified from what @vp1981 posted:

ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/scheduler}="bfq"

(The wildcard was causing several false positives and errors to show up in the system log while booting.)

graysky commented on 2017-08-15 21:20

@mrkline - Interesting... I get the same.
EDIT: https://ck-hack.blogspot.com/2017/08/linux-412-ck2-muqss-version-0160-for.html?showComment=1502832329876#c3067299809122898386

mrkline commented on 2017-08-15 20:20

Scratch that, 4.12.7-2 seems to have the same issue.

mrkline commented on 2017-08-15 18:40

Apparently ck-2 contains changes to make BFQ the default scheduler: http://ck-hack.blogspot.com/2017/08/linux-412-ck2-muqss-version-0160-for.html

So we should be good to go as soon as @graysky bumps this.

vp1981 commented on 2017-08-15 12:32

@mrkline, you may ask post-factum to translate new on linux.org.ru, see https://www.linux.org.ru/news/kernel/13581989, but this is receipt from the news:

[russian]
Планировщики ввода-вывода при использовании blk-mq нельзя указывать через командную строку ядра в загрузчике. Вместо этого используйте правило udev, например:

ACTION=="add|change", KERNEL=="sd[a-z]*", ATTR{queue/scheduler}="bfq"

Чтобы включить подсистему blk-mq, ядро нужно собрать с опцией CONFIG_SCSI_MQ_DEFAULT=y или передать параметр scsi_mod.use_blk_mq=1 из загрузчика.
[/russian]

(my translation)
... use udev rule, for example:

ACTION=="add|change", KERNEL=="sd[a-z]*", ATTR{queue/scheduler}="bfq"

In order to enable blk-mq subsystem the kernel has to be configured with option CONFIG_SCSI_MQ_DEFAULT=y or pass parameter scsi_mod.use_blk_mq=1 in boot loader.

P.S. Gee, I found the news on post-factum site:
https://pf.natalenko.name/news/, see "v4.12-pf2 is out" (https://pf.natalenko.name/news/?p=291)

All comments