I had such a "hang" again today ... so also "ethtool -K eno1 tso off gso off " did not helped with me :-(
kernel 5.3.10-1-pve
Can you send your nic model from
# lspci -nn
?
I had such a "hang" again today ... so also "ethtool -K eno1 tso off gso off " did not helped with me :-(
kernel 5.3.10-1-pve
Sure.Can you send your nic model from
# lspci -nn
I had such a "hang" again today ... so also "ethtool -K eno1 tso off gso off " did not helped with me :-(
kernel 5.3.10-1-pve
basically the host was running without reboot since I entered the command ... How and where I would need to add it? Could you please tell me that and I will try it.Are you applying it in the network config, any nic reset will cause it to be lost hence you need to enter it into your network config as an if up so its applied every time.
root@pve:~# ethtool -K eno1 tso off gso off
-bash: ethtool: command not found
apt-get install ethtool
# lspci -v | grep Ethernet
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 30)
Subsystem: Intel Corporation Ethernet Connection (6) I219-V
# ethtool -i eno1
driver: e1000e
version: 3.2.6-k
firmware-version: 0.4-4
expansion-rom-version:
bus-info: 0000:00:1f.6
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
So, is there any reason why the e1000e driver being used in Proxmox/Debian is so outdated?
Thanks!
Can't we just get a driver pack instead of a whole new kernel?
Intel Corporation 82578DM Gigabit Network Connection - Proxmox doing the same thing for me, the eno link down. I am not sure how big of an interruption it is, luckily it hasn't affected my streaming yet.
Linux is not working that way So yes new Kernel is the way to go thereCan't we just get a driver pack instead of a whole new kernel?
Intel Corporation 82578DM Gigabit Network Connection - Proxmox doing the same thing for me, the eno link down. I am not sure how big of an interruption it is, luckily it hasn't affected my streaming yet.
Has anyone tested this yet and any results they can share?I have build the laster pve-kernel 5.3 with the patch,
if you want to test:
http://odisoweb1.odiso.net/pve-kernel-5.3.18-2-pve_5.3.18-2_amd64.deb
(I don't have tested it, please don't use it in production)
It's only a backport ofHas anyone tested this yet and any results they can share?
@spirit - Could you provide details of the patch along with how we would installed the patched kernel to test?
Great Thanks! I'll take a look at testing the PVE 5.4 kernel! Will report back but it would be good to know here if others have tried the PVE 5.4 kernel and what the results were for this issue...it's already included in kernel 5.4, and proxmox have official build since last week:
so if you can test it, it could be great
http://download.proxmox.com/debian/...64/pve-kernel-5.4.24-1-pve_5.4.24-1_amd64.deb
Maybe my backport is wrong.Motherboard asrock Z270m itx/ac
CPU qn8j
After replacing the kernel
http://odisoweb1.odiso.net/pve-kernel-5.3.18-2-pve_5.3.18-2_amd64.deb
Mar 19 20:09:11 xwzan kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <a6>
TDT <e5>
next_to_use <e5>
next_to_clean <a6>
buffer_info[next_to_clean]:
time_stamp <1014d1590>
next_to_watch <a7>
jiffies <1014d1748>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
Mar 19 20:09:13 xwzan kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <a6>
TDT <e5>
next_to_use <e5>
next_to_clean <a6>
buffer_info[next_to_clean]:
time_stamp <1014d1590>
next_to_watch <a7>
jiffies <1014d1941>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
Mar 19 20:09:15 xwzan kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <a6>
TDT <e5>
next_to_use <e5>
next_to_clean <a6>
buffer_info[next_to_clean]:
time_stamp <1014d1590>
next_to_watch <a7>
jiffies <1014d1b30>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
Mar 19 20:09:17 xwzan kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <a6>
TDT <e5>
next_to_use <e5>
next_to_clean <a6>
buffer_info[next_to_clean]:
time_stamp <1014d1590>
next_to_watch <a7>
jiffies <1014d1d28>
next_to_watch.status <0>
MAC Status <40080083>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
Mar 19 20:09:18 xwzan kernel: ------------[ cut here ]------------
Mar 19 20:09:18 xwzan kernel: NETDEV WATCHDOG: enp0s31f6 (e1000e): transmit queue 0 timed out
Mar 19 20:09:18 xwzan kernel: WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270
Mar 19 20:09:18 xwzan kernel: Modules linked in: tcp_diag inet_diag veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter softdog nfnetlink_log nfnetlink intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iwlmvm mac80211 aesni_intel libarc4 aes_x86_64 crypto_simd cryptd mei_hdcp iwlwifi glue_helper intel_cstate intel_rapl_perf btusb pcspkr btrtl btbcm cfg80211 btintel bluetooth input_leds ecdh_generic mei_me ecc mei ie31200_edac mac_hid acpi_pad vhost_net vhost tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi vfio_pci vfio_virqfd irqbypass vfio_iommu_type1 sunrpc vfio ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs xor zstd_compress raid6_pq libcrc32c hid_logitech_hidpp hid_logitech_dj hid_generic usbmouse usbkbd usbhid hid e1000e igb i2c_i801 ahci
Mar 19 20:09:18 xwzan kernel: i2c_algo_bit dca libahci video
Mar 19 20:09:18 xwzan kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P O 5.3.18-2-pve #1
Mar 19 20:09:18 xwzan kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z270M-ITX/ac, BIOS P2.60 09/04/2018
Mar 19 20:09:18 xwzan kernel: RIP: 0010:dev_watchdog+0x264/0x270
Mar 19 20:09:18 xwzan kernel: Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 18 54 ea 00 01 e8 e0 e9 fa ff 89 d9 4c 89 ee 48 c7 c7 70 c1 e1 a0 48 89 c2 e8 6d 21 73 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41
Mar 19 20:09:18 xwzan kernel: RSP: 0018:ffffa759001a8e58 EFLAGS: 00010282
Mar 19 20:09:18 xwzan kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006
Mar 19 20:09:18 xwzan kernel: RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff9ada8ecd7440
Mar 19 20:09:18 xwzan kernel: RBP: ffffa759001a8e88 R08: 0000000000000486 R09: ffffffffa159eab8
Mar 19 20:09:18 xwzan kernel: R10: 0000000000000774 R11: ffffa759001a8cb0 R12: 0000000000000001
Mar 19 20:09:18 xwzan kernel: R13: ffff9ada8045c000 R14: ffff9ada8045c480 R15: ffff9ada80430080
Mar 19 20:09:18 xwzan kernel: FS: 0000000000000000(0000) GS:ffff9ada8ecc0000(0000) knlGS:0000000000000000
Mar 19 20:09:18 xwzan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 19 20:09:18 xwzan kernel: CR2: 00007f899eea8000 CR3: 00000005c340a004 CR4: 00000000003626e0
Mar 19 20:09:18 xwzan kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 19 20:09:18 xwzan kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Mar 19 20:09:18 xwzan kernel: Call Trace:
Mar 19 20:09:18 xwzan kernel: <IRQ>
Mar 19 20:09:18 xwzan kernel: ? pfifo_fast_enqueue+0x160/0x160
Mar 19 20:09:18 xwzan kernel: call_timer_fn+0x32/0x130
Mar 19 20:09:18 xwzan kernel: run_timer_softirq+0x19d/0x420
Mar 19 20:09:18 xwzan kernel: ? enqueue_hrtimer+0x3c/0x90
Mar 19 20:09:18 xwzan kernel: ? ktime_get+0x40/0xa0
Mar 19 20:09:18 xwzan kernel: ? lapic_next_deadline+0x26/0x30
Mar 19 20:09:18 xwzan kernel: ? clockevents_program_event+0x93/0xf0
Mar 19 20:09:18 xwzan kernel: __do_softirq+0xdc/0x2d4
Mar 19 20:09:18 xwzan kernel: irq_exit+0xa9/0xb0
Mar 19 20:09:18 xwzan kernel: smp_apic_timer_interrupt+0x79/0x130
Mar 19 20:09:18 xwzan kernel: apic_timer_interrupt+0xf/0x20
Mar 19 20:09:18 xwzan kernel: </IRQ>
Mar 19 20:09:18 xwzan kernel: RIP: 0010:cpuidle_enter_state+0xbd/0x450
Mar 19 20:09:18 xwzan kernel: Code: ff e8 97 c4 82 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 63 03 00 00 31 ff e8 8a 2c 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 cf 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
Mar 19 20:09:18 xwzan kernel: RSP: 0018:ffffa759000c7e48 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
Mar 19 20:09:18 xwzan kernel: RAX: ffff9ada8ecea740 RBX: ffffffffa1158900 RCX: 000000000000001f
Mar 19 20:09:18 xwzan kernel: RDX: 00004fb1b171b988 RSI: 000000004f9a1f43 RDI: 0000000000000000
Mar 19 20:09:18 xwzan kernel: RBP: ffffa759000c7e88 R08: 0000000000000002 R09: 0000000000029fc0
Mar 19 20:09:18 xwzan kernel: R10: 00008baec78344a7 R11: ffff9ada8ece94c4 R12: ffffc758ffadf000
Mar 19 20:09:18 xwzan kernel: R13: 0000000000000006 R14: ffffffffa1158b58 R15: ffffffffa1158b40
Mar 19 20:09:18 xwzan kernel: ? cpuidle_enter_state+0x99/0x450
Mar 19 20:09:18 xwzan kernel: cpuidle_enter+0x2e/0x40
Mar 19 20:09:18 xwzan kernel: call_cpuidle+0x23/0x40
Mar 19 20:09:18 xwzan kernel: do_idle+0x22c/0x270
Mar 19 20:09:18 xwzan kernel: cpu_startup_entry+0x1d/0x20
Mar 19 20:09:18 xwzan kernel: start_secondary+0x167/0x1c0
Mar 19 20:09:18 xwzan kernel: secondary_startup_64+0xa4/0xb0
Mar 19 20:09:18 xwzan kernel: ---[ end trace f6c5e17c3f689390 ]---
Mar 19 20:09:18 xwzan kernel: e1000e 0000:00:1f.6 enp0s31f6: Reset adapter unexpectedly
Mar 19 20:09:18 xwzan kernel: vmbr0: port 1(enp0s31f6) entered disabled state
Mar 19 20:09:23 xwzan kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 19 20:09:23 xwzan kernel: vmbr0: port 1(enp0s31f6) entered blocking state
Mar 19 20:09:23 xwzan kernel: vmbr0: port 1(enp0s31f6) entered forwarding state