Search results for query: e1000e

...interface restart**: For bridges, also restarts underlying physical interfaces - **Hardware hang detection**: Detects and handles Intel e1000e controller hangs from kernel logs - **Hardware-level reset**: Module reload and PCI reset for hardware hangs (e1000e, etc.) -...

...machine: pc-q35-9.2+pve1 memory: 8192 meta: creation-qemu=9.2.0,ctime=1752367111 name: Tiny11 net0: e1000e=BC:24:11:55:2C:E5,bridge=vmbr0,firewall=1 numa: 0 ostype: win11 scsi0: local-zfs:vm-119-disk-1,cache=writeback,discard=on,iothread=1,size=32G scsihw: virtio-scsi-single smbios1...

Just as a follow-up: I ran the community script and once I rebooted I appear to be in the clear of any issues.

Hello heliospeed, Also had this start happening (Without a backup run on my Home Lab too. Jul 09 21:08:07 pve kernel: e1000e 0000:00:19.0 enp0s25: Detected Hardware Unit Hang: TDH <5e> TDT <e4>...

...with kernel 6.8.12-11-pve. When I switch back to kernel 6.5.13-6-pve, the problem disappears entirely. I’m using an Intel NIC with the e1000e driver. Here is the output of lspci -nn | grep -i eth: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection...

...ideas for troubleshooting update your bios and try to disable c-states there, some users had instabilities with amd cpu's and disabling c-states helped your mainboard has an intel nic, check if you are affected by the e1000e bug - check dmesg for entries with " e1000e Detected Hardware Unit...

Just a wild guess but that sounds like the e1000e bug. Do you use an intel nic? If you disconnect the cable and reconnect it, does the web interface work again? If yes you should read this

I upgraded on the 26th and so far (6 days) this "e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:" has hit me twice. Proxmox: 8.4.1 Kernel: 6.8.12-11-pve NIC: Intel Corporation Ethernet Connection (7) I219-LM (rev 10) This is my home system so I've just renegotiated the device when it...

...any issues with the network bridge. I have also tried all network card models. Does anyone have an idea? Could it be possible that the network card model needs to be correctly selected during installation? I had Virtio during the installation, but I read that one should use the Intel E1000E.

Some revisions of the the I225-V have been causing problems. The e1000e "fixes" might help here too.

Hab es jetzt über das Helperskript gelöst: https://community-scripts.github.io/ProxmoxVE/scripts?id=nic-offloading-fix

...lspci | grep -i ethernet 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10) ethtool -i eno1 driver: e1000e version: 6.8.12-11-pve firmware-version: 0.5-4 expansion-rom-version: bus-info: 0000:00:1f.6 supports-statistics: yes supports-test: yes...

same issue here: Proxmox 8.4.1 proxmox-kernel-6.8.12-8-pve-signed e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <fa> TDT <35> next_to_use...

...machine: pc-q35-9.2+pve1 memory: 16382 meta: creation-qemu=9.2.0,ctime=1751172511 name: tiny11-23h2 net0: e1000e=BC:24:11:34:9F:CC,bridge=vmbr0,firewall=1 numa: 0 ostype: win11 scsihw: virtio-scsi-single smbios1: uuid=82cd2088-d17c-4b69-8534-19b3dbaa9cef sockets: 1 tpmstate0...

It was pure luck that I looked at the ssh session just as it crashed. I got a copy a few seconds before it disappeared. So, the two errors are ata7.00: failed command: READ FPDMA QUEUED ata7.00: failed command: WRITE FPDMA QUEUED How do I figure out which device is ata7.00? I've got 4 x SSDs...

There was little visible content remaining post-crash this time either. There was plenty on the screen four hours earlier, pasted below: What's the next step in diagnosing this? Any recommendation on preserving the watch "dmesg | tail -50" content in a terminal window? Is there another...

...bridge-stp off bridge-fd 0 post-up /sbin/ethtool -K eno1 tso off gso off source /etc/network/interfaces.d/* source: https://forum.proxmox.com/threads/intel-nic-e1000e-hardware-unit-hang.106001/post-765582 the post-up hook invokes ethtool which does set the offload settings

I do have the e1000e nic and made sure to include it in my system description. I'd skimmed those threads before, but hadn't dug into them because my symptoms don't match exactly and I don't have the Detected Hardware Unit Hang in my logs. I also didn't want to start applying fixes for problems...

See if there's any "e1000e" mentioned in your dmesg. A lot of people, myself included, have been having issues with Intel NICs causing the nodes to reboot randomly when any bit of traffic is going through the NIC. https://forum.proxmox.com/threads/intel-nic-e1000e-hardware-unit-hang.106001/page-3

...CPU: Intel Xeon E5-2695 v4 18c/36t @ 2.10GHz RAM: 64GB DDR4,2400,RDIMM,ECC,HYNIX Mobo: Mikonos MB LGA-2011 NIC: 1Gbps ethernet onboard mobo e1000e Intel(R) PRO/1000 Network Connection GPU: Nvidia GTX 1060 Storage: 1 x SPCC 256GB as boot SSD 2 x Sandisk 512GB as LVM-Thin storage drives 1 x...