Search results for query: e1000e

I think thats a pretty pretty old bug IMHO. Seen that couple of times already and encountered a similiar problem with an e1000 driver on one of my mini PCs aswell. I've looked up the old thread regarding this and its here. TLDR; Its most likely related to an old intel network card bug. Disable...

...devsel, latency 0, IRQ 145, IOMMU group 13 Memory at a3900000 (32-bit, non-prefetchable) [size=128K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e Kernel modules: e1000e

...(500mbit from isp) when this happened funny thing is,i went to meshcentral(other server),connected(hw desktop) and saw those errors,unloaded e1000e,loaded and still frozen..how the hell is amt working over frozen hw?..luckily i have x710 2-port copper (only inter 10g to nas,no amt there...so...

...Corporation Ethernet Connection (17) I219-LM [8086:1a1c] (rev 11) Subsystem: Dell Device [1028:0ac9] Kernel driver in use: e1000e Kernel modules: e1000e 05:00.0 Non-Volatile memory controller [0108]: Shenzhen Longsys Electronics Co., Ltd. Lexar NM790 NVME SSD...

Feb 06 01:02:30 pve1 kernel: e1000e 0000:00:1f.6 nic1: Detected Hardware Unit Hang: das sagt schon alles. da ist eine intel 1 gbit (vermutlich i218/i219) netzwerkkarte verbaut und die kachelt ab. siehe dazu https://forum.proxmox.com/threads/e1000e-eno1-detected-hardware-unit-hang.59928/

...06 00:56:30 pve1 pveproxy[2178]: worker 2181 finished Feb 06 00:56:30 pve1 pveproxy[2178]: worker 2179 finished Feb 06 01:02:28 pve1 kernel: e1000e 0000:00:1f.6 nic1: Detected Hardware Unit Hang: TDH <1> TDT...

...Corporation Ethernet Connection (17) I219-LM [8086:1a1c] (rev 11) Subsystem: Dell Device [1028:0ac9] Kernel driver in use: e1000e Kernel modules: e1000e 05:00.0 Non-Volatile memory controller [0108]: Shenzhen Longsys Electronics Co., Ltd. Lexar NM790 NVME SSD...

thanks for the post. Can you provide a link to the script you mentioned here? just migrated from ESXI and having this issue multiple times a day. #### found it #### thanks bash -c "$(curl -fsSL...

...related to bad memory: perform a prolonged memory test on both systems driver/firmware bug for e1000: see https://forum.proxmox.com/threads/e1000e-reset-adapter-unexpectedly.87769/#post-384609 proxy/VPN dropping the connection: what network hardware sits in-between the 2 hosts? what MTU is...

...a general networking issue similar to this: https://forum.proxmox.com/threads/pve-network-kernel-tg3-issue-intermittent-lost-of-network.89485/ E1000E is known for causing issues too but you probably don't use that. You can check via ls -l /sys/class/net/*/device/driver. I'd likely connect via...

...100% available at the moment with the error "timeout of 24000ms exceeded" or "getaddrinfo EAI_AGAIN". In my virtual machines, I used the Intel e1000e network adapter, as well as others, including Intel e1000 and virtio. On all of them, the same problem persists. Connection problems, if...

...x86-64-v2-AES efidisk0: data:vm-1107-disk-0,efitype=4m,size=1M memory: 32768 meta: creation-qemu=8.1.5,ctime=1719247597 name: VMName net0: e1000e=BC:24:11:9F:46:B7,bridge=vmbr2 numa: 0 onboot: 1 ostype: l26 parent: OK_12-01-26 sata0: none,media=cdrom scsi2...

I've since fixed this. I updated the network device's model to "Intel E1000E" from "VirtIO" on the backup server's VM configuration, and switched out the Lets Encrypt certificate for the default, self-signed one. I then added this certificate's fingerprint to my storage configuration.

I've already disabled everything related to power saving and Wake on LAN in the BIOS. I've disabled EEE too. This seems to make no changes.

...is going into some kind of power-saving mode, which is why it becomes unresponsive until you physically reset it. With the Intel I217-LM and e1000e driver, this is often related to Energy Efficient Ethernet (EEE) or Wake-on-LAN settings. You could try disabling EEE with ethtool -s nic0 eee...

In der VM habe ich mit VirtIO und E1000E getestet, im Amiga nutze ich das uaenet.device. Aber ich habe es nun hinbeommen, zum einen Fehlte in Windows eine dll: uaenet: npcap/winpcap not installed (wpcap.dll) Und dann hat das uaenet.device im Amiga nun scheinbar "3" verschiedene Devices...

...Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes The NIC uses e1000e drivers, and its model is an Intel Corporation Ethernet Connection I217-LM (rev 04). Thanks in advance.

Intel e1000e driver worked at the beginning, but didn't survive a reboot too. I tried the following, neither of it worked: - virtio 0.1.285 driver - virtio.0.1.266 driver - realtek driver Disabling various advanced networking options (offloading) did not help. I found some information that...

Just built a new Proxmox node and it randomly dies. I have tried to find what's the issue but really heading nowhere. Hardware: 1. Base: Lenovo P3 Ultra Gen 2 2. CPU: Intel Core Ultra 5 235 (Arrow Lake-S) 3. Memory: SK Hynix 2x 32GB SODIMM ECC 4. Drive: Micron 7450 Pro 960GB M.2 2280 5...

...Nr. 7: https://www.intel.com/content/dam/doc/specification-update/82571eb-82572ei-gbe-controller-spec-update.pdf Just because it uses the "e1000e" driver does not necessarily mean, that it is affected by this bug. You have to specifically check the Intel documentation on related topics. The...