Package Details: linux-rt 4.6.7_rt14-1

Git Clone URL: (read-only)
Package Base: linux-rt
Description: The Linux-rt kernel and modules
Upstream URL:
Licenses: GPL2
Submitter: schivmeister
Maintainer: jhernberg
Last Packager: jhernberg
Votes: 136
Popularity: 2.859954
First Submitted: 2011-08-09 20:03
Last Updated: 2016-10-03 19:03

Latest Comments

jhernberg commented on 2016-09-03 14:25

4.6.7_rt11-1 contained a performance regression in dcache. Highly recommended to upgrade to 4.6.7_rt11-2, which if it doesn't entirely fix it, at least comes close.

cyberwoodman commented on 2016-08-30 09:08

Here is workaround:
echo keyserver hkp:// >>~/.gnupg/gpg.conf

Then manually import those keys:
gpg --recv-keys 79BE3E4300411886
gpg --recv-keys 38DBBDC86092693E
gpg --recv-keys 7B96E8162A8CF5D1

cyberwoodman commented on 2016-08-30 08:39

==> Verifying source file signatures with gpg...
linux-4.6.tar ... FAILED (unknown public key 79BE3E4300411886)
patch-4.6.7 ... FAILED (unknown public key 38DBBDC86092693E)
patch-4.6.7-rt11.patch ... FAILED (unknown public key 7B96E8162A8CF5D1)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build linux-rt.

jhernberg commented on 2016-08-24 11:34

@oberon: I'll build myself a NO_HZ_FULL kernel and test some.

Regarding vbox modules, I'll let that sleep as I don't maintain any vbox packages, and no one has complained so far. Personally I prefer using qemu, though I use it very sparingly.

oberon2007 commented on 2016-08-23 23:36

The NO_HZ_FULL seems to do what it should and no complaints sofar ;)
Here's our config:
For the vbox-modules it should be enough to locally edit your /usr/src/vboxhost-5.1.4_OSE/vboxdrv/r0drv/linux/timer-r0drv-linux.c like in this patch just with (4, 6, 0) instead of (4, 8, 0).
Like that you should be able to build the modules for 46-rt. It will just fail for regular linux46 and 47 then ;)

jhernberg commented on 2016-08-23 17:19

@oberon: Thanks for the nvidia hint, next week I'm on vacation, so I hope to find some time to mess around with nvidia-dkms. We've had copyright problems before, so I'll see what I can come up with, though I'm suprised that this is the reason this time.

Regarding vbox modules, as no one has complained yet, and I have no way personally to change the vbox modules package I've ignored the entire thing ;)

Googling the nvidia problems I came across some manjaro linux-rt discussion. How is CONFIG_NO_HZ_FULL turning out for you? Iirc I had it on for a short while, but removed it as it didn't seem to help anything, and iirc it was printing the occasional warnings in the kernel msg buffer.

oberon2007 commented on 2016-08-23 16:27

To fix the vbox-modules not building is a little harder. I have patched the vbox-dkms-modules and built in an extra kernel define in the 46-rt kernel:
With these dkm-modules you can then also build the linux-rt-virtualbox extramodules... :P
If you don't need to compile any vbox-modules against other kernels, patching vbox with just >= KERNEL_VERSION(4, 6, 0) instead of (4, 8, 0) will be fine without changing anything in the kernel.
But you still have to compile your patched vbox-dkms first...

oberon2007 commented on 2016-08-23 16:20

The unofficial dirty hack looks like this:

oberon2007 commented on 2016-08-23 16:17

nvidia's MIT license forbids the use of rt_mutex_destroy, therefor:
FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only symbol
There is no "officially clean" fix for this ;)

jhernberg commented on 2016-08-23 14:09

This solves CVE-2016-5696. Unfortunately the latest nvidia-dkms doesn't seem to work, but I downgraded nvidia-dkms to 367.35 which appears to work.

All comments