Does Intel(R) PROSet for Wired Connections 9.20.0000 supports Windows Server 2008 R2 and Windows Server 2012 R2?

My ESXi 5.5 system has Intel X540-t2 installed, and using ixgbe driver version 3.21.

In the driver code, I can see the following lines, which shows it does not support MAC address change in ESXi 5.5, because if vfinfo[vf].pf_set_mac=true, when guest OS change its MAC, the ixgbe driver won't change it in vfinfo accordingly and will report error: VF attempted to set a new MAC address but it already has an administratively set MAC address

int ixgbe_ndo_set_vf_mac(struct net_device *netdev, int vf, u8 *mac)

{

  s32 retval = 0;

  struct ixgbe_adapter *adapter = netdev_priv(netdev);

  if (!is_valid_ether_addr(mac) || (vf >= adapter->num_vfs))

      return -EINVAL;

  dev_info(pci_dev_to_dev(adapter->pdev), "setting MAC %pM on VF %d\n", mac, vf);

  dev_info(pci_dev_to_dev(adapter->pdev), "Reload the VF driver to make this change effective.\n");

  retval = ixgbe_set_vf_mac(adapter, vf, mac);

  if (retval >= 0) {

      /* pf_set_mac is used in ESX5.1 and base driver but not in ESX5.5 */

      adapter->vfinfo[vf].pf_set_mac = true;

      if (test_bit(__IXGBE_DOWN, &adapter->state)) {

          dev_warn(pci_dev_to_dev(adapter->pdev), "The VF MAC address has been set, but the PF device is not up.\n");

          dev_warn(pci_dev_to_dev(adapter->pdev), "Bring the PF device up before attempting to use the VF device.\n");

      }

  } else {

      dev_warn(pci_dev_to_dev(adapter->pdev), "The VF MAC address was NOT set due to invalid or duplicate MAC address.\n");

  }

  return retval;

}

static int ixgbe_set_vf_mac_addr(struct ixgbe_adapter *adapter, u32 *msgbuf, u32 vf)

{

  u8 *new_mac = ((u8 *)(&msgbuf[1]));

  if (!is_valid_ether_addr(new_mac)) {

      e_warn(drv, "VF %d attempted to set invalid mac\n", vf);

      return -1;

  }

  if (adapter->vfinfo[vf].pf_set_mac && memcmp(adapter->vfinfo[vf].vf_mac_addresses, new_mac, ETH_ALEN)) {

      u8 *pm = adapter->vfinfo[vf].vf_mac_addresses;

      e_warn(drv,  "VF %d attempted to set a new MAC address but it already has an administratively set MAC address %2.2X:%2.2X:%2.2X:%2.2X:%2.2X:%2.2X\n",

                            vf, pm[0], pm[1], pm[2], pm[3], pm[4], pm[5]);

      e_warn(drv, "Check the VF driver and if it is not using the correct MAC address you may need to reload the VF driver\n");

      return -1;

  }

  return ixgbe_set_vf_mac(adapter, vf, new_mac) < 0;

}

However, according to the VMware document, it should be supported.   Why this contradiction happens?

I had a tool suffered BSoD issue recently. I used Windbg to analyze crash dump file. Windbg pointed out issue probaly caused by e1000325.sys (intel NIC driver), but I don't understand the detail message from Windbg. Could someone teach me how to read analysis result of windbg ?

Thanks.

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00ffdff9, memory referenced

Arg2: 000000ff, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: ffdff983, address which referenced memory

Debugging Details:

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

WRITE_ADDRESS:  00ffdff9

CURRENT_IRQL:  ff

FAULTING_IP:

+2702faf00e2dfc4

ffdff983 ff80f9dfff00    inc     dword ptr [eax+0FFDFF9h]

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

TRAP_FRAME:  805500f0 -- (.trap 0xffffffff805500f0)

ErrCode = 00000002

eax=00000000 ebx=80010031 ecx=ffdff980 edx=80010031 esi=badb0d00 edi=806f372a

eip=ffdff983 esp=80550164 ebp=ffdff980 iopl=0         nv up di ng nz ac po cy

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010093

ffdff983 ff80f9dfff00    inc     dword ptr [eax+0FFDFF9h] ds:0023:00ffdff9=????????

Resetting default scope

LAST_CONTROL_TRANSFER:  from ffdff983 to 804e187f

STACK_TEXT:

805500f0 ffdff983 badb0d00 80010031 86329394 nt!KiTrap0E+0x233

WARNING: Frame IP not in any known module. Following frames may be wrong.

80550160 806f372a badb0d00 80010031 86329380 0xffdff983

80550174 f73a26a0 86329008 804da6ed 00000202 hal!HalProcessorIdle+0x2

8055017c 804da6ed 00000202 804da6f6 00000000 e1000325+0x6a0

80550184 804da6f6 00000000 f746ef2e 860f4930 nt!KeSynchronizeExecution+0x17

8055018c f746ef2e 860f4930 f73a2694 80010031 nt!KeSynchronizeExecution+0x20

805501ac 804dbbd4 80558e80 80558c20 ffdff000 NDIS!ndisMDpcX+0x62

805501d0 804dbb37 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46

805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10

STACK_COMMAND:  kb

FOLLOWUP_IP:

e1000325+6a0

f73a26a0 c20400          ret     4

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1000325+6a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1000325

IMAGE_NAME:  e1000325.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4450f0b4

FAILURE_BUCKET_ID:  0xD1_e1000325+6a0

BUCKET_ID:  0xD1_e1000325+6a0

Followup: MachineOwner

---------

Personal desktop PC, ASUS VANGUARD B85 mainboard onboard ethercard Intel® I217V, now need to install a intel I350-T4 PCI-E 4 port gigabit ethercard, run Windows Server 2012 R2 operating system. Ask: they can be used together?

https://downloadcenter.intel.com/download/25442/Network-Adapter-Driver-for-Windows-Server-2012-R2- This is intel I350-T4 for Windows Server 2012 R2 operating system of the driver? Among the following description:

NOTE: The following devices do not have driver or software support for Windows Server 2012 R2:

- Intel® Ethernet Connection I217-V

- Intel® Ethernet Connection I218-V

- Intel® 82579V Gigabit Ethernet PHY

Does this mean that after the installation is complete, i mainboard onboard ethercard Intel® I217V will invalid?

If this card is branded Dell then it is hardware ID

PCI\VEN_8086&DEV_1528&SUBSYS_50038086&REV_01

In that case it can have firmware upgraded by this update Intel NIC Family Version 17.0.0 Firmware for I350, I354, X520, and X540 adapters

But I have a couple of RETAIL units that present hardware ID

PCI\VEN_8086&DEV_1528&SUBSYS_00018086&REV_01

They can not be upgraded by above update, they also strangely present current version of firmware 0.0.0 (surely could not be the case?)

Is there a way to upgrade firmware for retail cards?

Seb

I need a driver for Intel 82567LM-3 Gigabit Network Connection for a Win7 computer.

I am trying to run a bridge inside a VM and would like the VF interface to be in promiscuous mode so that it can receive packets for any unicast MAC address.  I am currently unable to get this to work and have found some interesting threads about promiscuous mode not working in a VF.  Mainly these:

Intel i350: promiscuous mode and SR-IOV

promisc function does not work with VF in XL710 Network card

However this thread talks about setting all ones in the UTA in order to enable promiscuous mode:

ixgbe 3.21.2 driver for 82599

So some questions - is this supported?  Seems there is a bit of conflicting information out there.  Even if not by the published driver, is it supported by the hardware?  The driver companion guide doesn't really have enough information about how to make this work or explain why or where the all 1s thing would work.  I have tried and have not been able to get it to work.  I'd be curious to understand what the performance implication is.

I have the ability to peek/poke registers and manipulate the driver if need be.  I can upgrade if need be but I've looked at the differences in the drivers around this area and can't see anything different enough to warrant upgrading.

Hi, Expert

I've investigated this for some days.

My purpose is launching a VM which has two VFs come from two physical NICs, and then do the bonding inside the VM.

I've tried all the 7 bonding modes, only the mode 1(active-backup) works, all the others cannot work.

From the following articles, the reason why other bonding mode cannot work is VM cannot change the VF's MAC address successfully.

https://bugzilla.redhat.com/show_bug.cgi?id=1164224

SR-IOV on NIC 82599: Are VF MAC Addresses unique?

https://communities.intel.com/message/246183#246183

From the igb driver code, I also notice the HOST refuse VM's change VF's MAC address request.

case E1000_VF_SET_MAC_ADDR:

    retval = -EINVAL;

    if (!(vf_data->flags & IGB_VF_FLAG_PF_SET_MAC))

         retval = igb_set_vf_mac_addr(adapter, msgbuf, vf);

    else

         dev_warn(&pdev->dev, "VF %d attempted to override administratively set MAC address\nReload the VF driver to resume operations\n", vf);

    break;

So, My question is

* Does Intel's SR-IOV NIC only support bonding mode active-backup? only this mode not request VM change it's interface's MAC address.

* If I want to use active-active bonding mode, such as mode 0/2/4/5/6, any solution/walkaround to make it work?

Thanks.

Hi,

  Recently in one of the customer field we observed packet drop with Intel XL710 40GbE NIC.  Is there any know packet drop/issues with following XL710 Rev02/B1 NIC?

We saw packet drop even though we haven't utilized link capacity 100%. Hardly 50% of link capacity utilized when we observe the packet drop issue.

05:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02)

05:00.1 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02)

We have APP which is developed by using DPDK 2.1 version and used XL710 NIC for packet reception/transmission. 

Here is the high-level view how our APP RX and TX path connected Router which is immediate node for our APP.

     APP  <== RX Path======   

                                                      Router

     APP  ====TX Path======>

Unfortunately there is no way to measure the actual error packet statistics at APP side as DPDK 2.1 doesn't support the NIC statistics for driver i40e.

Please help us if there is any know packet drop issues with even XL710 B1 seriers. Or some other fine tune tuning required in NIC level.

Thanks in advance for your help.

Regards,

Suresh.

Intel Wired Ethernet team,

The latest version of the ProWinx64.exe driver package (20.7) is missing the powershell module.  It was in 20.3.

How can we maintain powershell support and update the driver?

Hello , the problem is this: While surfing the web browser, downloading files or other network activity all okay when I go online game ( CS:GO , League of Legends , World of Tanks) ) I start to lost packets ,after that just (Connection problem)and i need to reconnect or restart my ethernet adapter, it does not depend on time, load or from the network server, one time everything is OK and sometimes LAG and dissconected ,cable for direct \ cable from the router, it does not matter , the problem remains.Help please what to do, where to find the problem. Configuration of computer Motherboard : Z97-Pro Gamer (last BIOS) , adapter Intel(R) Ethernet Connection I218-V (last driver from Intel), Win7 Ultimate !

For whatever reason, my internet decides to disconnect at random times during the night when I am not using it. It always returns, however the Network Icon will sit with the yellow exclamation mark until a reboot or ipconfig /release and /renew. It claims there is not internet access while the internet will work. It appears to me, this is a bug in the software/driver or an cryptic setting that just needs adjusting.

While it isn't a major error, its a bit of eyesore to constantly see it everyday especially on brand new hardware.

For the record, its happened on 2 different Asus boards and chipsets, but the Intel I219-V remains the common culprit.

There were complete fresh installs of Windows 7 64 bit with all updates and all correct drivers. None of the driver updates for the I219-V have fixed it.

Also, a Realtek NIC does NOT suffer this issue.

So it could be a setting I am missing, but I have not seen this issue raised anywhere and I highly doubt I received 2 faulty Intel NICs on 2 completely different boards so its more than likely a software/driver issue.

Why my internet drops, well thats the fault of ISP. And yes, its not the ethernet wire.

Thanks

We have a polling XL710 VF driver and have found the appropriate poll-mode workaround in the DPDK. We are however not using the DPDK and are relying on the accompanying fix made to the latest Intel PF Linux drivers eg  version 1.3.49. However this fix does not work and we believe it is incomplete. The part we are referring to involves the clearing of the DIS_AUTOMASK_N flag in the GLINT_CTL register. The code in the above release (and earlier ones) is: (i40e_virtchnl_pf.c: 344)

    if ((vf->driver_caps & I40E_VIRTCHNL_VF_OFFLOAD_RX_POLLING) &&

        (vector_id == 0)) {

        reg = rd32(hw, I40E_GLINT_CTL);

        if (!(reg & I40E_GLINT_CTL_DIS_AUTOMASK_VF0_MASK)) {

            reg |= I40E_GLINT_CTL_DIS_AUTOMASK_VF0_MASK;

            wr32(hw, I40E_GLINT_CTL, reg);

        }

We believe this should say:

    if ((vf->driver_caps & I40E_VIRTCHNL_VF_OFFLOAD_RX_POLLING)

       && (vector_id == 1) {

       reg = rd32(hw, I40E_GLINT_CTL);

        if (!(reg & I40E_GLINT_CTL_DIS_AUTOMASK_VF0_MASK)) {

          reg |= I40E_GLINT_CTL_DIS_AUTOMASK_VF0_MASK |

                    I40E_GLINT_CTL_DIS_AUTOMASK_N_MASK);

           wr32(hw, I40E_GLINT_CTL, reg);

        }

    }

With the above changes the fix then works.

The addition of the I40E_GLINT_CTL_DIS_AUTOMASK_N_MASK is as per the datasheet S 8.3.3.1.4.2.

The test for vector_id == 1 is because the default MSIX vector is 1. However there is a good argument for removing this test altogether since the vector involved depends on the VF implementation. Note that the fix in the DPDK eliminates this test.

We would appreciate it if you could verify the above and make changes to the released PF driver.

Hi

just upgraded to windows 10.

There is a Intel pro 1000 and in windows 7 after installing Advanced Network services from Intel the VLAN feature was very helpful

after upgrading to Windows 10 the  VLANS are no longer available.

When attempting to install Advanced Network services from Intel,  the following error is displayed

there is an issue with Microsoft* windows* 10 the prevents the Intel(R) Advanced Network Services from working correctly

where can the correct drivers be found, searches have been unsuccessful thus far.

Any help appreciated.

Chris

Okay i have a problem here, i would like to upgrade my graphics card since it kinda sucks. but im not sure how or if its even possible here are my important specs

Graphics card - Intel HD530 (Integrated in processor)

Processor      - Intel Core i3-6100 3,70GHz

Motherboard  - ASUS H110M-K D3

Power           - FSP 500W 60HHN 80+ Bronze  

I have opened my desktop and it looked like there was room for a new card, but i asked someone and he said it wouldn't work.

Too my knowledge if there is room, there is power and there is the software. i should be able. if i can which would you recommend, i have a decent budget about 1000 dollars but please keep it about 200-300 dollars. otherwise i will just sel the thing and buy a new one.

I am evaluating the Ethernet Server Adapter I350-T2 to replace our previous end of life card.  I have not had any issues with the card during my operational tests but when I execute the cards offline tests the network interface goes offline and requires the network service to be restarted.  My concern that there is some real instability between my hardware/software and the I350 that could manifest in failures over prolonged use.

Here are my test results and kernel log data.

$ sudo ethtool --test eth2 offline

Cannot get strings: No such device

2016-03-03 11:04:34.833 localhost kernel: igb 0000:01:00.0: offline testing starting

2016-03-03 11:04:34.833 localhost kernel: igb 0000:01:00.0: eth2: igb: eth2 NIC Link is Down

2016-03-03 11:04:36.508 localhost kernel: igb 0000:01:00.0: eth2: igb: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None

2016-03-03 11:04:36.943 localhost avahi-daemon[948]:  Interface eth2.IPv4 no longer relevant for mDNS.

2016-03-03 11:04:36.943 localhost avahi-daemon[948]:  Leaving mDNS multicast group on interface eth2.IPv4 with address 192.168.50.2.

2016-03-03 11:04:36.944 localhost kernel: igb 0000:01:00.0: eth2: PCIe link lost, device now detached

2016-03-03 11:04:36.944 localhost kernel: igb 0000:01:00.0: pattern test reg 002C failed: got 0x0000FFFF expected 0x00005A5A

2016-03-03 11:04:38.621 localhost kernel: igb 0000:01:00.0: testing shared interrupt

2016-03-03 11:04:40.315 localhost kernel: igb 0000:01:00.0: Cannot do PHY loopback test when SoL/IDER is active.

2016-03-03 11:04:45.155 localhost avahi-daemon[948]:  Withdrawing address record for fe80::a236:9fff:XXXX:XXXX on eth2.

2016-03-03 11:04:45.155 localhost avahi-daemon[948]:  Withdrawing address record for 192.168.50.2 on eth2.

2016-03-03 11:04:45.155 localhost ntpd[2499]:  Deleting interface #8 eth2, fe80::a236:9fff:XXXX:XXXX#123, interface stats: received=0, sent=0, dropped=0, active_time=6201 secs

2016-03-03 11:04:45.155 localhost ntpd[2499]:  Deleting interface #4 eth2, 192.168.50.2#123, interface stats: received=0, sent=0, dropped=0, active_time=6201 secs

Why is this offline test failing? Should I even worry that this test fails? Does anybody have some tips as to what I should change/fix/do to get the test to pass?

Thanks,

Stephan

Some background details:

OS: Linux Fedora 13

Motherboard:  AIMB-780 w/ Intel Core i5-660

$ sudo ethtool -i eth2

driver: igb

version: 5.3.3.5

firmware-version: 1.63, 0x80000cbb

bus-info: 0000:01:00.0

$uname -r

2.6.33.5-112.fc13.i686.PAE

$ sudo lspci -s 01:00  -nnvvvk

01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)

  Subsystem: Intel Corporation Ethernet Server Adapter I350-T2 [8086:0002]

  Physical Slot: 128

  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

  Latency: 0, Cache Line Size: 32 bytes

  Interrupt: pin A routed to IRQ 16

  Region 0: Memory at fbd00000 (32-bit, non-prefetchable) [size=1M]

  Region 3: Memory at fbcfc000 (32-bit, non-prefetchable) [size=16K]

  Capabilities: [40] Power Management version 3

  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)

  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-

  Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

  Address: 0000000000000000  Data: 0000

  Masking: 00000000  Pending: 00000000

  Capabilities: [70] MSI-X: Enable+ Count=10 Masked-

  Vector table: BAR=3 offset=00000000

  PBA: BAR=3 offset=00002000

  Capabilities: [a0] Express (v2) Endpoint, MSI 00

  DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us

  ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+

  DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+

  RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-

  MaxPayload 128 bytes, MaxReadReq 512 bytes

  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-

  LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L0s L1, Latency L0 unlimited, L1 <32us

  ClockPM- Surprise- LLActRep- BwNot-

  LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+

  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

  LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+

  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-

  LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

  Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

  Compliance De-emphasis: -6dB

  LnkSta2: Current De-emphasis Level: -6dB

  Capabilities: [100 v2] Advanced Error Reporting

  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

  Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-87-06-7c

  Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)

  ARICap: MFVC- ACS-, Next Function: 1

  ARICtl: MFVC- ACS-, Function Group: 0

  Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)

  IOVCap: Migration-, Interrupt Message Number: 000

  IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy-

  IOVSta: Migration-

  Initial VFs: 8, Total VFs: 8, Number of VFs: 8, Function Dependency Link: 00

  VF offset: 384, stride: 4, Device ID: 1520

  Supported Page Size: 00000553, System Page Size: 00000001

  Region 0: Memory at 00000000c0000000 (64-bit, prefetchable)

  Region 3: Memory at 00000000c0020000 (64-bit, prefetchable)

  VF Migration: offset: 00000000, BIR: 0

  Capabilities: [1a0 v1] #17

  Capabilities: [1c0 v1] #18

  Capabilities: [1d0 v1] Access Control Services

  ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  Kernel driver in use: igb

  Kernel modules: igb

01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)

  Subsystem: Intel Corporation Ethernet Server Adapter I350-T2 [8086:0002]

  Physical Slot: 128

  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

  Latency: 0, Cache Line Size: 32 bytes

  Interrupt: pin B routed to IRQ 17

  Region 0: Memory at fbb00000 (32-bit, non-prefetchable) [size=1M]

  Region 3: Memory at fbcf8000 (32-bit, non-prefetchable) [size=16K]

  Capabilities: [40] Power Management version 3

  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)

  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-

  Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

  Address: 0000000000000000  Data: 0000

  Masking: 00000000  Pending: 00000000

  Capabilities: [70] MSI-X: Enable+ Count=10 Masked-

  Vector table: BAR=3 offset=00000000

  PBA: BAR=3 offset=00002000

  Capabilities: [a0] Express (v2) Endpoint, MSI 00

  DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us

  ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+

  DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+

  RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-

  MaxPayload 128 bytes, MaxReadReq 512 bytes

  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-

  LnkCap: Port #0, Speed 5GT/s, Width x4, ASPM L0s L1, Latency L0 unlimited, L1 <32us

  ClockPM- Surprise- LLActRep- BwNot-

  LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+

  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

  LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+

  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-

  LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB

  Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

  Compliance De-emphasis: -6dB

  LnkSta2: Current De-emphasis Level: -6dB

  Capabilities: [100 v2] Advanced Error Reporting

  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

  Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-87-06-7c

  Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)

  ARICap: MFVC- ACS-, Next Function: 0

  ARICtl: MFVC- ACS-, Function Group: 0

  Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)

  IOVCap: Migration-, Interrupt Message Number: 000

  IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy-

  IOVSta: Migration-

  Initial VFs: 8, Total VFs: 8, Number of VFs: 8, Function Dependency Link: 01

  VF offset: 384, stride: 4, Device ID: 1520

  Supported Page Size: 00000553, System Page Size: 00000001

  Region 0: Memory at 00000000c0040000 (64-bit, prefetchable)

  Region 3: Memory at 00000000c0060000 (64-bit, prefetchable)

  VF Migration: offset: 00000000, BIR: 0

  Capabilities: [1a0 v1] #17

  Capabilities: [1d0 v1] Access Control Services

  ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  Kernel driver in use: igb

  Kernel modules: igb

$ modinfo igb

filename:       /lib/modules/2.6.33.5-112.fc13.i686.PAE/kernel/drivers/net/igb/igb.ko

version:        5.3.3.5

license:        GPL

description:    Intel(R) Gigabit Ethernet Network Driver

author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>

srcversion:     F03F0C4A4602E651FFBECFA

alias:          pci:v00008086d000010D6sv*sd*bc*sc*i*

alias:          pci:v00008086d000010A9sv*sd*bc*sc*i*

alias:          pci:v00008086d000010A7sv*sd*bc*sc*i*

alias:          pci:v00008086d000010E8sv*sd*bc*sc*i*

alias:          pci:v00008086d00001526sv*sd*bc*sc*i*

alias:          pci:v00008086d0000150Dsv*sd*bc*sc*i*

alias:          pci:v00008086d000010E7sv*sd*bc*sc*i*

alias:          pci:v00008086d000010E6sv*sd*bc*sc*i*

alias:          pci:v00008086d00001518sv*sd*bc*sc*i*

alias:          pci:v00008086d0000150Asv*sd*bc*sc*i*

alias:          pci:v00008086d000010C9sv*sd*bc*sc*i*

alias:          pci:v00008086d00000440sv*sd*bc*sc*i*

alias:          pci:v00008086d0000043Csv*sd*bc*sc*i*

alias:          pci:v00008086d0000043Asv*sd*bc*sc*i*

alias:          pci:v00008086d00000438sv*sd*bc*sc*i*

alias:          pci:v00008086d00001516sv*sd*bc*sc*i*

alias:          pci:v00008086d00001511sv*sd*bc*sc*i*

alias:          pci:v00008086d00001510sv*sd*bc*sc*i*

alias:          pci:v00008086d00001527sv*sd*bc*sc*i*

alias:          pci:v00008086d0000150Fsv*sd*bc*sc*i*

alias:          pci:v00008086d0000150Esv*sd*bc*sc*i*

alias:          pci:v00008086d00001524sv*sd*bc*sc*i*

alias:          pci:v00008086d00001523sv*sd*bc*sc*i*

alias:          pci:v00008086d00001522sv*sd*bc*sc*i*

alias:          pci:v00008086d00001521sv*sd*bc*sc*i*

alias:          pci:v00008086d00001539sv*sd*bc*sc*i*

alias:          pci:v00008086d0000157Csv*sd*bc*sc*i*

alias:          pci:v00008086d0000157Bsv*sd*bc*sc*i*

alias:          pci:v00008086d00001538sv*sd*bc*sc*i*

alias:          pci:v00008086d00001537sv*sd*bc*sc*i*

alias:          pci:v00008086d00001536sv*sd*bc*sc*i*

alias:          pci:v00008086d00001533sv*sd*bc*sc*i*

alias:          pci:v00008086d00001F45sv*sd*bc*sc*i*

alias:          pci:v00008086d00001F41sv*sd*bc*sc*i*

alias:          pci:v00008086d00001F40sv*sd*bc*sc*i*

depends:        dca

vermagic:       2.6.33.5-112.fc13.i686.PAE SMP mod_unload 686

parm:           InterruptThrottleRate:Maximum interrupts per second, per vector, (max 100000), default 3=adaptive (array of int)

parm:           IntMode:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2 (array of int)

parm:           Node:set the starting node to allocate memory on, default -1 (array of int)

parm:           LLIPort:Low Latency Interrupt TCP Port (0-65535), default 0=off (array of int)

parm:           LLIPush:Low Latency Interrupt on TCP Push flag (0,1), default 0=off (array of int)

parm:           LLISize:Low Latency Interrupt on Packet Size (0-1500), default 0=off (array of int)

parm:           RSS:Number of Receive-Side Scaling Descriptor Queues (0-8), default 1, 0=number of cpus (array of int)

parm:           VMDQ:Number of Virtual Machine Device Queues: 0-1 = disable, 2-8 enable, default 0 (array of int)

parm:           max_vfs:Number of Virtual Functions: 0 = disable, 1-7 enable, default 0 (array of int)

parm:           MDD:Malicious Driver Detection (0/1), default 1 = enabled. Only available when max_vfs is greater than 0 (array of int)

parm:           QueuePairs:Enable Tx/Rx queue pairs for interrupt handling (0,1), default 1=on (array of int)

parm:           EEE:Enable/disable on parts that support the feature (array of int)

parm:           DMAC:Disable or set latency for DMA Coalescing ((0=off, 1000-10000(msec), 250, 500 (usec)) (array of int)

parm:           LRO:Large Receive Offload (0,1), default 0=off (array of int)

parm:           debug:Debug level (0=none, ..., 16=all) (int)

I have two Dell r720 VMware hosts, and a Thecus n12000 Pro NAS. I just put an x540-t2 in each. They are connected through a Netgear ProSafe XS708e switch. There are no other devices on the network.

In all three machines, the port nearest the PCI is running 10Gb, and the other port is at 1Gb. The lights on the cards, and on the switch, all agree with this. One yellow, one green, for each endpoint.

How do I get both ports on these cards to run 10Gb?

All:

    I am trying to get a dual 40G Xl710-QDA2 interface up with i40e.ko to drive them up,but failed.

    I found some use message like that:

[root@linux src]# dmesg |tail

[75592.003591] i40e 0000:04:00.1: irq 200 for MSI/MSI-X

[75592.127531] i40e 0000:04:00.1: irq 201 for MSI/MSI-X

[75592.251468] i40e 0000:04:00.1: irq 202 for MSI/MSI-X

[75592.362414] i40e 0000:04:00.1: irq 203 for MSI/MSI-X

[75592.486353] i40e 0000:04:00.1: irq 204 for MSI/MSI-X

[75592.789203] i40e 0000:04:00.1: PCI-Express: Speed 8.0GT/s Width x8

[75592.966116] i40e 0000:04:00.1: Features: PF-id[1] VSIs: 66 QP: 24 RX: 1BUF RSS FD_ATR FD_SB NTUPLE VxLAN NVGRE PTP VEPA

[75617.228339] i40e 0000:04:00.0 eth6: the driver failed to link because an unqualified module was detected.

[75617.343091] 8021q: adding VLAN 0 to HW filter on device eth6

[75617.410885] i40e 0000:04:00.0 eth6: adding 68:05:ca:32:45:e8 vid=0

[root@linux src]# lspci |grep Eth

01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe

01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe

02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe

02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe

04:00.0 Ethernet controller: Intel Corporation Device 1583 (rev 01)

04:00.1 Ethernet controller: Intel Corporation Device 1583 (rev 01)

05:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)

05:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)

[root@linux src]# ethtool -i eth6

driver: i40e

version: 1.4.25

firmware-version: 4.42 0x80001932 0.0.0

bus-info: 0000:04:00.0

[root@linux src]# uname -a

Linux xgw-6 3.10.10-DPDK-1-0-0-0 #4 SMP Mon Mar 7 19:07:38 CST 2016 x86_64 x86_64 x86_64 GNU/Linux

QSFP+ Fiber Module is Gigalight GQS-MD0400-007C AOC Cable 7M.

So why can not link up with this QSFP+？

Hi,

can any one help me in find old stm-1 tranciever which was part of INFENION after Lantiq Gmbh  own these product after INtel owned lantiq now can any one intel help me for these product or any other which was similar of these .compatible like these in properties   Infineon AG  STM-1 01769527  V50017-R60-K802   Infineon AG  Stm-1 99669123  V50017_R60-K802

  regrds

shahroz

compass pakistan

Hi,I havean Intelnetwork adapterEthernetServerAdapterX520-DA2,

you knowif it iscompatible withNexenta CE version 3.1.6 FP3

I tried toadd itbutdo not see itfrom the availableadapters.

Withthe lspci-vcommanddisplays the following information. They can be useful?
Thank you

Paolo

07:00.0 Ethernet controller: Intel Corporation Unknown device 1572 (rev 01)

        Subsystem: Intel Corporation Unknown device 0007

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at f8000000 (64-bit, prefetchable)

        Memory at f7ff8000 (64-bit, prefetchable)

        Expansion ROM at fbb00000 [disabled]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable-

        Capabilities: [70] MSI-X: Enable- Mask- TabSize=129

        Capabilities: [a0] Express Endpoint IRQ 0

        Capabilities: [e0] Vital Product Data

07:00.1 Ethernet controller: Intel Corporation Unknown device 1572 (rev 01)

        Subsystem: Intel Corporation Unknown device 0000

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at f9800000 (64-bit, prefetchable)

        Memory at f97f8000 (64-bit, prefetchable)

        Expansion ROM at fbb80000 [disabled]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable-

        Capabilities: [70] MSI-X: Enable- Mask- TabSize=129

        Capabilities: [a0] Express Endpoint IRQ 0

        Capabilities: [e0] Vital Product Data