Is the Intel X520-SR2 (82599ES) supported by the ixbe driver?

Dennis Glatting dg at
Fri Mar 15 17:17:25 UTC 2013

I have a new Intel X520-SR2 that I plopped into my Supermicro H8QGL-6F 
with the hope I could connect 10GbE to a Cisco 3560. The links come but 
but there is much wierdness. Looking through the driver I see the 82599EB 
is supported but no mention of the ES.

Should this work?

I have:

Keystone# uname -a
FreeBSD Keystone 9.1-STABLE FreeBSD 9.1-STABLE #0 r248293: Thu Mar 14 
19:31:29 PDT 2013     root at Keystone:/usr/obj/disk-3/src/sys/SECRACK  amd64

Keystone# dmesg | egrep 'ix[01]'
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.7 - 
STABLE/9> port 0x8400-0x841f mem 
0xdce80000-0xdcefffff,0xdce7c000-0xdce7ffff irq 32 at device 0.0 on pci3
ix0: Using MSIX interrupts with 9 vectors
ix0: Ethernet address: 90:e2:ba:2f:5f:9c
ix0: PCI Express Bus: Speed 5.0Gb/s Width x8
ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.7 - 
STABLE/9> port 0x8800-0x881f mem 
0xdcf80000-0xdcffffff,0xdcf7c000-0xdcf7ffff irq 33 at device 0.1 on pci3
ix1: Using MSIX interrupts with 9 vectors
ix1: Ethernet address: 90:e2:ba:2f:5f:9d
ix1: PCI Express Bus: Speed 5.0Gb/s Width x8
ix0: link state changed to UP

Keystone# ifconfig ix0
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 8192

         ether 90:e2:ba:2f:5f:9c
         media: Ethernet autoselect (10Gbase-SR <full-duplex>)
         status: active

Here's an interesting point. If I set the address for the interface, it is 
accepted but an ifconfig of the interface is shown above. Specifically, I 
previously executed this command:

Keystone# ifconfig ix0 inet mtu 8192 up

Executing that command a second time yields:

Keystone# ifconfig ix0 inet mtu 8192 up
ifconfig: ioctl (SIOCAIFADDR): File exists

A truss of that command yields more interesting things, specifically:

kldload("if_ix")                                 ERR#2 'No such file or directory'

There is no driver named if_ix. It is also weird that the interface is 
named ix0 rather than ixgbe0.

Also, an arp shows:

Keystone# arp -an
? ( at 2c:21:72:cb:f5:0c on vlan17 expires in 166 seconds 
? ( at 78:e7:d1:ea:7a:4e on vlan13 expires in 760 seconds 
? ( at 2c:21:72:cb:f5:0c on vlan13 expires in 97 seconds 
? ( at 00:21:d8:0b:57:98 on vlan13 expires in 232 seconds 
? ( at dc:7b:94:9a:52:41 on vlan7 expires in 268 seconds 
? ( at e0:2f:6d:30:39:41 on vlan7 expires in 290 seconds 
? ( at 00:21:d8:0b:57:98 on vlan7 expires in 210 seconds 
? ( at 28:92:4a:2e:e0:a0 on vlan7 expires in 1199 seconds 
? ( at 78:e7:d1:ea:7a:4e on vlan7 expires in 143 seconds 
? ( at 28:92:4a:2e:eb:22 on vlan7 expires in 615 seconds 
? ( at 90:e2:ba:2f:5f:9c on ix0 permanent [ethernet]

So clearly there is a MAC/IP association however I cannot ping the IP:

Keystone# ping
PING ( 56 data bytes

Can someone clue me in?

More information about the freebsd-questions mailing list