<?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>Troubleshooting on PSA Labs</title><link>https://psalabs.eu/tags/troubleshooting/</link><description>Recent content in Troubleshooting on PSA Labs</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://psalabs.eu/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>proxmox: NIC issues with e1000e network adapters</title><link>https://psalabs.eu/articles/kb/proxmox-nic-issues/</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><guid>https://psalabs.eu/articles/kb/proxmox-nic-issues/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;Some Intel onboard NICs using the &lt;strong&gt;e1000e&lt;/strong&gt; driver can intermittently lose network connectivity on Proxmox VE and repeatedly log errors like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;e1000e … Detected Hardware Unit Hang&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This can cascade into Linux bridge ports being disabled (VM connectivity loss) and may trigger reboot/recovery automation if present.&lt;/p&gt;
&lt;p&gt;A commonly used mitigation is to disable specific NIC offloads (especially &lt;strong&gt;TSO&lt;/strong&gt;) and disable &lt;strong&gt;EEE (Energy Efficient Ethernet)&lt;/strong&gt;, then re-apply those settings on every boot using a systemd unit.&lt;/p&gt;</description></item></channel></rss>