Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Feb 2015 20:47:15 +0000
From:      Steven Hartland <killing@multiplay.co.uk>
To:        freebsd-net@freebsd.org
Subject:   Re: FreeBSD 10.1: Intel dual port 10GbE card (82599EB): second port not present?
Message-ID:  <54DBBFD3.7010801@multiplay.co.uk>
In-Reply-To: <54DBBB95.2050901@gmail.com>
References:  <54DBBB95.2050901@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 11/02/2015 20:29, John Jasen wrote:
> I have several servers that have two Intel 10GbE ports on board. They're
> technically Dell daughterboards which have two Intel 1GbE and two 10GbE
> ports.
>
> However, the second ix interface is not accessible, and does not seem to
> be available. From a brief look, it looks like ix0 and both igb
> interfaces come up before SMP is started. The second ix interface is
> attempted afterwards, but doesn't show up.
>
> Am I missing the obvious?
>
> IE, from dmesg:
>
> ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15>
> port 0xfcc0-0xfcdf mem 0xd8d00000-0xd8dfffff,0xd8ff8000-0xd8ffbfff
> irq 36 at device 0.0 on pci1
> ix0: Using MSIX interrupts with 9 vectors
> ix0: Unsupported SFP+ Module
> device_attach: ix0 attach returned 5
>
> ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15>
> port 0xfce0-0xfcff mem 0xd8e00000-0xd8efffff,0xd8ffc000-0xd8ffffff
> irq 34 at device 0.1 on pci1
> ix0: Using MSIX interrupts with 9 vectors
> ix0: Ethernet address: ec:f4:bb:c8:0b:12
> ix0: PCI Express Bus: Speed 5.0GT/s Width x8
>
> <snip>
>
> SMP: AP CPU #21 Launched!
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #18 Launched!
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #17 Launched!
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #16 Launched!
> SMP: AP CPU #9 Launched!
> SMP: AP CPU #23 Launched!
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #10 Launched!
> SMP: AP CPU #12 Launched!
> SMP: AP CPU #11 Launched!
> SMP: AP CPU #14 Launched!
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #13 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #8 Launched!
> SMP: AP CPU #19 Launched!
> SMP: AP CPU #15 Launched!
> SMP: AP CPU #22 Launched!
> SMP: AP CPU #6 Launched!
> SMP: AP CPU #20 Launched!
>
> <snip>
>
> ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15>
> port 0xfcc0-0xfcdf mem 0xd8d00000-0xd8dfffff,0xd8ff8000-0xd8ffbfff irq
> 36 at device 0.0 on pci1
> ix1: Using MSIX interrupts with 9 vectors
> ix1: Unsupported SFP+ Module
> device_attach: ix1 attach returned 5
>
> <snip, then again>
>
> ix1: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15>
> port 0xfcc0-0xfcdf mem 0xd8d00000-0xd8dfffff,0xd8ff8000-0xd8ffbfff irq
> 36 at device 0.0 on pci1
> ix1: Using MSIX interrupts with 9 vectors
> ix1: Unsupported SFP+ Module
> device_attach: ix1 attach returned 5
Your problem looks like its the SFP's which are "unsupported" to which 
the attach will fail with error EIO (5).

You can set hw.ix.unsupported_sfp=1 in /boot/loader.conf to enable 
unsupported SFP's but be aware you "doing so your on your own".

     Regards
     Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54DBBFD3.7010801>