<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ansible on Opscode</title><link>https://opscode.io/tags/ansible/</link><description>Recent content in Ansible on Opscode</description><generator>Hugo -- 0.162.1</generator><language>en-us</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://opscode.io/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>The Kernel Updated. The Drivers Didn't.</title><link>https://opscode.io/posts/kernel-pinning-dkms/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://opscode.io/posts/kernel-pinning-dkms/</guid><description>&lt;p&gt;I work with industrial Linux systems that have strict real-time requirements. The hosts
run low-latency kernels and depend on out-of-tree kernel drivers compiled against the
running kernel. When any part of that chain breaks, critical functionality is lost.&lt;/p&gt;
&lt;p&gt;Kernel pinning and out-of-tree driver management are two related problems that need to be
solved together. This post covers why, and how.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="why-the-low-latency-kernel"&gt;Why the low-latency kernel&lt;/h2&gt;
&lt;p&gt;The generic kernel runs fine on most Ubuntu hosts. The issue is not that it is broken; it
is that it does not meet the timing requirements of the software and hardware devices
connected to these systems.&lt;/p&gt;</description></item></channel></rss>