Package Details: linux-rt 4.9.13_rt12-1

Git Clone URL: https://aur.archlinux.org/linux-rt.git (read-only)
Package Base: linux-rt
Description: The Linux-rt kernel and modules
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: schivmeister
Maintainer: jhernberg
Last Packager: jhernberg
Votes: 140
Popularity: 0.960061
First Submitted: 2011-08-09 20:03
Last Updated: 2017-03-11 11:27

Latest Comments

jhernberg commented on 2017-03-01 23:11

The old ticker config of 1000Hz is obsolete :) Now days hrtimers offer a higher resolution than jiffies.

I use i7 cpus, and for me the pstate driver works very well, but you can easily change the governor if you want to.

If you want to, you can verify the kernel latencies on your system with cyclictest, and some hackbench, see: https://wiki.archlinux.org/index.php/Realtime_kernel#Latency_testing_utilities

sekret commented on 2017-03-01 11:31

May I ask why the timer frequency is set to 300Hz by default rather than 1000Hz?

Also, wouldn't it be better to use the performance governor by default?

Or in other words: Is this kernel supposed to be optimized to the highest level or some sort of compromise?

Gelmo commented on 2017-02-22 18:57

@davelis90 Take a look at this page:

https://help.ubuntu.com/community/UbuntuStudioPreparation

davelis90 commented on 2017-02-22 08:00

Hello!

Could someone write the steps I need to follow (what to type in the command prompt) in order to download and install a realtime kernel in an Ubuntu system (version 16.02)? I am new in Linux and I have no idea how to do it, I only managed to download a low latency kernel but it shouldn´t be enough for my application.

Thank you very much in advance.

jhernberg commented on 2017-02-16 17:42

FYI, nvidia-dkms ought to work again

jhernberg commented on 2017-02-07 13:40

@blackhole: I've asked the -rt devs and they seem fairly convinced that the problem lies in the vbox modules doing something that works on vanilla but breaks on realtime. They said that it's hard to tell what is going on due to Arch's low loglevel. They suggested to add the following to the kernel flags, to see if there would be better console output: "debug ignore_loglevel printk.devkmsg=off"

The debug flag might be picked up by systemd though, thus the reason for "printk.devkmsg=off". They were unsure if systemd would spam the console anyways, but let's try it?

blackhole commented on 2017-02-07 10:18

I have installed to MSI H81M-E33 + i7-4770 with 6 usb ports connected. I am sure it is a timing problem, however. I have booted with blacklisted vbodrv modules, after I have loaded manually and no crash.

jhernberg commented on 2017-02-07 06:36

@blackhole: What kind of hardware do you have?

blackhole commented on 2017-02-06 21:12

Here the problem is that vbox modules are compiling just fine, but once loaded the boot process crash.
This is not occurring all times. Maybe it is a question of loading order, I don't know.
I think I will use a little script trick: I will blacklist them by default while loading the modules with Desktop environment autostart if the kernel is not realtime.

jhernberg commented on 2017-02-06 19:49

@blackhole: There is a discussion lower down about similar problems in the past, maybe helpful? Were the boot problems due to the vbox modules?

All comments