I've seen this posted on the forum a number of times, but there has been no posted solution. i have two know good 710 based network cards that have had their SPI flash chip replaced with a blank one. Now both cards are unable to be flashed with using the nvm utility. does anyone know the root cause of this? i am assuming since there is no firmware running from the SPI flash, that the nvm tool can not be used. does this mean that the SPI flash needs to be programmed manually?

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.30.22.3

Copyright (C) 2013 - 2017 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [+.........]

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) Ethernet Controller XL710              154B 00:001 Access error  

    Generic ID                                                 

Tool execution completed with the following status: Device not found

Press any key to exit.

Hi,

under the firmware version info, what does all three fields indicates.i think first one is firmware version, second one is ETrakID, What does the third field indicate ?

driver: i40e

version: 1.3.46.1

firmware-version: 5.05 0x80002927 1.1313.0

bus-info: 0000:08:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

I am planning to upgrade the firmware version to "5.40 0x80002d35 18.0.17", but i am not able to get the file. Is this specific to any vendor or any dependencies ?

-

Vishruth

Hi guys,

I can't get the created vlan(s) enabled. Their states keep showing "disabled" and the "modify" button is grey.

In the "network connections" page, the physical NIC icon is blue, but the virtual NIC(s) is grey.

Anybody has an idea what's going on here ?

Here are some related data:

* The notebook is Dell Latitude / Windows 8.1 pro up to date / 64-bit.

* No VM installed, virtualization is by default enabled at the bios, though.

* Adapter teaming is OFF by default.

* The wired NIC type is Intel i218-LM / ProSet version 23.2 the latest release.

* The ethernet properties have the default values. "Advance Network Services Protocol" will be checked automatically once I create a vlan.

Here are some taken actions:

1- tested out the trunk (tagged) port of the switch by using a macbook and a usb2eth adapter.

2- tried to create 1 vlan only and restart the notebook.

3- tried to create 2 vlans and restart the notebook.

4- tried to assign the virtual NIC ip addresses manually and dynamically.

5- tried to disable it and re-enable it manually from the "network connections" page.

6- tried to turn off the wifi and start all over again.

7- tried to completely remove the proset software and the drivers, restart the notebook, and re-install the 23.2 package.

Thank you in advance !

Henry

Iam so dissappointed i left the stability of qualcomm network driver.

I have been running a KF2 Killing

floor 2 server for years.

Just recently i retired the gigabyte board and went with asus and the intel network drivers i have heard so much about!

Its been 4 mnths of torture trying to sort my high lag spike problem!!

Ping Spikes into the thousands every 5th or so refresh of server in game browser!!!

Yet when i start server on my old giga board the ping is steady!!

I want to break bones !!

How on earth do you release faulty drivers!!!

I finally thought i better atleast try ask and look for solutions in here , god knows ive looked everywhere!!!

NOT HAPPY.. intel LOLOL

i had better add... z370 asus rog strix i gaming crap, latest drivers and all dated drivers all bios now the latest .. attachment shows my 2 servers , ping spikes when running one server also.

Hi,

    I am using network performance measurement tool nuttcp with IGB and E1000 cards on one of my development boards.

Issue: Observed crash/watchdog bite using testing with both IGB and E1000 cards.

Kernel: kernel_msm-3.18

Steps to reproduce.

1.) On device:  ./nuttcp-8.1.4.arm -S

2.) On PC side run below command xxx.xx.xxx.xxx -> IP address of device.

./nuttcp-8.1.4.x86 -w2m -u -R 160M -i 1 -T 1m xxx.xx.xxx.xxx

3) After a couple of iterations we see the crash reported in the log.

IGB  Log

------------------

Parsing debug information for MSM_DUMP_DATA_CPU_CTX. Version: 20 Magic: 42445953 Source:

Parsing CPU1 context start 171c8a800 end 171c8b000

Core 1 PC: arch_counter_get_cntvct+1c <ffffffc000a25164>

Core 1 LR: arch_counter_get_cntvct+1c <ffffffc000a25164>

[<ffffffc000a25164>] arch_counter_get_cntvct+0x1c

[<ffffffc000352ca0>] __delay+0x24

[<ffffffc000352c74>] __const_udelay+0x24

[<ffffffc00049235c>] msm_trigger_wdog_bite+0xd0

[<ffffffc0000f1d0c>] spin_bug+0x94

[<ffffffc0000f1e7c>] do_raw_spin_lock+0x104

[<ffffffc000eb38a0>] _raw_spin_lock+0x28

[<ffffffc000710768>] igb_get_stats64+0x30

[<ffffffc000cb8244>] dev_get_stats+0x4c

[<ffffffc000d249f8>] iface_stat_fmt_proc_show+0x98

[<ffffffc0001e77e0>] seq_read+0x18c

[<ffffffc000222874>] proc_reg_read+0x8c

[<ffffffc0001c5fcc>] vfs_read+0xa0

[<ffffffc0001c6758>] SyS_read+0x58

[<ffffffc0000864b0>] el0_svc_naked+0x24

From the code, it looks like it could be stuck in igb_update_stats and so the unlock might not be happening in time.

Code file:/kernel_msm-3.18/kernel/drivers/net/ethernet/intel/igb/igb_main.c

5160static struct rtnl_link_stats64 *igb_get_stats64(struct net_device *netdev,

5161 struct rtnl_link_stats64 *stats)

5162{

5163 struct igb_adapter *adapter = netdev_priv(netdev);

5164

5165 spin_lock(&adapter->stats64_lock);

5166 igb_update_stats(adapter, &adapter->stats64);

5167 memcpy(stats, &adapter->stats64, sizeof(*stats));

5168 spin_unlock(&adapter->stats64_lock);

5169

5170 return stats;

E1000 Log

-------------

[  100.703446] init: Service 'atfwd' (pid 765) exited with status 255

[  100.708673] init: Service 'atfwd' (pid 765) killing any children in process group

[  104.343224] init: Untracked pid 2636 exited with status 0

[  133.202677] BUG: spinlock lockup suspected on CPU#0, kworker/0:3/986

[  133.208030]  lock: iface_stat_list_lock+0x0/0x18, .magic: dead4ead, .owner: NetworkStats/1294, .owner_cpu: 1

[  133.217936] Causing a watchdog bite!

[  133.345512] Backtrace for cpu 1 (current):

[  133.348758] CPU: 1 PID: 1294 Comm: NetworkStats Tainted: G        W      3.18.31-g12d3836-dirty #2

[  133.357697] Hardware name: Qualcomm Technologies, Inc. APQ8096v3 + PMI8994 DragonBoard (DT)

[  133.366028] Call trace:

[  133.368473] [<ffffffc000089d9c>] dump_backtrace+0x0/0x278

[  133.373843] [<ffffffc00008a034>] show_stack+0x20/0x28

[  133.378884] [<ffffffc000e70b08>] dump_stack+0x9c/0xd4

[  133.383914] [<ffffffc000093700>] arch_trigger_all_cpu_backtrace+0x6c/0xdc

[  133.390687] [<ffffffc0000f1e80>] do_raw_spin_lock+0x108/0x160

[  133.396415] [<ffffffc000e7f428>] _raw_spin_lock+0x28/0x34

[  133.401800] [<ffffffc0006d2de0>] e1000e_get_stats64+0x44/0x118

[  133.407614] [<ffffffc000c83140>] dev_get_stats+0x4c/0xac

[  133.412907] [<ffffffc000cef8f4>] iface_stat_fmt_proc_show+0x98/0x198

[  133.419243] [<ffffffc0001e77e0>] seq_read+0x18c/0x3b4

[  133.424277] [<ffffffc000222874>] proc_reg_read+0x8c/0xb4

[  133.429571] [<ffffffc0001c5fcc>] vfs_read+0xa0/0x14c

[  133.434520] [<ffffffc0001c6758>] SyS_read+0x58/0x94

cheers,

mohit

Hi,

     I’ve come across a need to hotplug PCI devices between dom0 and domU using SR-IOV NIC. But I'm experiencing problems when trying to detach VF more than one PV guests.

I can attach VF  to DomU successful as follow:

# xl pci-assignable-list

0000:05:10.0

0000:05:10.2

# xl pci-attach 1 05:10.0

# xl pci-attach 2 05:10.2

But when I can't detach VF and it report errors as follow:

# xl pci-detach 2 05:10.2

libxl: error: libxl_device.c:1269:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/2/0 not ready

And only 05:10.0 can detach successful :

# xl pci-detach 1 05:10.0

# xl pci-assignable-list

0000:05:10.0

Each guest config is the same like this:

name = "ubuntu-pv-1"

bootloader = "pygrub"

memory = 256

vcpus = 1

vif = [ 'bridge=xenbr0' ]

disk = [ 'file:/home/ye/ubuntu-pv/ubuntu-pv-1/ubuntu-pv-1.img,xvda,rw' ]

pci_permissive = 1

Follow xl dmesg log:

# xl dmesg | grep -i vt-d | grep -i enable

(XEN) Intel VT-d Snoop Control enabled.

(XEN) Intel VT-d Dom0 DMA Passthrough enabled.

(XEN) Intel VT-d Queued Invalidation enabled.

(XEN) Intel VT-d Interrupt Remapping enabled.

(XEN) Intel VT-d Shared EPT tables enabled.

# xl dmesg | grep "I/O virt"

(XEN) I/O virtualisation enabled

And libxl-driver log:

# cat  /var/log/libvirt/libxl/libxl-driver.log

xc: detail: sysctl operation failed -- need to rebuild the user-space tool set?

libxl: error: libxl.c:4364:libxl_get_physinfo: getting physinfo: Permission denied

xc: debug: hypercall buffer: total allocations:7 total releases:7

xc: debug: hypercall buffer: current allocations:0 maximum allocations:1

xc: debug: hypercall buffer: cache current size:1

xc: debug: hypercall buffer: cache hits:6 misses:1 toobig:0

I'm running in Ubuntu 14 using Xen-4.6. I have tested in other machine using the same environment but encountering the same problem.

Hi, we have been redirected here from this thread in the embedded community: ARM tools for 82574 |Embedded Community

To summarize the important parts of our previous discussion, we have an Intel EXPI9301CT Gigabit CT PCI-e Desktop Adapter, which has an 82574 controller and a Winbond W25X40BVNIG flash. We are trying to use the eepromARMtool to reprogram the MAC address in the flash.

Running ./eepromARMtool -dump -NIC=1 gives us a file whose first line is:

8888 8888 8887 0C20 F746 2014 FFFF FFFF

We want to change the MAC address, so we edit the file that was dumped and change the first line to:

70B3 D501 C307 0C20 F746 2014 FFFF FFFF

Then we run ./eepromARMtool -write -NIC=1 -f=new_mac.otp. If we run the dump command again, the flash appears to have the correct contents. However, if we reboot or power cycle the machine and dump again, the output has returned to its original contents. This seems to imply that our changes were not actually flushed to the flash.

Do you have any advice for how to fix this problem? Thank you!

Hi.

I am having problems with I219-V VLAN tag. Whan adding  a tag I get blue screen every single time., reason Bad_pool_caller.

First step I am adding new VLAN in VLAN tab from Intel Ethernet conection I219-V:

And when adding new VLAN tag, let's say 13 it crashes:

I don't even get a chance to press second OK in Intel window, it crashes right here. It says Configuring for two seconds, maybe tree and the blue screen. I can make it anytime I want.
I tried with versions 12.17.8.7 and 12.15.25.6:

I have Lenovo T470s. Any help would be gratefull.

Regards

Hello

I have a strange problem, I have an X710-DA4 card that works very well on a hp ProLiant DL380 Gen9 server

in 2012 r2 Intel (R) Xeon (R) CPU E5-2620 v3 @ 2.40GHz

The card has a strange behavior on hp ProLiant DL360p Gen8 with Intel (R) Xeon (R) CPU E5-2650 v2 @ 2.60GHz, whether in 2016 or 2012 r2 server and doing a new install, on the 4 ports I have a port that creates me BSOD, can not update the driver

if i boot on a livecd ubuntu desktop, my 4 network cards works well.

The card posing the problem has the FrindlyName "Intel (R) Ethernet Converged Network Adapter X710-4"

Is it a prerequisite related to the processor? The prerequisite for this card is just pcie 3.0.

I would like to understand why on 4 cards, 3 work normally and not the 4th.

Thanks in advance Julien

I recently got a new mobo, and upon installing win 10, i discovered the driver mentioned in the title (Intel(R) Ethernet Connection (7) I219-V) is not functioning properly.

It has no connection what so ever.

I have tried to update the driver in the following ways:

Mobo disc

Mobo manufacturer's site

Intels driver download site

Windows device manager

Even after the attempted updates, it still doesn't work. I have tried resetting my CMOS, and it did not have any effect.

Attempting to uninstall the driver is unsuccessful, as it automatically returns.

The LAN port itself when plugged in has LED's flashing.

The LAN controller is enabled/activated in my BIOS.

My BIOS has been flashed to the newest version.

I have windows 10 updated.

Even Intel's own driver updater doesn't do anything for me.

The error code I get from the device is:

This device cannot start. (Code 10)

{Operation Failed}

The requested operation was unsuccessful.

The mobo in question is the MSI B360 Gaming Plus

Is it a possibility that the mobo is faulty? The board is new, and other than the described issue, it works perfectly fine.

Hello,

We have a problem with eepromARMTool using it on Nvidia Jetson TX2.

We are using your 82574L Gigabit Network Controller integrated on Intel Gigabit CT DESKTOP ADAPTER (EXPI9301CTBLK). Our platform is based on Nvidia Jetson TX2 modul (https://www.nvidia.com/en-us/autonomous-machines/embedded-systems-dev-kits-modules/) and we use Nvidia Jetson TX2 Developer Kit with integrated PCIeX4 interface.

Currently, 82574L is connected to Nvidia Jetson Tx2 Developer Kit. Operating system on Jetson TX2 is Ubuntu 16.04, kernel version is Linux tegra-ubuntu 4.4.38-tegra.

We have built eepromARMTool application only by running make on source files which you have provided.

When we run app eepromARMTool without arguments we recived expected answer:

Intel(R) Eeprom ARM Tool ARM OTP Programming Tool

Provided under the terms of a CNDA. Do Not Distribute.

Copyright(C) 2013 by Intel(R) Corporation

NIC BUS DEV FUN Silicon Memory Type Present

=== === === === ===== ======================

1 1 0 0 82574 FLASH

But when run app in dump mode, it causes Bus error (core dumped):

Intel(R) Eeprom ARM Tool NVM/OTP Programming Tool

Provided under the terms of a CNDA. Do Not Distribute.

Copyright(C) 2013-2014 by Intel(R) Corporation

Version 0.6.7

Bus error (core dumped)

dmesg prints:

Unhandled fault: alignment fault (0x92000061) at 0x0000007f7b59e014

Any help will be appreciated.

Regards,

Ilija

Hi.

So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.

Ou snap

Message was edited by: Tiit Talts

Hello,

I have MSI x299 sli plus with I211 and I219-V

and since 2 to 3 weeks of connection problems to know more reception or upload for about 0.1ms.

This happens on both network cards randomly 1h like 10 minutes I tried also to go on a 4G connection and ADSL same symptoms.

The update of the drivers in 23.2 does not change anything and a complete reinstallation of windows 10 pro no change.

it's very annoying in online games if you have solutions ..

Hi ,

   We upgraded firmware of X710-DA2 (EtrackID was added into .cfg file )  and after that card shows access error , how to recover it ?

    Server : ProLiant DL380 Gen10

    OS : 14.04.1-Ubuntu , 3.16.0-77-generic (our internal requirement )

    NICs : HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter (Embedded )

           Intel(R) Ethernet Converged Network Adapter X710 (Field Replacable)

     What we have done :

     1. Upgraded driver to 2.4.10

     2. Tried NVMUpdatePackage , it displayed update not available.

     3. After looking at couple of forum threads for same issue ,we added EtrackID to the nvmupdate.cfg and tried again , upgrade failed with error .

     4. After system reboot , ports are not showing in ifconfig .

Vendor ID IS : 8086 , DEVID is : 5172 , used in PCIe 3.0, x8

sudo lspci | egrep -i --color 'network|ethernet'

02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)

02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)

02:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)

02:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)

13:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)

13:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)

5d:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)

5d:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)

admin@versa-flexvnf: ~] # ethtool -i eth4

driver: i40e

version: 0.4.10-k  <<<< First updated Driver .

firmware-version: f5.60 a1.5 n05.60 e800033b1  <<<<

bus-info: 0000:5d:00.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

[admin@versa-flexvnf: ~] # sudo ethtool -i eth4

driver: i40e

version: 2.4.10  <<<<<<< Driver update ok

firmware-version: 5.60 0x800033b1 1.1752.0  <<<<<<<<

bus-info: 0000:5d:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

[admin@versa-flexvnf: Linux_x64] # sudo ./nvmupdate64e

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.30.22.3

Copyright (C) 2013 - 2017 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [***|......]

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) Ethernet Converged Network       4.65  1572 00:019      Update not    

    Adapter X710                                                     available

02) HPE Ethernet 10Gb 2-port 562FLR-SFP+      5.96  1572 00:093      Update not        

    Adapter                                                           available

We looked at forum for possible reason for displaying Update not available and found EtrackID is not available at nvmupdate.cfg , we added our EtrackID to the list .

800033B1 was added as shown below .

605 BEGIN DEVICE

606 DEVICENAME: XL710

607 VENDOR: 8086

608 DEVICE: 1572

609 NVM IMAGE: X710DA2_6p01_CFGID7p2_OEMGEN.bin

610 OROM IMAGE: BootIMG.FLB

611 EEPID: 80003483

612 REPLACES: 8000191B 80001920 80001DC0 80001F54 80001FA4 80002282 8000206E 800024C6 8000252E 8000252F 80002530 80002892 80002927 80002928 80002929 80002C44 800033B1

613 EEPROM MAP: PF_Alloc_WOL_DIS.txt

614 RESET TYPE: REBOOT

615 END DEVICE

[admin@versa-flexvnf: Linux_x64] # sudo ./nvmupdate64e

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.30.22.3

Copyright (C) 2013 - 2017 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [***|......]

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) Ethernet Converged Network       4.65  1572 00:019 Update not    

    Adapter X710                                                available

02) HPE Ethernet 10Gb 2-port 562FLR-SFP+      5.96  1572 00:093 Update        

    Adapter                                                     available

Options: Adapter Index List (comma-separated), [A]ll, e[X]it

Enter selection:A

Would you like to back up the NVM images? [Y]es/[N]o: Y

Update in progress. This operation may take several minutes.

[****|.....]

Tool execution completed with the following status: An error occurred when updating a firmware module

Press any key to exit.

We rebooted device after failure and found ports are not coming and check the update again .

[admin@versa-flexvnf: Linux_x64] # sudo ./nvmupdate64e

[sudo] password for admin:

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.30.22.3

Copyright (C) 2013 - 2017 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [..********]

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) Ethernet Converged Network       4.65  1572 00:019 Update not        

    Adapter X710                                                available

02) HPE Ethernet 10Gb 2-port 562FLR-SFP+            1572 00:093 Access error   <<<<<<<<<<<<

    Adapter                                                    

Options: Adapter Index List (comma-separated), [A]ll, e[X]it

Enter selection:X

Is there a way to recover the card back ?

Thanks,

Sai Chandra .

C:\Intel23.2\APPS\BootUtil\Winx64>bootutilw64e -iv

Intel(R) Ethernet Flash Firmware Utility

BootUtil version 1.6.59.0

Copyright (C) 2003-2017 Intel Corporation

Image versions in BootIMG.FLB

(...)

Port Network Address Location Series  WOL Flash Firmware                Version

==== =============== ======== ======= === ============================= =======

  1   000E0C668A9F     4:05.0 Gigabit N/A UEFI,PXE Enabled              1.5.86

C:\Intel23.2\APPS\BootUtil\Winx64>bootutilw64e -UP=iSCSI -all

Intel(R) Ethernet Flash Firmware Utility

BootUtil version 1.6.59.0

Copyright (C) 2003-2017 Intel Corporation

iSCSI is not a valid image type for port 1

...and? What can I do?

Hi,

     I’ve come across a need to hotplug PCI devices between dom0 and domU using SR-IOV NIC. But I'm experiencing problems when trying to detach VF more than one PV guests.

I can attach VF  to DomU successful as follow:

# xl pci-assignable-list

0000:05:10.0

0000:05:10.2

# xl pci-attach 1 05:10.0

# xl pci-attach 2 05:10.2

But when I can't detach VF and it report errors as follow:

# xl pci-detach 2 05:10.2

libxl: error: libxl_device.c:1269:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/2/0 not ready

And only 05:10.0 can detach successful :

# xl pci-detach 1 05:10.0

# xl pci-assignable-list

0000:05:10.0

Each guest config is the same like this:

name = "ubuntu-pv-1"

bootloader = "pygrub"

memory = 256

vcpus = 1

vif = [ 'bridge=xenbr0' ]

disk = [ 'file:/home/ye/ubuntu-pv/ubuntu-pv-1/ubuntu-pv-1.img,xvda,rw' ]

pci_permissive = 1

Follow xl dmesg log:

# xl dmesg | grep -i vt-d | grep -i enable

(XEN) Intel VT-d Snoop Control enabled.

(XEN) Intel VT-d Dom0 DMA Passthrough enabled.

(XEN) Intel VT-d Queued Invalidation enabled.

(XEN) Intel VT-d Interrupt Remapping enabled.

(XEN) Intel VT-d Shared EPT tables enabled.

# xl dmesg | grep "I/O virt"

(XEN) I/O virtualisation enabled

And libxl-driver log:

# cat  /var/log/libvirt/libxl/libxl-driver.log

xc: detail: sysctl operation failed -- need to rebuild the user-space tool set?

libxl: error: libxl.c:4364:libxl_get_physinfo: getting physinfo: Permission denied

xc: debug: hypercall buffer: total allocations:7 total releases:7

xc: debug: hypercall buffer: current allocations:0 maximum allocations:1

xc: debug: hypercall buffer: cache current size:1

xc: debug: hypercall buffer: cache hits:6 misses:1 toobig:0

I'm running in Ubuntu 14 using Xen-4.6. I have tested in other machine using the same environment but encountering the same problem.

My Environment:

Server: Fujitsu PRIMERGY RX2530 M4

Ethernet Adapters: Intel Ethernet Connection X722 LOM (Two SFP+ ports)

Ethernet Adapters Firmware: 3.51

--

ESXi: 6.5 U2

i40en driver version: 1.5.8

--

Both ethernet ports are connected to Juniper EX4550 Virtual Chassis (Junos version 12.3R9.4).

Switch ports are in trunk mode with native vlan.

--

After server boot up ESXi show only one X722 port which is online and port pass traffic. When I assign vlan tag to this interface (also changing ip addresses) then port is online but no traffic.

By default dcbx protocol is enabled on all switch ports:

set protocols dcbx interface all

I disabled dcbx protocol on ports where ESXi server is connected:

set protocols dcbx interface xe-0/0/15.0 disable

set protocols dcbx interface xe-1/0/15.0 disable

After server reboot ESXi show two X722 ports which are online and vlan tag assignment is working.

Is this the i40en driver problem?

Hi,

We have been having the same problem since last October when we upgraded to esxi 6.5 and in turn started using the i40en nic driver. With this driver on every few weeks one of our hosts locks up. This post nails the problem better than I can describe Install ESXi 6.5 on R730 with Intel X710 |VMware Communities

Our workaround was to downgrade to the i40e version, unfortunately doing this makes VMware non compliant in update manager and because us IT guys have serious OCD its very annoying. It's also not good as we like to keep a visual view of these hosts so we know when to patch them.

Is this issue going to be fixed? Just to note on more than one occasion we have had production hosts go down because of this issue and we have had to explain to our staff.

Regards

Hello everyone,

My desktop motherboard uses an Intel l211 network adapter and on Windows Pro 1803 (with the latest 23.2 driver, but also with 23.1) I've noticed that TCP Checksum Offload cannot be enabled at all via Device Manager -> Advanced Adapter Settings or Windows PowerShell.

On Advanced Adapter Settings, the options seem to be set to Disabled by default, but once I set them to something else and apply the settings, the window is closed, connection is lost for a few seconds, and once I open the Settings page once again, the options are back to Disabled.

Then, I tried using Enable-NetAdapterChecksumOffload on Windows Powershell, but when I try reading the new values with Get-NetAdapterChecksumOffload, I see everything set to Disabled.

Any ideas?

Thanks!

I was looking through the i40evf source code, and it seems like the maximum number of queues supported is 4. Is there a reasoning for this? Is there a way to use more, such as 16?

I've seen patches proposing removing a few variables (MAX_QUEUES, which sets the max to 16, but doesn't actually serve a purpose since the RX queues limit is set to 4).