Hello,

I tested hardware filters on my Ubuntu+82599 development environment and everything seemed to work great. I've further read Intel and ethtool documentation, but I've been unable to find a solution to my next question. I've got a DNS analysis tool and I would like to only accept UDP packets sent to/from 53 port (DNS request/responses) and drop everything else. In your opinion, is by any means possible to implement a hardware filter like this one (drop all non-UDP packets and not sent to 53 port) below:

ethtool --config-ntuple eth4 flow-type !udp4 dst-port !53 action -1

Thanks in advance and best regards,

Manuel Polonio

Hi!

     My servers use  82599ES 10-Gigabit adaptor.

I want to poll the register for the Tx/Rx interrupt events (MSI-x mode). From the 82599 datasheet, i know the registers are  EICR(1) and EICR(2) . But i can not get the addresses of EICR(1) and EICR(2).

Can everybody give the the addresses of EICR(1) and EICR(2) to me? Thanks.

Hello,

am from Lithuania, Europe. Have wired LAN internet (direct to PC, no wireless), 100 Mbps download/upload both to Lithuania and abroad. Dell Latitude 6530 HG7RWW1, Windows Firewall, Nod 32, Windows 7 64 bit. Noticed my upload to Europe is only 5-6 Mpbs, to Lithuania - 80-90 Mbps. Download is 80-90 Mbps to everywhere in Europe. Disabled firewall and Nod - 32 nothing changed. Scanned with Nod 32 and Malwarebytes - nothing. Can't understand, where the reason is.

Also have to note my first hop of tracert always gives time outs, so time outs for DHCP. Contacted my ISP, they came, turned their PC on and got 80-90 Mbps upload. Told problem was on my side and left.

Then decided to update all drivers, unfortunately got this even tried many times (see attachment).

Also noticed my network card's 812579 LM driver is 16.8.45.0 from February 21st, 2013, but when I try to search for driver update, system says your driver is up to date, which is very strange - how 3 years old driver could be up to date?

Any ideas on upload speed and drivers update?

Hi all,

Help me please. I need to create a driver of the framebuffer for SPI lcd with controller ILI9341.

I found drivers of the framebuffers for a lot different displays https://github.com/notro/fbtft, but I codn't integrate it.

I did the same how in the example https://hackaday.io/project/7025/logs, but I coudn't compile the driver from this example.

If some body did it, help me please, give me example if you have, I can pay if need.

Thanks.

Hello,

Can someone point me in the right direction or a KB article or explain what is the different between the different Intel Boot Agents.

Recently I've been seeing the following:

CL

GE

FE

Is there a matrix that explains the differences?

Or could be be product developments, FE became GE which became CL  (or something like that)

Thanks

Hello,

Hardware:

ASUS P8Z77-V PRO

Intel 82579V Network Adapter

I wanted to change MAC address and accidently flashed eeprom with wrong files from here:

http://www.insanelym...-quo/?p=2029530

Flashed lan.eep imagefile for Intel 82574L with eepupdate command.

I have Intel 82579V

82579V(my) -> 82574L(wrong)

So now my controller is shown as 82574L and doesnt work.

Please suggest how can I fix, restore back my 82579V eeprom?! Do I need dump? How can I restore eeprome?
Someone can please provide Intel 82579V dump .eep image file?

Thanks!

Hi,

Do the I217-LM and the I210-IT support link aggregation (IEEE 802.3ad) ?

It seems that chips built on AMT technology do not support link aggregation:

82574L and 82579LM Link Aggregation

Regards,

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?

Hi you all,

I'm trying to install the 82578DC module on my 4.3 kernel however the procedure is not working properly. As you can see below.

root@test:~/Desktop/e1000e-3.3.3/src# make install

Makefile:67: *** Kernel header files not in any of the expected locations.

Makefile:68: *** Install the appropriate kernel development package, e.g.

Makefile:69: *** kernel-devel, for building kernel modules and try again.  Stop.

Thanks in advance.

Hi,

I tried to download "Intel Ethernet Connection CD 20.7" to install the driver on my WHS 2011 server. The installation fails with something like "Intel ethernet adapter not found". Are there no drivers for this Windows Server? The ethernet adapter is a onboard solution of a motherboard with Z170 chipset.

Thanks,

anve

Hello,

after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.

Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.

However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.

Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.

Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.

Thanks in advance!

Kind regards,

Famaku

Greetings Intel Community,

I have several systems that experience a system panic with a currently unknown cause. The brief overview of the configuration is:

OS: SLES 11 SP 4

Kernel: 3.0.101-68-default

ixgbe driver (inbox): 3.19.1-k

Adapter: Each server has two dual-port X520-SR2 networking adapters installed (4x10G ports total, 2 physical adapters)

Configuration: all 4 interfaces under bond0 in mode=802.3ad (lacp) to a managed switch with the matching configuration

Note #1: We've seen the crashes on sles11sp3 (as well as RHEL systems too), different kernels, and different ixgbe drivers. This is just the current configuration that is experiencing the issue.

Note #2: Load & types of traffic don't seem to matter, the system can crash with or without load, the crash has happened with just a SSH session open.

With some crash dump information, it seems that the adapters have issues with "IOH timeouts" and we also see "CATERRs".

0x000A:IOH: D3_IOBAS_IOLIM_SSTS @ 0x00000181C = 0x0000000040006060

0x000A:IOH: D3_IOBAS_IOLIM_SSTS:SIGSYSTEMERROR <30> = 0x1

0x000A:IOH: D3_IOBAS_IOLIM_SSTS:IOBASEADDRLIMIT <15:12> = 0x6

0x000A:IOH: D3_IOBAS_IOLIM_SSTS:IOBASEADDR <7:4> = 0x6

Also...

0x0024 r002i23b02 IOH on IP93-5 sn RPM031 10 Stuck RH Tracker Entry - IOH (6 total on this node)

0x003E r002i23b15 IP93-5 sn RRB997 9 RH H0 detected TRB Timeout - Destination Node

0x0004 r002i01b02 SKT0 on IP93-5 sn RPX686 8 RH H0 detected TRB Timeout - Requester

0x0000 r002i01b00 IP93-5 sn RPJ019 7 RH H0 detected TRB Timeout - Destination Node

What I'm hoping to get is a method to further debug what is happening with the driver during a system crash, is there a way to build the ixgbe driver with debugging options that generate information that could be useful to understanding the problem more.

I'm also wondering if anyone has any suggestions for kernel parameters that might help these types of issues.

Thanks for any input.

I use original network card Intel 82574L (EXPI9301CTBLK). After the upgrade, with the built-in "Windows 7 x64" driver 11.0.5.22 to the last 12.7.28.0 there are delays in downloading web pages. There is a general slowdown. Why are there new drivers slow down? After roll back to version 11.0.5.22 everything becomes normal.

PS And in the driver confused modes FullDuplex (Half) and HalfDuplex (Full).

<><> Apologies if this has been posted in the wrong place <><>

Ok I'll keep this brief.

Problem:- LAN regulary disconnects and reconnets 30 seconds later.

Symptons:- Loose connection to Lan / Internet for around 30 seconds.

Background:- Had this problem with both P8P67 B2 and P8P67 pro boards. I have several other computers connected to the switch (not hub) and they are working fine. Have replaced the lead to no avail. Have even used the same lead in several other computers which works fine.

Config:-

Study

Netgear 8 port SWITCH 10/100/1000
Server
VOIP
PC

Switch connected to lounge hard wired via outdoor sheilded cat6 lead.

Lounge

Netgear 8 port SWITCH 10/100/1000
Router
XBOX 360
Wii
<><><>

Message in System Event Logs;-

<><>
Warning message - date time - source = e1cexpress
Event ID = 27

Intel 82579V Gigabit Network Connection
- Network link is disconnected
<><>

Then it states its connected again.

Have also tried the following;-

Remove Kaspersky 2011
Ensure ALL power management even OS is disabled
Use IPV4 instead of IPv6 in prefix policies
Disable nativue IPv6
Disable tunnel IPv6
Disable IPv6

netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
netsh int ip set global taskoffload=disabled

Disabled SNP;-
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
EnableTCPChimney=dword:00000000
EnableTCPA=dword:00000000
EnableRSS=dword:00000000

Have tried driver from Asus MB CD, Asus Website, Your Website, Windows Update all to no avail.

Please help.

The 40Gb modes can no longer be selected using the qcu64e utility since the firmware upgrade from 4.42 to 5.02. Only 4x10 and 2x2x10 options are offered but the XL710-QDA2 card is QSFP+ capable.

# qcu64e /NIC=1 /INFO

Intel(R) QSFP+ Configuration Utility

QCU version: v2.26.17.06

Copyright(C) 2015 by Intel Corporation.

Software released under Intel Proprietary License.

Adapter supports QSFP+ Configuration modification.

Current Configuration: 4x10

Supported Configurations:

4x10

2x2x10A (Top 2 lanes on Module0; Bottom 2 lanes on Module 1)

2x2x10B

Cards that already are in 40Gb mode continue to function in 40Gb mode, but they report invalid configuration with qcu64e:

# qcu64e -nic=1 -info

Intel(R) QSFP+ Configuration Utility

QCU version: v2.26.17.06

Copyright(C) 2015 by Intel Corporation.

Software released under Intel Proprietary License.

Adapter supports QSFP+ Configuration modification.

Current Configuration: Invalid

Supported Configurations:

4x10

2x2x10A (Top 2 lanes on Module0; Bottom 2 lanes on Module 1)

2x2x10B

We are using the i40e driver 1.4.25 on Redhat 6: 2.6.32-573.18.1.el6.x86_64 kernel

# ethtool -i eth4

driver: i40e

version: 1.4.25

firmware-version: 5.02 0x80002285 0.0.0

bus-info: 0000:06:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

It looks like there is currently no way to downgrade the firmware, which make the cards that are now stuck in 4x10 unusable for us.

Hello,

Is it possible to use ntuple for blocking packets by ttl value in the ethernet?

I am curious about User-defined field shown in Filters.

Regards,

Filter: 2045

        Rule Type: TCP over IPv4

        Src IP addr: 0.0.0.0 mask: 255.255.255.255

        Dest IP addr: 213.232.170.33 mask: 0.0.0.0

        TOS: 0x0 mask: 0xff

        Src port: 0 mask: 0xffff

        Dest port: 81 mask: 0x0

        VLAN EtherType: 0x0 mask: 0xffff

        VLAN: 0x0 mask: 0xffff

        User-defined: 0x0 mask: 0xffffffffffffffff

        Action: Drop

Hi All,

I'm having this issues, as described below:

https://bugs.launchpad.net/neutron/+bug/1506003

My libvirt version is 1.2.17

Is this an ixgbe issue or libvirt ? if it is, is there already a defect for it, and is it already scheduled to be fixed ?

Thanks ahead,

Ran.

From the kernel log:

May 13 10:38:16 andromeda kernel: e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:

                                    TDH                  <44>

                                    TDT                  <4b>

                                    next_to_use          <4b>

                                    next_to_clean        <44>

                                  buffer_info[next_to_clean]:

                                    time_stamp           <10112f310>

                                    next_to_watch        <45>

                                    jiffies              <10112f50c>

                                    next_to_watch.status <0>

                                  MAC Status             <40080083>

                                  PHY Status             <796d>

                                  PHY 1000BASE-T Status  <3800>

                                  PHY Extended Status    <3000>

                                  PCI Status             <10>

May 13 10:38:18 andromeda kernel: e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:

                                    TDH                  <44>

                                    TDT                  <4b>

                                    next_to_use          <4b>

                                    next_to_clean        <44>

                                  buffer_info[next_to_clean]:

                                    time_stamp           <10112f310>

                                    next_to_watch        <45>

                                    jiffies              <10112f764>

                                    next_to_watch.status <0>

                                  MAC Status             <40080083>

                                  PHY Status             <796d>

                                  PHY 1000BASE-T Status  <3800>

                                  PHY Extended Status    <3000>

                                  PCI Status             <10>

May 13 10:38:20 andromeda kernel: e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:

                                    TDH                  <44>

                                    TDT                  <4b>

                                    next_to_use          <4b>

                                    next_to_clean        <44>

                                  buffer_info[next_to_clean]:

                                    time_stamp           <10112f310>

                                    next_to_watch        <45>

                                    jiffies              <10112f9bc>

                                    next_to_watch.status <0>

                                  MAC Status             <40080083>

                                  PHY Status             <796d>

                                  PHY 1000BASE-T Status  <3800>

                                  PHY Extended Status    <3000>

                                  PCI Status             <10>

May 13 10:38:22 andromeda kernel: e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:

                                    TDH                  <44>

                                    TDT                  <4b>

                                    next_to_use          <4b>

                                    next_to_clean        <44>

                                  buffer_info[next_to_clean]:

                                    time_stamp           <10112f310>

                                    next_to_watch        <45>

                                    jiffies              <10112fc14>

                                    next_to_watch.status <0>

                                  MAC Status             <40080083>

                                  PHY Status             <796d>

                                  PHY 1000BASE-T Status  <3800>

                                  PHY Extended Status    <3000>

                                  PCI Status             <10>

May 13 10:38:22 andromeda kernel: ------------[ cut here ]------------

May 13 10:38:22 andromeda kernel: WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x23e/0x250()

May 13 10:38:22 andromeda kernel: NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out

May 13 10:38:22 andromeda kernel: Modules linked in: xt_nat iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables dahdi_echocan_mg2(O) sch_fq_codel btrfs xor raid6_pq sd_mod x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ahci libahci ghash_clmulni_intel iTCO_wdt wctdm(O) aesni_intel dahdi(O) crc_ccitt aes_x86_64 lrw gf128mul glue_helper serio_raw ablk_helper cryptd microcode xhci_pci ehci_pci xhci_hcd ehci_hcd i2c_i801 i2c_core r8169 mii lpc_ich mfd_core e1000e libata ptp pps_core evdev usbcore usb_common fan thermal battery tpm_infineon tpm_tis tpm acpi_cpufreq button processor thermal_sys hwmon

May 13 10:38:22 andromeda kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: G           O   3.19.5 #1

May 13 10:38:22 andromeda kernel: Hardware name: ASUS All Series/Z87-DELUXE, BIOS 2103 08/15/2014

May 13 10:38:22 andromeda kernel:  0000000000000000 ffffffff8152b0af ffffffff8141c950 ffff88043fac3e18

May 13 10:38:22 andromeda kernel:  ffffffff81044ab7 0000000000000000 ffff88041e57c3a0 ffff88041e57c000

May 13 10:38:22 andromeda kernel:  0000000000000003 0000000000000001 ffffffff81044b35 ffffffff8152f9f8

May 13 10:38:22 andromeda kernel: Call Trace:

May 13 10:38:22 andromeda kernel:  <IRQ>  [<ffffffff8141c950>] ? dump_stack+0x47/0x67

May 13 10:38:22 andromeda kernel:  [<ffffffff81044ab7>] ? warn_slowpath_common+0x77/0xb0

May 13 10:38:22 andromeda kernel:  [<ffffffff81044b35>] ? warn_slowpath_fmt+0x45/0x50

May 13 10:38:22 andromeda kernel:  [<ffffffff81345cfe>] ? dev_watchdog+0x23e/0x250

May 13 10:38:22 andromeda kernel:  [<ffffffff81345ac0>] ? dev_graft_qdisc+0x80/0x80

May 13 10:38:22 andromeda kernel:  [<ffffffff8108a445>] ? call_timer_fn.isra.32+0x15/0x80

May 13 10:38:22 andromeda kernel:  [<ffffffff81098cd0>] ? tick_sched_handle.isra.18+0x30/0x30

May 13 10:38:22 andromeda kernel:  [<ffffffff81345ac0>] ? dev_graft_qdisc+0x80/0x80

May 13 10:38:22 andromeda kernel:  [<ffffffff8108a650>] ? run_timer_softirq+0x1a0/0x230

May 13 10:38:22 andromeda kernel:  [<ffffffff810480f4>] ? __do_softirq+0xf4/0x200

May 13 10:38:22 andromeda kernel:  [<ffffffff81048365>] ? irq_exit+0x95/0xa0

May 13 10:38:22 andromeda kernel:  [<ffffffff8102daa9>] ? smp_apic_timer_interrupt+0x39/0x50

May 13 10:38:22 andromeda kernel:  [<ffffffff81422c2a>] ? apic_timer_interrupt+0x6a/0x70

May 13 10:38:22 andromeda kernel:  <EOI>  [<ffffffff81302645>] ? cpuidle_enter_state+0x45/0xb0

May 13 10:38:22 andromeda kernel:  [<ffffffff8130263a>] ? cpuidle_enter_state+0x3a/0xb0

May 13 10:38:22 andromeda kernel:  [<ffffffff810781f5>] ? cpu_startup_entry+0x245/0x2e0

May 13 10:38:22 andromeda kernel: ---[ end trace 5b6161fdf3307fee ]---

May 13 10:38:22 andromeda kernel: e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly

May 13 10:38:28 andromeda kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

From lspci -vv:

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)

        DeviceName:  Onboard LAN

        Subsystem: ASUSTeK Computer Inc. Ethernet Connection I217-V

        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

        Interrupt: pin A routed to IRQ 32

        Region 0: Memory at dfd00000 (32-bit, non-prefetchable) [size=128K]

        Region 1: Memory at dfd3d000 (32-bit, non-prefetchable) [size=4K]

        Region 2: I/O ports at f080 [size=32]

        Capabilities: [c8] Power Management version 2

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

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

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

                Address: 00000000feeff00c  Data: 4153

        Capabilities: [e0] PCI Advanced Features

                AFCap: TP+ FLR+

                AFCtrl: FLR-

                AFStatus: TP-

        Kernel driver in use: e1000e

        Kernel modules: e1000e

Anybody got any clues? Looks similar to problems with other e1000 hardware so I am currently testing with 'ethtool -K eno1 tso off' to see if the recurring problem goes away.

Thanks!

after I install the driver of igb-5.3.3.5.tar.gz, the light of the

Network Connections are all off. and I can't

find the eth0 by ifconfig.

I have searched for the possible answer on the forums and outside but no avail.

Issue: Device Cannot Start Code 10

Computer: Thinkpad W540

OS: Windows 7 Pro

Architecture: x64

Short-term Solution: Disable/Enable the device on Device Manager

The things I already did are the following:

• Windows Update
• BIOS are set to factory default
• Lenovo System Update
• Downloaded and (re-)installed drivers from Intel's Website (older and newer/-est drivers)
• Deleted previous drivers
• Disk cleanup

Any other troubleshooting steps that I may have missed? Please don't tell me that the motherboard used on the W540 is defective by design.