e1000 driver hang
- Thread starter alatteri
- Start date
I appreciate the reply, I googled earlier and also found ethtool -k <adaptername>, however it didn't work for me and your command isn't either
Despite the fact that this command DOES work ... (confused)
ethtool -K eno1 tso off gso off
Any thoughts?
show the output of the commandI appreciate the reply, I googled earlier and also found ethtool -k <adaptername>, however it didn't work for me and your command isn't either
Despite the fact that this command DOES work ... (confused)
ethtool -K eno1 tso off gso off
Any thoughts?
ip aand the
networking config
Last edited:
Last edited:
jaxjexjox
add networkingauto loiface lo inet loopbackiface eno1 inet manualoffload-gso offoffload-gro offoffload-tso offoffload-rx offoffload-tx offoffload-rxvlan offoffload-txvlan offoffload-sg offoffload-ufo offoffload-lro offapply without rebooting
ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg offwe check
ethtool -k eno1 | grep offloadYou can also see the number of interface crashes
dmesg | grep 'Reset adapter unexpectedly' | wc -l
Last edited:
Thank you!
So my original command was:
ethtool -K eno1 tso off gso off
This still left the following on:
With those 3 still on, my testing still passed.
Your command indeed turns the whole lot off, none the less I'll stick with yours, I assume the performance impact on a 6 core machine isn't too high.
Finally, when you say 'add networking' I take it you mean /etc/network/interfaces - add those lines?
(sorry, still learning!) and thank you, thank you all.
After rebooting, this is my result:
Here's the contents of /etc/network/interfaces, I take it I've done something wrong?
Last edited:
Ok thanks for this, I have ended up using the post-up command in the interfaces file and that's ended up causing it to stick on reboot.
Thanks all for the help, hopefully there's a longer term solution for this which can help others, ideally they find this thread before they spend a long, long time diagnosing the issues.
Thanks all for the help, hopefully there's a longer term solution for this which can help others, ideally they find this thread before they spend a long, long time diagnosing the issues.
I can't believe this is STILL a problem in 2024!
I have now read though almost everything but i keep getting stuck when trying to run the ethtool command
Below is the output of ip a
So i have manged to figure out that it is on "enp0s25" i need to to disable tso and gso
But when i run ethtool -K enp0s25 tso off gso off , i get this error message
I have tried to google it but had no success
I'm running proxmox 5.15.143-1-pve,
My ethernet controller:
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 05)
Subsystem: Dell Ethernet Connection I217-LM [1028:0617]
Kernel driver in use: e1000e
Kernel modules: e1000e
(yes i have tried adding
iface enp0s25 inet manual
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for eno1" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for eno1"). But it just spits out the same error)
Below is the output of ip a
Bash:
root@pve:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 48:4d:7e:d0:27:5b brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 48:4d:7e:d0:27:5b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.211/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::4a4d:7eff:fed0:275b/64 scope link
valid_lft forever preferred_lft forever
4: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 92:3f:e9:05:5c:1b brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 scope global vmbr1
valid_lft forever preferred_lft forever
5: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
link/ether 92:11:6a:7e:1c:47 brd ff:ff:ff:ff:ff:ff
6: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a2:cd:e2:50:93:ca brd ff:ff:ff:ff:ff:ff
7: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000But when i run ethtool -K enp0s25 tso off gso off , i get this error message
Bash:
root@pve:~# ethtool -K enp0s25 tsp off gso off
netlink error: bit name not found (offset 56)
netlink error: Operation not supportedI have tried to google it but had no success
I'm running proxmox 5.15.143-1-pve,
My ethernet controller:
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 05)
Subsystem: Dell Ethernet Connection I217-LM [1028:0617]
Kernel driver in use: e1000e
Kernel modules: e1000e
(yes i have tried adding
iface enp0s25 inet manual
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for eno1" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for eno1"). But it just spits out the same error)
Thank you all. Having the same issue on Proxmox v8. Network interface keeps hanging every couple of minutes under heavy load. Resolved with a command below (took effect immediately without a reboot)
Also for persistence across reboots I added this to my
Friendly reminder: when copy pasting the above remember to double check that your interface name is also eno1. If not then modify the code accordingly.
ethtool -K eno1 gso off tso offAlso for persistence across reboots I added this to my
/etc/network/interfaces underneath iface eno1 inet manual line so it looks like thisiface eno1 inet manual post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for eno1" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for eno1"Friendly reminder: when copy pasting the above remember to double check that your interface name is also eno1. If not then modify the code accordingly.
Last edited:
Register a special account to inquire about the latest solution to this problem.
The current situation on my side is
I tried using the methods given above, such as
The problem now is not to solve the problem of E1000 network card, but according to the above settings, whether adding the network card configuration file or manually entering the command to execute, it will cause the virtual machine on this host to be unable to ping. However, the console web can still access the virtual machine.
I don’t know how to solve this problem now, please help me.
The current situation on my side is
- You can see that the network card model is I219-V
Code:
lspci -nn |grep Ethernet
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (14) I219-V [8086:15fa] (rev 11)- You can see the PVE kernel version
Code:
uname -a
Linux pve15 6.8.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-1 (2024-08-05T16:17Z) x86_64 GNU/Linux- You can see the PVE version
Code:
pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1- Add to the network card configuration file
Code:
post-up /usr/bin/logger -p debug -t ifup "Disabling segmentation offload for {{ DRIVER_NAME }}" && /sbin/ethtool -K $IFACE tso off gso off && /usr/bin/logger -p debug -t ifup "Disabled offload for eno1"- Execute commands manually
Code:
ethtool -K {{ DRIVER_NAME }} tso off gso offThe problem now is not to solve the problem of E1000 network card, but according to the above settings, whether adding the network card configuration file or manually entering the command to execute, it will cause the virtual machine on this host to be unable to ping. However, the console web can still access the virtual machine.
I don’t know how to solve this problem now, please help me.
This previous post in this thread on a workaround "fixed" it for me. Haven't had the issue since. However, I have noticed a significant increase in CPU load.
https://forum.proxmox.com/threads/e1000-driver-hang.58284/page-8#post-390709
https://forum.proxmox.com/threads/e1000-driver-hang.58284/page-8#post-390709
I solved my problem using the methods listed at
Code:
https://forum.proxmox.com/threads/e1000-driver-hang.58284/post-390709This method was used before, but there was no solution.
But this time, I confirmed that the problem has basically been solved