[Bug 216460] 82599ES 10-Gigabit SFI/SFP+ Network Connection link constantly falps

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216460

            Bug ID: 216460
           Summary: 82599ES 10-Gigabit SFI/SFP+ Network Connection link
                    constantly falps
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jlegato at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

We have a system running 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
06:55:27 UTC 2016  with using an Intel 82599 based Dual port SFP+ nic:

ix2 at pci0:131:0:0:       class=0x020000 card=0x061115d9 chip=0x10fb8086 rev=0x01
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82599ES 10-Gigabit SFI/SFP+ Network Connection'
    class      = network
    subclass   = ethernet

We're using an SFP+ SR optic with OM3 multimode fiber. We've configured the ix2
interface with an IP and brought it up. No carrier is shown and no traffic
passes. We're finding that the link constantly moves between the UP/down state.
ix2: link state changed to UP
ix2: link state changed to DOWN
ix2: link state changed to UP
ix2: link state changed to DOWN
ix2: link state changed to UP



We are running driver version 3.13-k but have also tried the intel supplied 
3.14 driver with no luck:

ix2: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.1.13-k> port
0xd020-0xd03f mem 0xfb880000-0xfb8fffff,0xfb904000-0xfb907fff irq 64 at device
0.0 numa-domain 1 on pci11
ix2: Using MSIX interrupts with 9 vectors
ix2: Ethernet address: 0c:c4:7a:88:7d:58
ix2: PCI Express Bus: Speed 5.0GT/s Width x8
ix2: netmap queues/slots: TX 8/2048, RX 8/2048

We've tried a number of cables to eliminate a cable issue. The card works
without issue under Linux on the exact same hardware. We've also tried FreeBSD
10.3 with the exact same results. Are hitting a known bug? If so is their a
workaround?

-- 
You are receiving this mail because:
You are on the CC list for the bug.