What is the tx_restart_queue?

What causes tx_restart_queue to increment?

Is it normal to see packet drops when tx_restart_queue increments?

Hello. I have an old Toshiba Laptop with an Intel pro/100 8255x controller NIC. Recently the PXE-BOOTP stopped working with this message: ""PXE-E05: Lan adapter's configuration is corrupted or has not been initialized. The Boot Agent cannot continue.". There's also no NIC visible when the linux system boots up on the laptop.

I have downloaded the preeboot.tar.gz file from Intel's  download page, and ran "$ APPS/BootUtil/Linux32/DRIVER/install", which completed without any error.

If understand correctly, I must re-flash the PXE-ROM with bootutil32 in order to restore the PXE-BOOTP capability of the NIC. But what I get is:

# ./bootutil32  =>  Port / 1, Network-Addr / MAC^, Location / 2.08.0, Series / 10-100, WIOL / NA, Flash / FLASH, Firmware / Not Present

# ./bootutil32 -NIC=1 -up -file=../BootIMG.FLB  => "Option ROM area in the flash is not suported for this device on port 1"

Can someone tell me what I am doing wrong and how I can correct this problem?

Thanks & Regards.

I have two servers running OpenSUSE both with  Intel dual port 82599EB 10-Gigabit SFI/SFP+ using the ixgbe drivers. And I'm not getting the bandwidth I expect with iperf. Both ports are connected directly to the the other two ports of the second server.

On one machine I run

iperf -s

On the other machine I run these two commands in separate terminals.

iperf -c 192.168.1.10 -t 20 -B 192.168.1.20

iperf -c 192.168.1.11 -t 20 -B 192.168.1.21

And I get

[  4]  0.0-20.0 sec  7.63 GBytes  3.28 Gbits/sec

[  5]  0.0-20.0 sec  14.7 GBytes  6.30 Gbits/sec

If I run only one port, I get

[  6]  0.0-20.0 sec  22.8 GBytes  9.80 Gbits/sec

Shouldn't I be able to expect roughly 10Gbe on each port simultaneously? Do I have the wrong hardware for that requirement? Or an invalid test?

I am using the above Intel adapter in a Synology NAS server. I would like to update the firmware running on the on the NIC because I am having some intermittent network errors that might be related to the NIC. I down loaded the latest firmware available from Intel's website. I cannot do the upgrade on the box that it is running on because it runs a stripped down version of Linux and some of the commands don't work. I tried putting the NIC in a windows 7 PC but I can't seem to get the firmware update utility to run. I was wondering if anyone has tried this and give me some direction.

Hi,

1.        I have a Intel®  PRO/1000 PT Quad Port Server Adapter.

• Can i install this in a PCIE*1 slot ?
• will there be any degradation in the performance.
• can we use  Intel Gigabit ET Dual-Port Server Adapter in absence of   Intel®  PRO/1000 PT Quad Port Server Adapter.? what is the difference.

I've run into a one-way transmission issue with FreeBSD and Virtual Functions on an Intel 10GbE X520. So far we've tested:

•     Ubuntu 12.04 LTS
•     CentOS 6.5
•     pfSense 2.1 / FreeBSD 8.3
•     pfSense 2.2 / FreeBSD 10.0 (alpha)
•     FreeBSD 8.3-STABLE

All are instances are running on top of KVM installed on Ubuntu 14, hosted on Intel Grizzly Pass OEM hardware with the above-mentioned card installed. The card's two 10GbE ports are connected back-to-back.

In our test case, all instances above have a VF inside VLAN 100 and are bridged via the 82599 controller's internal L2 'switch.' The Ubuntu and CentOS instances can reach each other on their VF/VLAN100 interfaces, but any FreeBSD instance spun up cannot. tcpdump on a CentOS instance and a FreeBSD instance show the FreeBSD instance send an ARP request, the CentOS instance receive it and respond, but it never reaches the FreeBSD instance. Since this is not an issue on Ubuntu or CentOS, and has persisted across two versions of FreeBSD and two Intel VF driver versions, I have to assume it's unique to FreeBSD. The examples below are between FreeBSD 8.3-STABLE and CentOS 6.5:

freebsd1# tcpdump -i ix0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ix0, link-type EN10MB (Ethernet), capture size 96 bytes
21:24:44.137249 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:45.144856 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:46.154881 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:47.164913 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:48.174898 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:49.184903 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:50.194905 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:51.204917 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:52.214924 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:53.224947 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:54.234961 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:55.245032 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
21:24:56.255034 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
^C
13 packets captured
13 packets received by filter
0 packets dropped by kernel

[root@centos1 ~]# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
17:24:44.274997 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:44.275053 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:45.282609 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:45.282651 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:46.292589 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:46.292602 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:47.302563 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:47.302576 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:48.312541 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:48.312553 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:49.322596 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:49.322609 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:50.332542 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:50.332553 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:51.342602 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:51.342614 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:52.352554 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:52.352566 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:53.362614 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:53.362627 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:54.372599 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:54.372611 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
17:24:55.382681 ARP, Request who-has 192.168.100.101 tell 192.168.100.253, length 28
17:24:55.382802 ARP, Reply 192.168.100.101 is-at 52:54:00:db:57:b2 (oui Unknown), length 28
^C
24 packets captured
24 packets received by filter
0 packets dropped by kernel

freebsd1# uname -a
FreeBSD freebsd1 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Mon Apr 9 21:23:18 UTC 2012 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64

freebsd1# dmesg | grep Virtual
CPU: QEMU Virtual CPU version 2.0.0 (2793.29-MHz K8-class CPU)
ix0: <Intel(R) PRO/10GbE Virtual Function Network Driver, Version - 1.1.2> mem 0xfebf0000-0xfebf3fff,0xfebf4000-0xfebf7fff at device 5.0 on pci0

freebsd1# ifconfig ix0
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 52:54:00:44:99:6c
inet6 fe80::5054:ff:fe44:996c%ix0 prefixlen 64 scopeid 0x3
inet 192.168.100.253 netmask 0xffffff00 broadcast 192.168.100.255
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: active

Our issue is identical in description to this post. However, there is no "Simulated MSI Support" option in our BIOS and I believe that particular option was unique to his board based on Intel's BIOS release notes. Another individual ran into a similar problem with FreeBSD 10.0.

Note that pfSense runs v1.1.4 of the Intel VF driver. If you look here, Intel provides a link to e1000 FreeBSD VF drivers. However, no VF-specific drivers are mentioned for ixgbe. There is _vf.h and _vf.c source code in the FreeBSD tree, but we have been unable to compile newer drivers and get them to load.

I'm currently at a loss. I can provide whatever additional information may be helpful; I'm not sure what else is useful at this point. I've dumped some additional info below.

On the host, SR-IOV and IOMMU are enabled. The 10GbE card is on PCI bus 81:00:

root@ubuntu:~# dmesg | grep Intel | grep ixgbe
[ 8.690398] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1-k
[ 8.690398] ixgbe: Copyright (c) 1999-2013 Intel Corporation.
[ 8.950982] ixgbe 0000:81:00.0: Intel(R) 10 Gigabit Network Connection
[ 9.211614] ixgbe 0000:81:00.1: Intel(R) 10 Gigabit Network Connection

VFs are enabled at the host level:

root@ubuntu:~# lspci -s 81:
81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
81:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
81:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:10.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:11.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:12.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.1 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.2 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.3 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.4 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.5 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.6 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
81:13.7 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)

The virtual functions with several instances spun up. VF3 is centos1, VF6 is freebsd1.

root@ubuntu:~# ip link show dev eth4
5: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 90:e2:ba:47:2c:30 brd ff:ff:ff:ff:ff:ff
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 2 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 3 MAC 52:54:00:db:57:b2, vlan 100, spoof checking on, link-state auto
vf 4 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 5 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 6 MAC 52:54:00:44:99:6c, vlan 100, spoof checking on, link-state auto
vf 7 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 8 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 9 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 10 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 11 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 12 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 13 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 14 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 15 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

KVM is also pleased:

root@ubuntu:~# virsh nodedev-list | grep 81
pci_0000_81_00_0
pci_0000_81_00_1
pci_0000_81_10_0
pci_0000_81_10_1
pci_0000_81_10_2
pci_0000_81_10_3
pci_0000_81_10_4
pci_0000_81_10_5
pci_0000_81_10_6
pci_0000_81_10_7
pci_0000_81_11_0
pci_0000_81_11_1
pci_0000_81_11_2
pci_0000_81_11_3
pci_0000_81_11_4
pci_0000_81_11_5
pci_0000_81_11_6
pci_0000_81_11_7
pci_0000_81_12_0
pci_0000_81_12_1
pci_0000_81_12_2
pci_0000_81_12_3
pci_0000_81_12_4
pci_0000_81_12_5
pci_0000_81_12_6
pci_0000_81_12_7
pci_0000_81_13_0
pci_0000_81_13_1
pci_0000_81_13_2
pci_0000_81_13_3
pci_0000_81_13_4
pci_0000_81_13_5
pci_0000_81_13_6
pci_0000_81_13_7

The FreeBSD instance in question is on pci_0000_81_11_4, which maps to VF6 above.

KVM XML for the freebsd1's interface:

        <interface type='hostdev' managed='yes'>          <mac address='52:54:00:44:99:6c'/>          <source>            <address type='pci' domain='0x0000' bus='0x81' slot='0x11' function='0x4'/>          </source>          <vlan>            <tag id='100'/>          </vlan>          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>        </interface>

FYI - we allow KVM to assign the MAC, etc. We only supply the bus, slot, and function numbers when adding a VF-based interface to the instance.

Thanks to anyone who reads and responds. I could really use some help. I've made similar posts on the FreeBSD and pfSense forums, as well as in both /r/freebsd and /r/pfsense on reddit. gonzopancho on reddit directed me to this link, which has a number of patches written by Ryan Stone. It seems like this may be a known issue. At this point we're just looking for confirmation that we aren't crazy. I've felt like this for a week.

Thanks!

I've been having troubles getting WinPE 5.1 to accept the latest drivers from Intel for the 82574L gigabit Ethernet adapter.  Even after adding the drivers to the WinPE image (oem1.inf), the OS insists on loading some old drivers and shows up as e1iexpress adapters via the net1ic64.inf file that has nearly the exact same profiles as for the correct and newer drivers.  I can use DRVLOAD while in command shell in WinPE; however, those other drivers are still resident and overriding the load.

Is there a way to force load during starnet.cmd or any other way?

here is one section from the net1ic64.inf file found in winpe from Microsoft:

;-------------------------------------------------------------------------------
; Intel(R) 82574L Gigabit Network Connection
;

[E10D3.6.2.1]
Characteristics    = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType            = 5    ; PCI
AddReg             = e1c.reg, TcpSeg.reg, JumboPacket.reg
AddReg             = CopperQR.reg, Copper1000.reg
AddReg             = AIFS.reg
AddReg             = RSS.reg, RSS2Q.reg
CopyFiles          = win8.CopyFiles
*IfType            = 6     ; IF_TYPE_ETHERNET_CSMACD
*MediaType         = 0     ; NdisMedium802_3
*PhysicalMediaType = 14 ; NdisPhysicalMedium802_3

[E10D3.6.2.1.Services]
AddService = e1iexpress, 2, win8.Service, win8.EventLog

[E10D3.6.2.1.HW]
AddReg             = MSIX3.reg
Include            = machine.inf
Needs              = PciIoSpaceNotRequired

;-------------------------------------------------------------------------------
; Intel(R) 82583V Gigabit Network Connection
;

[E150C.6.2.1]
Characteristics    = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType            = 5    ; PCI
AddReg             = e1c.reg, TcpSeg.reg, JumboPacket.reg
AddReg             = CopperQR.reg, Copper1000.reg
AddReg             = AIFS.reg
CopyFiles          = win8.CopyFiles
*IfType            = 6     ; IF_TYPE_ETHERNET_CSMACD
*MediaType         = 0     ; NdisMedium802_3
*PhysicalMediaType = 14 ; NdisPhysicalMedium802_3

[E150C.6.2.1.Services]
AddService = e1iexpress, 2, win8.Service, win8.EventLog

[E150C.6.2.1.HW]
AddReg             = MSIX1.reg
Include            = machine.inf
Needs              = PciIoSpaceNotRequired

here's the section from Intel's inf after conversion to oem1.inf (with adding driver from DISM into the boot.wim):

;-------------------------------------------------------------------------------
; Intel(R) 82575EB Gigabit Backplane Connection
;
[E10A9.6.2.1]
Characteristics    = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType            = 5    ; PCI
Port1FunctionNumber = 0
DelReg             = Advanced.DelReg
AddReg             = e1q.reg, TcpSeg.reg, JumboPacket.reg
AddReg             = Powermgmt.reg, WakeOnSlot.reg
AddReg             = EnableWakeOnManagmentOnTCO.reg
AddReg             = LLI.reg
AddReg             = RSS.reg, RSS4Q.reg
AddReg             = UninstallW2.reg
CopyFiles          = win8.CopyFiles, UninstallProg.CopyFiles
*IfType            = 6     ; IF_TYPE_ETHERNET_CSMACD
*MediaType         = 0     ; NdisMedium802_3
*PhysicalMediaType = 14 ; NdisPhysicalMedium802_3

[E10A9.6.2.1.Services]
AddService = e1qexpress, 2, win8.Service, win8.EventLog

[E10A9.6.2.1.CoInstallers]
AddReg             = CoInstaller_AddReg, CoInKS.reg
CopyFiles          = CoInstaller_CopyFiles

[E10A9.6.2.1.HW]
Include            = machine.inf
Needs              = PciIoSpaceNotRequired
AddReg             = MSIX.reg

;-------------------------------------------------------------------------------
; Intel(R) 82574L Gigabit Network Connection
;

[E10D3.6.2.1]
Characteristics    = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType            = 5    ; PCI
DelReg             = Advanced.DelReg
AddReg             = e1q.reg, TcpSeg.reg, JumboPacket.reg
AddReg             = Powermgmt.reg, WakeOnSlot.reg
AddReg             = EnableWakeOnManagmentOnTCO.reg
AddReg             = Copper.reg, Copper1000.reg
AddReg             = AIFS.reg
AddReg             = RSS.reg, RSS2Q.reg
AddReg             = UninstallW2.reg
CopyFiles          = win8.CopyFiles, UninstallProg.CopyFiles
*IfType            = 6     ; IF_TYPE_ETHERNET_CSMACD
*MediaType         = 0     ; NdisMedium802_3
*PhysicalMediaType = 14 ; NdisPhysicalMedium802_3

[E10D3.6.2.1.Services]
AddService = e1qexpress, 2, win8.Service, win8.EventLog

[E10D3.6.2.1.CoInstallers]
AddReg             = CoInstaller_AddReg, CoInKS.reg
CopyFiles          = CoInstaller_CopyFiles

[E10D3.6.2.1.HW]
AddReg             = MSIX3.reg
Include            = machine.inf
Needs              = PciIoSpaceNotRequired

Hello,

I'm having a weird problem with two servers using Supermicro 9SRH-7TF boards and the onboard Intel X540-AT2 based ports. The ethernet ports come up as 100mbps/full duplex. This is happening with two different Cisco switches, one 2960G and one 7609 with a 48port Gb card. Cabling is Cat6, 15 meters for the 7609 and 3 meters for the 2960G.

The servers are running Debian Wheezy and I've tried the stock Debian 3.2.0 kernel as well as the latest kernel from kernel.org (3.14.15). I've also tried using the latest ixgbe driver from sourceforge to no avail.

I was obviously expecting it to come up at 1gbps. But all ports come up *** 100mbps/fdx.

If I change the advertised modes from the server end to only include 1gbps/fdx the link goes down. Setting "speed 1000" on the Cisco also causes the link to go down.

Anyone seen something like this?

Regards,

Fredrik Lindgren

Hi,

We have 5 systems now wich lost communication. It happend random and we do not now where to search.

Event ID: 56

Event Source: e1qexpress

Event Type: Information

Event Description: Intel(R) 82574L Gigabit Network Connection.  The network driver has been stopped because the network adapter has been removed.

I have seen this similar questions posted here for other intel Ethernet problems wich are basically the same issue I am having my issue is with a asrocks 990fx extreme 9 motherboard and also a asus h81m-k motherboard which both have this intel Ethernet chip 82583v and both are doing the same thing connections are constantly hanging

most times we have to refresh to get a page to respond and keep getting dns server timed out errors as well as the network is disconnected error I see this has been a on going problem for a couple years from what I am reading and researching on has anyone figured this problem out yet I have tried every possible driver version from intel and also tried changing setting as well tried turning off or disabled the wake on lan and I have tried disabled the power saving features also I have tried changing speeds of the connection but nothing seems to work I only have one pci slot on my board and I use a tv tuner card so I don't want to have to use a Ethernet card as well any way any help or suggestions would be really appreciated sorry for the run on sentences but I am not too good with English so I do apologise for my bad grammar it is just so frustrating to have spent 1200 dollars building my rig and I cant even get online half the time and arocks has been no help whats so ever but neither has asus  so if I cant get help from you guys I don't know what I can do anyway thanks in advance jaymus777

Summary:

Unable to configure the Pro/1000-PT iSCSI parameters in either:

1. the preboot environment
2. the bootutil DOS command

I'm looking for ideas to work around this problem.

Goal: iSCSI install/boot of an ESXi-5.5 from a Synology iSCSI target.

Relevant environment info:

• SuperMicro server board X10SLL-F
  • This MB contains built-in i217LM and a i210AT NICs. Note that only the i217LM supports native iSCSI
  • MB is using BIOS version 2.0 (04/24/2014), which is the latest available
• Intel Pro/1000-PT Dual-port network card
  • iSCSI flash image installed using DOS-based bootutil program version 1.5.22.2 (from 19.3 distro 8/08/2014)

Symptoms: Preboot:

• During preboot, I get prompted to hit ^D to configure iSCSI.
• Hitting this ^D key brings up a dialog titled "Intel (R) iSCSI Remote Boot v3.0.34
• This dialog lists the two interfaces on the PRO/1000-PT card as well as the built-in i217LM interface on the MB.
• PROBLEM: When I select either of the PRO/1000-PT interfaces using the <ENTER> key, nothing happens; when I select the built-in MB interface, I get the menu of iSCSI and CHAP configurations, cancel and save. So no way to set the TARGET IP address, netmask, CHAP parameters, etc.

Symptoms: bootutil running from DOS:

• "bootutil" command (no command args) lists 4 interface ports:
  • ports 1 and 2 are the built-in MB ports which show "No Flash Present". This makes sense based on the bootutil documentation
  • Ports 3 and 4 are the Pro/1000-PT ports. They currently show "iSCSi Primary" and "iSCSI" in the "Flash Firmware column" and both show as version 3.0.14 (which I belive is the latest).
• I am able to successfully change the upload different flash versions using the bootutil command
• The "bootutil -nic=3 -imageversion" command outputs the following:
  • iSCSI   v3.0.34
  • iSCSI Setup  v3.0.34
  • 40G Interface   v1.0.01  [I have no idea what this last element is of the flashed firmware.]
• PROBLEM: The "bootutil -nic=3" command *should* dump the iscsi configuration the first Pro/1000 port. However, nothing is reported. The %ERRORLEVEL% value after this command is "1", which indicates (according to "bootutil -EXITCODES") a "Bad Command Line Parameter".
• PROBLEM: The iSCSI parameter setting commands such as "bootutil -nic=3 -INITIATORIP=1.2.3.4" don't have any affect. These commands also exit with error code 1, but also do not print any error message out.

Note that I can configure (using the preboot environment), access and begin to install ESXi-5.5 on a remote iSCSI target using the built-in MB i217LM adapter, but ESXi fails to complete the install due to a known issue (Vmware KB 2020053). The work around is to use a network interface besides the first network interface for iSCSI boot/runtime. This is the reason I purchased the Pro/1000 card.

Hi Everyone,

We've recently began installing the Intel Desktop CT Adapter into our Windows 7 machines for configuring some VLANs. One issue we've run into is that the CT adapter on Windows 8.1 seems to not have the same experience as it does in Windows 7. After some digging I found that the CT adapter is not Fully supported on Windows 8. Does anyone know if Intel plans on releasing a Full Support version of the drivers and utilities for this NIC?

My Notebook has 82567LF.

I use now 100Mbit cable, but the speed only connected after i make: netsh int ip reset

Then it runs some Minutes very well and then fall down to round about 25 Mbit.

This did not happen with Windows 7 x64

Any idea what i can do?

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.

I am acquiring 800Mb/sec+ multicast data in a RHEV 6.5 VM using an HP 560SFP+ (Intel 82599ES chip set) adapter in passthru mode (i.e. the NIC is presented natively to the VM).    I am seeing incrementing rx_missed_errors (and losing data) but rx_no_buffer_count is NOT incrementing.  I see some Internet references that indicate that this might be because I have insufficient PCI bandwidth, but that does not seem likely because the platform is e5-2680 and I think I have dedicated PCI-e lines right to the CPU.  I am using the stock RHEL 6.5 ixgbe driver 3.15.1k.    My RX ring buffer is set to 4096, rx-usecs is 180, and lscpi indicates that I am connected at 66Mhz.  Does anyone know what the incrementing rx_missed_errors is trying to tell me and is there any mitigation?

Hi All,

I am connecting my Intel Galileo with the LAN cable and get the IP address using the DHCP server, but I am not able to get a valid IP address.

The IP address I am getting is 255.255.255.255

I am using the Example INO file DHCP Address Print to get the IP.

Any help on this is greatly appreciated.

-Ganesh

Hi all,

We are facing a peculiar problem when connecting particular NICs to particular switches. The NICs will go off-line for 4-5 seconds, in irregular intervals, and then return to service as if nothing had happened. The weird thing is, we see this only on particular combinations of NICs and switches:

- Intel 82599EB, 8086:151c, only work reliably on a Nexus 4900M switch. When used on a Nexus 3064, we get a lot of those:

Sep  2 14:06:16 host kernel: ixgbe 0000:04:00.0: eth0: NIC Link is Down
Sep  2 14:06:21 host kernel: ixgbe 0000:04:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Sep  2 14:06:21 host kernel: ixgbe 0000:04:00.0: eth0: NIC Link is Down
Sep  2 14:06:23 host kernel: ixgbe 0000:04:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX

- Intel X540-AT2, 8086:1528, only work reliably on a Nexus 3064, When used on a Nexus 4900M, we observe the above.

All servers in question are running CentOS6. Those that are Dell have all the latest firmware and BIOS updates installed. We even tested the (then) latest Linux drivers, downloaded directly from Intel, over the ones that come with the OS, but it made no difference. Other machines in the mix are HP and custom-built, and all have one or the other NIC card.

Are there any debug tools for the NICs that could be useful here? Are there any particular options that should or should not be set?

Thanks.

Hi,

I am trying to create  teaming between two intel adapters that i have previously teamed before many times. But this time, I get this message:

"The specified adapter(s) could not be used to create a team. Use the `Team_ValidateAdaptersForTeaming' command to get the warning messages resulting from this action."

After doing above i get no error/warning messages. I have uninstalled and reinstalled the driver, but still getting the same result any ideas to solve this issue.

Thanks.

I am trying to enable a intel x520 10 Gb adapter to pxe boot.  Its a PCI add on card.  this is a bare bone systems that will be installed via PXE from the intel x520 card.  the system has no OS.  Has anyone encounter this issue before.  the instructions all point to and OS installed and runnning the utility,  The problem is it doesnt work with esxi5.0 and I tried with a boot iso which didnt work.  any thoughts

Hello All,

I am trying to install Windows XP on a HP ZBook 17 but unfortunately I am unable to find the drivers for the Intel Ethernet Connection I217-LM

I tried searching it every where contacted HP support but they are unable to help. The network adapter present in the laptop is the Intel Ethernet Connection I217-LM.

Will be really glad if some one helps me to sort this out. I need this up and running as one of the application which I use supports only XP. I have been trying to find this driver for more than a year now

Thanks and Regards,

Marley.