Hi,

I'm having one of the strangest audio problems I've ever seen on my PC right now, which seems to be linked to my internet connection (of all things), which uses an intel network driver.

First off I'm the sort of PC user that likes to leave the system on 24/7 and power off the displays when not in use, as this allows me to run certain background tasks (like automated file backups) overnight.

After leaving my system running for a few days I started to notice an erratic popping noise in my audio, a bit like static, but not as consistent. After doing some research online, I learned about something called DPC latency and used a program called 'DPC Latency Monitor' to try and diagnose the problem.

The data I collected pointed to my Intel network driver as a possible culprit for my audio issues, so I tried disabling the corresponding network adapter from the network and sharing center, and re-ran the latency test. The results with the network adapter disabled were greatly improved, and I could no longer hear the popping noises when listening to offline audio.

As soon as I re-enable the network adapter the problem returns, and so far the only solution I have is to randomly reboot my system, which I find rather inconvenient, as it also requires me to save all data in all open programs, exit out of everything, and then open it all back up again later.

I've already used Intel's driver update utility to ensure I'm on the latest drivers, and am unsure of what to do next.

The following is a compilation of the data I collected while trying to figure things out:

DPC latency monitor data, with network adapter enabled and before a system reboot:

With network adapter disabled and before reboot:

Network adapter enabled, after reboot:

Output from Intel system support utility:

I have install a XL710-QDA2 on a supermicro server and have setup the NIC with 4x10 through the EFI utlity QCU.

I would like to connect the server to my HP 5412zl switch, but so far no luck just "port status = down"

So my question is:

Can I connect the X4DACBL3 to the HP 5412zl module j9536a?

I need to upgrade an old Win2000 Advanced Server to 10Gb Ethernet with Cat 6A wire.

The motherboard is a Tyan bi-Opteron 2216 with PCI Express connectors.

Has anyone a solution ?

Thanks for the return

Emmanuel

My distributor listed this 10Gb NIC as PC compatible. Windows 10 does not even acknowledge the card.

I install X520-DA1 in two Windows 7 PCs, with 10Gbase-SR transceiver and an OM3 multi-mode fiber connected together.

I use iperf to test the speed, no matter how I tuned it, it can only run about 1.3 Gbps, I know it's for direct-attach cable, but wonder if this card not support using fiber connected?

Greetings,

A recently acquired motherboard has an on-board Intel i219-V NIC. Within a fresh Win7 Pro SP1 x64 install with latest Intel drivers (driver v12.15.23.1, PROSet v21.0.504.0), I am experiencing stability issues with this NIC when a specific combination of factors are met:

1. NIC is set to any Link Speed above 10Mbps Full Duplex (100M-Full, 1G-Full, & Auto Negotiate)

2. Steam (the application from Valve) is downloading application and/or game updates

Basically once Steam starts its updates and reaches about 1MB/s transfer rate, the link drops and the whole computer loses its network connection (LAN and WAN) - all LAN ARP entries are flushed, cannot ping local gateway router, Windows shows the little yellow triangle over the network icon (link but no L2/L3, self-assigned 169 address)

Once this issue occurs, it is resolvable in only two ways:

- Reboot the computer

- Change the Link Speed settings under the NIC's Device Properties page in Device Manager. It doesn't matter what I set it to, just the action of re-setting this parameter is enough to re-negotiate the link again, it seems.

The only workaround that I've found so far is to manually set the NIC Link speed to 10Mbps Full - the NIC is stable (albeit much slower) in this configuration.

Other Troubleshooting & Notes:

- No other application or traffic type seems to result in this behavior. For example, speed tests, iperf tests, torrent, etc all max out my WAN (not LAN) with ease, without the NIC dropping the link

- Replaced relevant CAT6 patch cables (all test good as well)

- Tested different port on LAN switch (NIC is connected directly to an enterprise HP ProCurve switch)

- Tested with switchport speed/duplex settings always matching NIC Link Speed settings (100M-Full, 10M-Full, etc)

Edit: I tested with a USB3.0 Ethernet adapter, and Steam has no issues maxing out the ISP without the link dropping. All other equipment is the same and configured the same.

Hello, I would like to know if there is documentation which would state how to increase the buffer settings for this card on Windows 7 and Windows 10 workstations.  We are looking to find the high and low limits.

Hello, there.

This morning I upgraded my fully functionnal Windows 8.1 Enterprise installation to Windows 10 Technical Preview. Before that, I downloaded the Intel Network Adapter Driver from this website, version 20.1, for Windows 10 64 bits. After the driver installation, I had the VLANs tab in the network card properties. However, i'm unable to create a VLAN. The network card is automatically disabled then I receive an error message saying this (translated from french):

One or more vlans could not be created. Please check the adapter status and try again.

The window freezes and I have to force-close it. 802.1 option is of course enabled in the Advanced options tab. The event viewer always shows the same error when I try to create a VLAN:

Nom de l’application défaillante NCS2Prov.exe, version : 20.1.1021.0, horodatage : 0x554ba6a4

Nom du module défaillant : NcsColib.dll, version : 20.1.1021.0, horodatage : 0x554ba57d

Code d’exception : 0xc0000005

Décalage d’erreur : 0x0000000000264064

ID du processus défaillant : 0x19d4

Heure de début de l’application défaillante : 0x01d0ada33fd50576

Chemin d’accès de l’application défaillante : C:\Program Files\Intel\NCS2\WMIProv\NCS2Prov.exe

Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\NcsColib.dll

ID de rapport : eefb5842-9220-4bad-93d3-774828c5736e

Nom complet du package défaillant :

ID de l’application relative au package défaillant :

I already tried to uninstall all the packages and drivers related to the network card. I deleted fantom network cards then cleaned up the registry. I tried to set some compatibility options to the given executable file, with no success. I tried to reinstall the driver with Drivers Signature disabled, tried to disable IPv4/IPv6 from the network card before trying to add a VLAN... I tried everything I found on Google.

Could someone help me, please?

Does the Intel XL710 4x10GE card support the processing of VLAN frames that have are tagged with STAGs (TPID == 0x88a8) instead of CTAGs (TPID == 0x8100)?   In my lab, I have tried a number of things to enable the processing of STAG frames on the XL710 board, including setting up the ethernet interface with commands such as the one below, but no luck, the interface will still not see the VLAN frames with a TPID of 0x88a8.  Frames tagged with CTAGs are processed just fine however.

$ sudo ip link add link enp1s0f0 name enp1s0f0.4004 type vlan protocol 8021.ad id 4004

Also, I have tried to setup the board in both promiscuous mode and true promiscuous mode.  Again, no joy, the board still refuse to detect/receive a VLAN tagged frame if the TPID is 0x88a8 instead of 0x8100.  By the way, for true promiscuous mode, I am using this command.

$ sudo ethtool --set-priv-flags enp1s0f0 vf-true-promisc-support on

I have the latest Intel firmware installed on this board and am using the latest Intel kernel module for this board.

$ sudo ethtool -i enp1s0f0

[sudo] password for nknuth:

driver: i40e

version: 1.5.16

firmware-version: 5.04 0x800024ca 0.0.0

expansion-rom-version:

bus-info: 0000:01:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

Alas, when I query the features of this ethernet board, it seems clear that STAG frames are not supported.

$ sudoethtool -k enp1s0f0

...

tx-vlan-stag-hw-insert: off [fixed]

rx-vlan-stag-hw-parse: off [fixed]

rx-vlan-stag-filter: off [fixed]

...

Any help is appreciated.  It really is a show stopper for my company to not be able to process STAGs on the XL710 boards.  We were using the 2 port 10GE boards that use the ixgbe kernel module and STAG frames were processed on those boards without issue.

Thanks in advance for any clarity here.

Nathan

I have two computers, each with a XL710-QDA2, currently running Windows Server 2016 Tech Preview 5.

Is it possible to directly connect these two with the QSFP+ cable?

This does not seem to be working for me

where could find intel i211-at ethernet linux driver ? (02:00.0 Class 0200: Device 8086:1532 (rev 03))

igb-5.3.5.3.tar.gz does not include support intel i211-at device

i need porting it to intel braswell android 5.1.1

Thanks.

Been having some problems with my Ethernet Connection.

http://prntscr.com/bywd09

and when i try to check for updates it just tells me i'm already using the lates version, I've been using an Old WiFi adapter i had in my old Computer. i really want to start using Ethernet again. Help. Please

http://prntscr.com/bywdsy

http://prntscr.com/bywe1x

Hello,

I bought a two-port Intel I350 NIC (vendor says "Generic i350-t2 V2"), and I wish to enable its critical session feature (also known as veto bit, keep PHY link up, and manageability session). However, it is not in a classic server installation, but rather in a simple desktop computer - I have my reasons for this, namely to be able to put the computer in suspend-to-RAM sleep state - which means there is no BMC as far as I know.

From the datasheet, I understand the BMC would send through SMBus a specific command to enable this feature. What I'd want is to send this command from the Linux kernel instead. As of now, I see two SMBus devices in '/dev', which are identified as "igb BB", so I guess they correspond to the two ports of the card, but I have not been able to send the command to either device. As a matter of fact, I cannot detect any slave on each device (using command i2cdetect). My try program results in an error, which code from errno is "ENXIO (6): no such device or address" when I send the command. Opening the device and setting the slave address to 0x49 "works" (in the sense it gives me no error).

So Tl;Dr: I want to send a manageability command through SMBus (or NC-SI if it'd work) without BMC, but rather from my Linux kernel or user-space. Is that even possible? If yes, how do I enable the NIC slave device?

Thanks for your help

ISP has IPV6 enabled and I noticed my desktop PC stopped getting Windows updates.

After much digging and test, I found out that my NIC was dropping TCP packet on the receive from Windows Update. After disabling all Offloading options and enabling options one by one, I was able to narrow it down to TCP RX was the culprit.

Windows 10 1607 x64

Intel I217-V 12.15.23.1 (5/10/2016)

Not sure if anyone else has seen this issue? Windows Update log showed it never received a HTTP response back from Microsoft.

2016/08/08 22:32:43.3589251 1416  12388 WebServices     WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

2016/08/08 22:32:43.3589262 1416  12388 WebServices     WS error: There was an error receiving the HTTP reply.

2016/08/08 22:32:43.3589268 1416  12388 WebServices     WS error: The connection with the remote endpoint was terminated.

2016/08/08 22:32:43.3589280 1416  12388 WebServices     WS error: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

2016/08/08 22:32:43.3589289 1416  12388 WebServices     WS error: There was an error receiving the HTTP reply.

2016/08/08 22:32:43.3589297 1416  12388 WebServices     WS error: The operation did not complete within the time allotted.

2016/08/08 22:32:43.3589493 1416  12388 WebServices     WS error: The connection with the server was terminated abnormally

2016/08/08 22:32:43.3589508 1416  12388 WebServices     Web service call failed with hr = 80240440.

This was one of many things that didn't work correctly when TCP RX Checksum offload was enabled.

Thanks!

Customer looking for available of EPS for Fisher Flat adapter card model XL710-QDA2.

I know that teaming is not supported for WIndows 10 at the moment by Intel drivers but maybe someone will have some info about my problem.

I am trying to set NIC (I350) teaming in active/passive configuration - 2 NICs are connected, if link to one goes down, the other takes over.

So, I have Windows 10 Enterprise machine with 4 onboard NICs. I am currently using only 2.

I have successfully teamed 2 NICs by using the following command:

New-NetLbfoTeam -Name Team -TeamMembers ethernet1,ethernet2

Everything works that way but that is active/active configuration which doesn't work for me. I need active/passive configuration.

I've tried to do that by using the following command:

Set-NetLbfoTeamMember -Name ethernet1 -AdministrativeMode Standby

this command fails with the following error:

Set-NetLbfoTeamMember : One or more parameter values passed to the method were invalid.
At line:1 char:1
+ Set-NetLbfoTeamMember -Name eth1 -AdministrativeMode Standby
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (MSFT_NetLbfoTea...DBCB57F957E4}"):root/StandardCi...tLbfoTeamMember) [Set-NetLbfoTeamMember], CimException
    + FullyQualifiedErrorId : MI RESULT 4,Set-NetLbfoTeamMember

Putting the names in quotes doesn't help either.

Powershell is running with administrator privileges, all NICs are from the same chipset and I can not use Intel teaming because it is not supported on Windows 10 ("Intel(R) Advanced Network Services (Intel(R) ANS) Teams and VLANs are not supported on Microsoft* Windows* "). There is a sample of that cmdlet from the Microsoft page which is essentially the same so I don't think that the syntax is incorrect - "Set-NetLbfoTeamMember -Name "NIC4" -AdministrativeMode Standby"

I have checked this page for the reference but without any help - https://technet.microsoft.com/en-us/library/jj130857(v=wps.630).aspx

Long story short - I can put 2 NICs in a team but can not make one passive.

Any suggestions?

Hi,

While running our application in windows 2008 R2 server some random BSOD are happening.

On analyzing the dump it points to a call from elr62x64.sys and then fails in tcpip.sys. Since tcpip.sys is a system file, we would like to understand if there is any known bug from NIC card driver.

the NIC card details:

Intel R Gigabit 2P I350-t Adapter.

The current driver version  details in the server machine where BSOD's surfaced :

1) erl62x64.sys - 12.13.27.0 (Date : 6/5/2015)

2) tcpip.sys - 6.1.7601.22950 (Date: 2/5/2015)

3) NDIS.sys - 6.1.7601.23235 (Date : 10/13/2015)

4) ad.sys - 6.1.7601.23237 (Date: 10/14/2015)

Also the call stack obtained from dump file is as follows:

STACK_TEXT: 

fffff800`03650158 fffff800`01e80e69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffff800`03650160 fffff800`01e7fae0 : 00000000`00000000 00000000`00000000 fffffa80`481a2000 fffff800`03650640 : nt!KiBugCheckDispatch+0x69

fffff800`036502a0 fffff880`01a6606b : 00000000`00000716 fffff800`03650640 fffffa80`2138dcf0 fffff800`03650640 : nt!KiPageFault+0x260

fffff800`03650430 fffff880`01a643c6 : 00000000`71f8da89 fffffa80`2aaced70 00000000`00000000 fffffa80`2aacee38 : tcpip!TcpSegmentTcbSend+0x17b

fffff800`03650530 fffff880`01a685d9 : fffffa80`2a9d5360 fffff880`01a8c89b fffffa80`1d81ad30 00000000`000025bc : tcpip!TcpBeginTcbSend+0xa66

fffff800`036507b0 fffff880`01a69450 : fffffa80`000000ba 00060000`00000006 00000000`00000000 00000000`00004800 : tcpip!TcpTcbSend+0x1d9

fffff800`03650a30 fffff880`01a681a8 : 00000000`00000000 00000000`00000000 fffff800`03650c50 fffff800`03650d30 : tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0xa0

fffff800`03650a60 fffff880`01a6836b : fffffa80`00000004 fffffa80`1cc0a924 00000000`00004800 fffff800`03650ba0 : tcpip!TcpEnqueueTcbSend+0x258

fffff800`03650b10 fffff800`01e8e1f8 : fffff800`03650bd8 00000000`00000000 fffffa80`1d1ed7b8 fffff800`03650bd8 : tcpip!TcpTlConnectionSendCalloutRoutine+0x1b

fffff800`03650b40 fffff880`01a6922a : fffff880`01a68350 fffffa80`1d81af20 00000000`00000502 fffff880`01a68e00 : nt!KeExpandKernelStackAndCalloutEx+0xd8

fffff800`03650c20 fffff880`0436b7be : fffffa80`3934f3e0 fffffa80`1fd537e0 fffffa80`1fd537e0 fffffa80`1fd537e0 : tcpip!TcpTlConnectionSend+0x7a

fffff800`03650c90 fffff880`0436f7b4 : fffffa80`1ffa4b50 fffff880`01a70000 fffffa80`389cc280 fffff800`03650f00 : afd!AfdTLTPacketsSend+0x47e

fffff800`03650e20 fffff880`0436fe83 : fffffa80`48c0b110 00000000`00000001 fffffa80`1c78a380 fffffa80`1ffa4cf8 : afd!AfdTPacketsSend+0x64

fffff800`03650e90 fffff880`01a4e9c0 : 00000000`00010000 fffffa80`1b4930a0 fffffa80`1f705e90 fffff800`03651158 : afd!AfdCommonRestartTPacketsSend+0x173

fffff800`03650ec0 fffff880`01a64fa8 : 00000000`00000000 fffff800`03651158 fffffa80`1b4930a0 fffff880`00000000 : tcpip!TcpCompleteTcbSend+0x40

fffff800`03650ef0 fffff880`01a6299a : fffffa80`2138dcf0 fffffa80`38854000 fffffa80`1b0a3400 fffffa80`1b6202a0 : tcpip!TcpTcbReceive+0x3ec

fffff800`03651000 fffff880`01a637fc : fffffa80`1cc457ac fffffa80`1b4930a0 fffffa80`1b4930a0 00000000`00000000 : tcpip!TcpMatchReceive+0x1fa

fffff800`03651150 fffff880`01a4667c : fffffa80`1b4946f0 00000000`00000000 fffffa80`00000004 fffffa80`1c745740 : tcpip!TcpPreValidatedReceive+0x49c

fffff800`03651220 fffff880`01a57712 : fffffa80`1c7c3010 fffffa80`1c783ba0 fffffa80`1c780006 00000000`00000006 : tcpip!IpFlcReceivePreValidatedPackets+0x5bc

fffff800`03651380 fffff800`01e8e1f8 : 00000000`00000000 00000000`00004800 fffff800`0200ecc0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2

fffff800`036513d0 fffff880`01a57e42 : fffff880`01a57670 fffff880`01a6959a 00000000`00000002 fffffa80`1b0c0d00 : nt!KeExpandKernelStackAndCalloutEx+0xd8

fffff800`036514b0 fffff880`00ee20eb : fffffa80`1c773010 00000000`00000000 fffffa80`1c6bd1a0 00000000`0000f800 : tcpip!FlReceiveNetBufferListChain+0xb2

fffff800`03651520 fffff880`00eabad6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NDIS!ndisMIndicateNetBufferListsToOpen+0xdb

fffff800`03651590 fffff880`00e25ac1 : fffffa80`1c6bd1a0 00000000`00000002 00000000`00000004 00000000`00000000 : NDIS!ndisMDispatchReceiveNetBufferLists+0x1d6

fffff800`03651a10 fffff880`05382f33 : fffffa80`481a2000 00000000`00000004 fffffa80`1a00caa0 fffffa80`481a2dc0 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc1

fffff800`03651a60 fffff880`05383101 : 00000000`00000001 fffffa80`1a00caa0 fffffa80`1c6c3e20 fffffa80`481a2000 : e1r62x64+0x23f33

fffff800`03651aa0 fffff880`053746e6 : 00000000`00000000 fffffa80`481a2040 00000000`00008000 ffff821b`00000000 : e1r62x64+0x24101

fffff800`03651b20 fffff880`053744a0 : fffffa80`1b8b7730 ffff0001`00000000 ffff0001`00000000 fffff880`00eab488 : e1r62x64+0x156e6

fffff800`03651b90 fffff880`05376628 : 00000000`00000000 ffff0001`00000000 00000000`00000000 00000000`00000000 : e1r62x64+0x154a0

fffff800`03651c00 fffff880`00e25951 : 00000000`001bbf1e 00000000`00000000 00000000`00000000 fffff800`0364b080 : e1r62x64+0x17628

fffff800`03651c40 fffff800`01e8d1dc : fffffa80`1cbb9918 00000023`00000000 00000000`00000000 fffff800`02000e80 : NDIS!ndisInterruptDpc+0x151

fffff800`03651cd0 fffff800`01e795ca : fffff800`02000e80 fffff800`0200ecc0 00000000`00000000 fffff880`00e25800 : nt!KiRetireDpcList+0x1bc

fffff800`03651d80 00000000`00000000 : fffff800`03652000 fffff800`0364c000 fffff800`03651d40 00000000`00000000 : nt!KiIdleLoop+0x5a

Please let us know if we were using older version of driver which leads to this error. If so please specify where to get the latest.

Also from the windows event viewer we got event as Microsoft.WIndows.Kernal.General with event ID as 12 sometimes and 41 sometimes and even 1 sometimes.

thanks.

Muralidhar

Hi,

I recently bought an i350 ethernet controller. I would like to enable the "critical manageability session" of the card, but I can't find any documentation that explains how to do that. The only document related to my question is https://www-ssl.intel.com/content/dam/www/public/us/en/documents/guides/maintaining-the-ethernet-link-to-the-BMC.pdf#pag…  which says to refer to the i350 documentation. I did... but I was not able to find any concrete information in it. Any hint?

Thanks!

Hi,

my Supermicro X10SRL-F has two onboard I210 NICs. Two days ago, after having it passed one through to a PFSense VM with KVM, they now show up under Linux as

07:00.0 Ethernet controller: Intel Corporation Device 1531 (rev 03)

08:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network  Connection (rev 03)

Only the second one is detected, the first one is missing in the BIOS, too. I've had the problem before and solved it by re-flashing the firmware which was provided by Supermicro support. I'm not certain about the circumstances back then, but it's possible that it was related to pass-through, too. However, it does not seem to be easily reproducible as the same setting has worked flawlessly several times before. Before trying to re-flash the firmware as advised by Supermicro, I'd like to ask if

- this is a known problem (I couldn't really find related reports) and if yes how it can be avoided

- you could use a firmware dump to get an idea of the problem / cause

Of course, any other helpful information is appreciated! The NIC was running with firmware Rev 1.24 (05/21/2013), they've sent me Rev. 1.27A (8/27/2015) to test.

With regards

N0T3P4D

hi, i would like to report that the new intel nic drivers version 19.3 that just released recently has huge 6000+ dpc latency spike once in a few secs.

my specs

Intel(R) 82579LM Gigabit Network Connection

windows 7 SP1 32bit + lastest windows update

i downgrade to intel nic drivers previous version 19.1 and the problem is just gone.