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.84
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 .. 246 247 248 249 250 251 252 253 254 255 256 .. 307 Next › Last »

skydrome commented on 2012-07-27 03:05 (UTC)

bfq bumped to 3.4.0-v4 minor changes http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.4.0-v4/README.BFQ

<deleted-account> commented on 2012-07-25 11:27 (UTC)

@Eithrial This has already been covered. Disable dynamic ticks, aka: # CONFIG_NO_HZ. See comments from 22 Jul. @Graysky Well I'm busy this week, but my plan was to try again later in the week, double and triple check through and try 3.5 again, failing that I was going to pull arch 3.5 from git, have a look through and build it. I have a feeling because I also used localmodconf I may have missed something. Also, using systemd 186-2 had no booting issues for me.

graysky commented on 2012-07-25 11:24 (UTC)

@eithrial - Comment by: graysky on Sun, 22 Jul 2012 12:22:02 +0000 Bump to v3.4.6-1 Changelog: We'll need to wait for ck to release a bfs that compiles against upstream with NO_HZ as an option. For now, I have removed it and set the clock to 300 MHz. If you are unhappy with this, do not update to 3.4.6 and stay with 3.4.5-1. Commit: http://pkgbuild.com/git/aur-mirror.git/commit/linux-ck?id=f48012d059d9c273e56b0cc66782e40042c98fdb

<deleted-account> commented on 2012-07-25 11:02 (UTC)

I can't compile 3.4.6-1. I got this error. LD init/built-in.o LD .tmp_vmlinux1 kernel/built-in.o: In function `tick_nohz_stop_sched_tick.isra.9': tick-sched.c:(.text+0x49c29): undefined reference to `calc_load_enter_idle' kernel/built-in.o: In function `tick_nohz_idle_exit': (.text+0x49fa7): undefined reference to `calc_load_exit_idle' make: *** [.tmp_vmlinux1] Error 1 ==> ERROR:(B A failure occurred in build().(B  Aborting...(B

felixonmars commented on 2012-07-25 06:42 (UTC)

I'm using systemd 187-2 and have no trouble at all on 3.5.0-0.

wuffleton commented on 2012-07-25 06:19 (UTC)

@graysky: Just enabled [testing] and -Syyu'd. After a reboot, both linux 3.5-1 and systemd 187-2 worked fine with no issues whatsoever. A full build of linux-ck 3.5-0 without localmodconfig is also working fine on my setup now that I've removed the btrfs_advanced hook.

graysky commented on 2012-07-25 05:42 (UTC)

@DarkSniper - can you boot the linux package in [testing]? Also, 187-2 is in [testing] as well. Might wanna enable it and -Syyu @Psykorgasm - same question but does your stuff work there?

wuffleton commented on 2012-07-25 04:58 (UTC)

@misc: Yikes, thanks for that information. I definitely won't be looking forward to that moving into core if those issues aren't resolved by then. It looks like the nonfunctional usb keyboard was due to a missing module (I used localmodconfig on my first build of it), and the early-userspace error was somehow the fault of btrfs_advanced, since specifying my root partition on the kernel's command line and disabling that hook resolved that problem. For now, systemd 186 seems to be working fine, seeing as I was able to successfully boot after the init issue was taken care of.

misc commented on 2012-07-24 19:30 (UTC)

Haven't been able to boot with systemd since 187 regardless of the used kernel. It will just stop to boot after apparently mounting my partitions once more (it repeats the same massage mentioning my HDD as often as there are Linux-relevant partitions — all ext4 — on it), without any further explanation. All that's possible then is to try to reboot, upon which readahead will complain about a read-only partition and some fsck are run, then it halts again. IOW, right now I'm back to classic initscripts.

wuffleton commented on 2012-07-24 18:53 (UTC)

I was unable to boot 3.5.0-0, it claimed that /sbin/init did not exist, and kicked me to a recovery shell, and my USB keyboard did not work (but my laptop's built one did). Not sure if it could contribute to this, but I'm using systemd and have a btrfs root (via the btrfs_advanced hook).