Search results for query: e1000e

Deine Analyse ist goldrichtig, es handelt sich um eine Kernel-Regression, die den e1000e Treiber betrifft. Das Anpinnen des alten Kernels ist ein guter Workaround. Langfristig ist das aber keine Dauerlösung, da du wichtige Kernel-Updates verpasst. Um die genaue Ursache im neuen Kernel zu finden...

...kommen. Falls du während der Installation auf eine andere Konsole (z.B. mit ALT+F2) wechseln kannst, wäre die Ausgabe von dmesg | grep e1000e interessant. Das könnte zeigen, warum der Treiber nicht korrekt lädt. Auch wenn du lieber direkt installierst: Der Weg über eine PVE 8.4 Installation...

Thank you for your suggestion, it pointed me in the right direction. The problem stems from me running "powetop --auto-tune" as a service. This puts the I-225 into a state that does not respond when the link is reconnected. Here is a good explanation I found in the internet: the command "echo...

...-i enp4s0 is the only viable workaround, maybe you manage to use something similar to a method mentioned in https://forum.proxmox.com/threads/e1000e-reset-adapter-unexpectedly.87769/ The problem there is probably other (offload functions), but I think on putting post-up /usr/sbin/ethtool -i...

Most likely the e1000e bug. You have to disable hardware offloading for your nic. https://forum.proxmox.com/threads/e1000e-reset-adapter-unexpectedly.87769/post-384609

Hi! This is probably a known problem (also see kernel bug) with the e1000e driver. Have you tried turning off TCP segmentation offloading and generic segmentation offloading? ethtook -K <interface> tso off gso off

...(one or more days of operation) and stops being accessible via network: 2025-10-01T08:55:47.939730+02:00 pvehost2 kernel: [90070.981674] e1000e 0000:00:1f.6 eno2: Detected Hardware Unit Hang: 2025-10-01T08:55:47.941867+02:00 pvehost2 kernel: [90070.981674] TDH <b6>...

...Intel Corporation Ethernet Connection (11) I219-LM based NIC. Here is the message that appears in the syslog. Sep 30 08:18:08 pve-02 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <22> TDT <d6> next_to_use <d6>...

...the pve git 6.8.12-8-pve -> Ubuntu-6.8.0-53.54 6.8.12-9-pve -> Ubuntu-6.8.0-58.60 The only things between those version i could find (with e1000e) on the Ubuntu Kernel changelog: e1000e: change I219 (19) devices to ADP e1000e: avoid failing the system during pm_suspend e1000e: Remove Meteor...

...(2025-09-12T09:46Z) x86_64 GNU/Linux root@prox-01:~# ******************************* 2025-09-27T06:34:36.839088+02:00 prox-01 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: 2025-09-27T06:34:36.839114+02:00 prox-01 kernel: TDH <98>...

...1 worker(s) 2025-09-27T06:32:46.701284+02:00 prox-01 pvedaemon[1194]: worker 3105368 started 2025-09-27T06:34:36.839088+02:00 prox-01 kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: 2025-09-27T06:34:36.839114+02:00 prox-01 kernel: TDH <98>...

Hello, I'm new to Proxmox VE and have a problem configuring my first server's network. I'm using an onboard Intel network card (I219-V, driver e1000e) and an external USB 3.0 network card from Realtek (RTL8153, driver r8152). The Intel I219-V is configured for a peer-to-peer connection to my...

...this morning the driver fails. but i've a clear installation without any changes in /etc/network/interface Sep 24 06:13:14 pve kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <f6> TDT...

...can not afford to lose Frigate-Home assistant usage in the home for extended periods of time. Thank you very much Sep 23 09:14:18 pve kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <64> TDT <82> next_to_use <82>...

After searching around, I found this recommendation: Create the file (if it doesn't exist) /etc/modprobe.d/e1000e.conf Put the following inside: options e1000e InterruptThrottleRate=3000 Then run: update-initramfs -u -k all And reboot. At the moment, it doesn't cut out after 2 minutes like it...

Hello, good morning. I arrived here via a Google search. I have a Dell 7070 with Intel e1000e and these problems. Today I did an upgrade and there was a new kernel, 6.14.8-3-bpo12-pve. With this kernel, after two minutes, the network connection is lost. Is there a solution to this problem?

...Intel "i2xx" nic is an absolute garbage, best joke they calling this "E1000/E1000E" :D The original e1000 adapter was produced nearly 20 years ago, when it was a "proper" server grade nic hardware ( INTEL PRO1000 ). Upgrade something "higher" or buy Broadcom NIC.

https://forum.proxmox.com/threads/network-issues-on-proxmox-netdev-watchdog-transmit-queue-timed-out-e1000e.155340/#post-752319 Hope this helps you.

Now it crashes much more often if sleep state C6 is disabled in the BIOS! With sleep state C6 enabled it ran about 2 days before hanging, if the C6 sleep state is disabled (which ran wonderful all the time before Proxmox 9 upgrade), it crashes after a few hours. Looked into journalctl logs...

Please check if it's related to https://forum.proxmox.com/threads/proxmox-6-8-12-9-pve-kernel-has-introduced-a-problem-with-e1000e-driver-and-network-connection-lost-after-some-hours.164439/ I am probably affected by the e1000 driver issue.