Package Details: linux-ck-headers 6.11.10-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: Headers and scripts for building modules for Linux-ck kernel
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 458
Popularity: 0.094674
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 118 119 120 121 122 123 124 125 126 127 128 .. 308 Next › Last »

ryant0000 commented on 2016-08-10 22:14 (UTC)

My machine kernel panicked after updating to 4.6.6-1. I do use BFQ for my ext4 root drive. I did not kernel panic on previous versions.

graysky commented on 2016-08-10 17:39 (UTC)

Bump to v4.6.6-1 Changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.6.6 Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

Distorted commented on 2016-08-10 14:48 (UTC)

Does anyone have issues with the new BFQ scheduler? The first v8 did some damage so i want to be careful

graysky commented on 2016-08-08 22:07 (UTC)

Bump to v4.6.5-4 Changelog: v8r2 of BFQ Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

graysky commented on 2016-08-05 22:02 (UTC)

Bump to v4.6.5-3 Changelog: v8r1 of BFQ Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

Distorted commented on 2016-08-05 20:39 (UTC)

Paolo updated the patch to bfq 4.6.0-v8r1, which causes the current url to be incorrect as wel.

graysky commented on 2016-08-02 17:36 (UTC)

@fafik1234 - Not out of date yet, see[1]. 1. https://wiki.archlinux.org/index.php/Linux-ck#Release_cycle

graysky commented on 2016-07-31 08:10 (UTC)

OK... I recommend using an alternative IO scheduler until Paolo resolves the issue.

glavin commented on 2016-07-31 08:06 (UTC)

yes getting kernel panic with bfq enabled on ext4 filesystem, in my case.

graysky commented on 2016-07-31 07:59 (UTC)

For those getting panics, please verify that it is because you are using BFQ on a device.