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 .. 119 120 121 122 123 124 125 126 127 128 129 .. 308 Next › Last »

Saren commented on 2016-07-31 07:43 (UTC)

Getting kernel panic on Haswell-E as well, I thought it was btrfs's problem, done btrfs check and fixed nothing, then I found the kernel panic message is about bfq and got here.

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

Getting kernel panic on sandybridge as well, freeze on moderate I/O and sometimes get panic messages on shutdown.

zosodk69 commented on 2016-07-30 23:01 (UTC)

The panics are almost certainly BFQv8 related. Reverting to BFQv7r11 makes them go away. I was able to get good panic output by logging to the serial port. I'm not a linux-ck user, rather a standalone BFQ user. I've started a thread on paolo's newsgroup to work through this issue: https://groups.google.com/forum/#!topic/bfq-iosched/80V4U6ak57w Because of these stability issues, I'd recommend linux-ck revert to BFQv7r11.

zerophase commented on 2016-07-30 22:49 (UTC) (edited on 2016-07-30 22:59 (UTC) by zerophase)

@graysky I'm definitely getting kernel panics after the system has been up for a few hours. the numlock key doesn't even respond, once the system locks up. Running the standard kernel for now to see if it's still an issue.

graysky commented on 2016-07-29 19:06 (UTC)

@rucci - That is the default for the PKGBUILD except for _BFQ_enable_=y (and NUMA code has been commented for ages now). The only diff you have is enabling BFQ by default but that shouldn't trigger a bug as you activated it through other means before.

mssdvd commented on 2016-07-29 16:28 (UTC) (edited on 2016-07-29 16:29 (UTC) by mssdvd)

I recompiled again with "_1k_HZ_ticks=y", "_BFQ_enable_=y", "_NUMAdisable=y", gcc patch and now it works without kernel panic...

zerophase commented on 2016-07-29 15:17 (UTC)

@graysky I haven't had any panics yet. Running the kernel compiled for Haswell, with '_1k_hz_ticks' and bfq enabled.

Cake commented on 2016-07-29 14:12 (UTC)

@graysky Yes, I only installed one disk (/dev/sda) and and enabled BFQ on it. Several hours ago, I checked it with cake-pc# cat /sys/block/sda/queue/scheduler noop deadline cfq [bfq] I am sorry that I did not try recompiling `linux-ck=4.6.5` with `_1k_HZ_ticks=`. I just changed `grub.cfg` and rebooted with the stock kernel ... Everything seems to be working fine ... I am wondering what is going on when the system freezes. So if you require any other information, please let me know.

graysky commented on 2016-07-29 13:19 (UTC)

So two reports of the new bfq causing panics? Can you both verify that you have a drive set to use bfq? I don't see how tick rate plays into the equation.

mssdvd commented on 2016-07-29 09:20 (UTC)

It works if I disable "_1k_HZ_ticks" option

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