Package Details: linux-ck 6.11-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.86
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-09-19 13:04 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 198 199 200 201 202 203 204 205 206 207 208 .. 307 Next › Last »

<deleted-account> commented on 2013-08-21 15:07 (UTC)

Somebody got the patch from: https://groups.google.com/forum/#!msg/bfq-iosched/f4Lg5INzQ-k/EFbHNzfjFTsJ to work? When should it be applied?

xcomcmdr commented on 2013-08-21 14:22 (UTC)

@clayman I've had hard lockups at boot-time with linux-ck and the vanilla kernel for a long time. It's rare and random, however. :/ 3.10-8-1-ck gives me the same error as BorgHunter. I reverted to 3.10-7-1-ck and it works fine. I do not have "elevator=something" in my kernel boot line.

clayman commented on 2013-08-21 12:14 (UTC)

@Cosmik Thanks, that's an interesting observation. I have just recompiled the kernel and managed to boot up but it seems I forgot to set BFQ as the default queue scheduler, which explains it.

csmk commented on 2013-08-21 11:29 (UTC)

@clayman, me too. The hard lockup is gone after I removed the "elevator=bfq" from the kernel boot line.

clayman commented on 2013-08-21 11:07 (UTC)

@BorgHunter Thanks, I have the same issue. I have already tried 3.10.9 by editing PKGBUILD but the problem persists. :(

BorgHunter commented on 2013-08-21 11:02 (UTC)

3.10.8 definitely causes problems for me. Hard lockup at boot with the message "Fixing recursive fault but reboot is needed" or something like that (can't find any logs for it). Looks like, according to the changelog, 3.10.9 might solve this. I'm on the vanilla kernel (3.10.7) until ck is updated.