Package Details: linux-rt 4.14.12_rt10-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: 145
Popularity: 1.535790
First Submitted: 2011-08-09 20:03
Last Updated: 2018-01-11 10:45

Required by (9)

Sources (17)

Latest Comments

Gimmeapill commented on 2018-01-13 10:28

Same here: all good so far, actually better results with cyclictest than the firsts 4.14.

rvalles commented on 2018-01-11 19:31

@jhernberg. Yeah, my new microcode is dated 2017-11-20, suggesting Intel has had it ready for a while. The good news is that, after running and using it for a few hours together with cycletest running, there doesn't seem to be any degradation to the max latency column compared to the pre-meltdown-workaround kernel.

jhernberg commented on 2018-01-11 18:59

@rvalles: You are welcome! I had it built 24 hours earlier :), but normally test run it a little before I upload a new script. It has turned up a few issues, and there is no testing on the AUR..

There was an intel ucode update too, so hopefully we are a bit safer now..

rvalles commented on 2018-01-11 17:41

Thank you for the prompt update.

jhernberg commented on 2018-01-07 21:55

Regarding Meltdown, since I'm not a kernel developer I prefer to wait for an official rt patch for a Meltdown patched kernel, rather than blindly applying patches without the necessary understanding. A new patch will be available in a few days.

rvalles commented on 2018-01-07 21:13

Grand. Unflagged until news. Had already read the LWN article before it blew up. It does unfortunately look terrible for latency, particularly when using linux-rt on the desktop (e.g. running web browsers) where disabling the mitigation isn't sensible.

Ralf_Mardorf commented on 2018-01-07 20:54

4.14.8-rt9 is the latest version available, see, hence the package is not out of date. Vulnerabilities such as don't render a package out of date. There are no fixes yet, see and also consider to read

rvalles commented on 2018-01-07 20:39

@Ralf_Mardorf: Neither server or DAW are my use case. My use case is the desktop. Linux-rt makes Linux tolerable. I have never said I can't wait and I can't tell how you came to believe so. Please elaborate on why you think flagging a package that's out of date as such is an abuse of the package action.

Ralf_Mardorf commented on 2018-01-07 20:12

The comments aren't for discussions, hence I posted to Arch proaudio. I care about reasonable security. I also care about the comments from jhernberg, the maintainer who mentioned that he has burnt out on packaging, so asking to backport a patch set, that likely is counter-productive in a real-time context, doesn't make much sense. Is linux-rt a suitable kernel for your server farm? Is KPTI required to increase security of your DAW? Is the possible loss of performance caused by KPTI tolerable for your DAW? Is there a reason for you, that you can't wait until upstream backported the patch set, to the long-term stable kernels?

Btw. that you flagged the package out-of-date is an abuse of the package action.

rvalles commented on 2018-01-07 19:16


Good for you that you don't care about security in your use case.

To answer your question, posted to proaudio instead of here for some reason, we is the rest of us.

All comments