<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kernel on Linux Security</title><link>https://linuxtransfer.com/tags/kernel/</link><description>Recent content in Kernel on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 14 Sep 2026 11:45:14 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/kernel/index.xml" rel="self" type="application/rss+xml"/><item><title>Using journalctl to Track Down the Hidden ‘eth0’ Carrier Lost Messages That Cause Network Flaps After a Kernel Upgrade</title><link>https://linuxtransfer.com/post/2026-09-14-using-journalctl-to-track-down-the-hidden-eth/</link><pubDate>Mon, 14 Sep 2026 11:45:14 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-09-14-using-journalctl-to-track-down-the-hidden-eth/</guid><description>&lt;h2 id="when-a-kernel-upgrade-silently-breaks-your-network">When a kernel upgrade silently breaks your network&lt;/h2>
&lt;p>Kernel upgrades are usually painless, but on a few systems they can trigger a cascade of “carrier lost” messages that make the interface drop and come back up repeatedly. The messages are buried deep in the system journal, so you may not notice them until the network flaps start causing outages. This post shows how to locate those hidden messages with &lt;code>journalctl&lt;/code>, correlate them with real‑world symptoms, and apply a fix that keeps the interface stable.&lt;/p></description></item></channel></rss>