From owner-freebsd-net@FreeBSD.ORG Fri Feb 20 17:13:51 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68511704 for ; Fri, 20 Feb 2015 17:13:51 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24752AB0 for ; Fri, 20 Feb 2015 17:13:51 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id l13so8412421iga.1 for ; Fri, 20 Feb 2015 09:13:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=Z6cjq1SL94ivXPsMTMFKTOu3H0AZ7xCMjJdUFcmv38s=; b=MID4W0Vvp0pcUARCx9GlU6yrLHG1Och9lPvmDpuPJNGVJM+F1RgnH/7wQEMABvB92P MmmkeiVt/c2YNel8aw3cEB3UTpoGauVZ05k+CMUEBDMPiXB/VgmitPKhxl9EbgBOVFvf 0Zf0xxUj6B/L6Ol4+r2eewyzDwg/LudhY21MGVbDu8h02mGp1LYukk4vsVNGKBa8i2rH pCbWJpjwS1YWzxU46VfHg9o/E2/dKcDpGinDd7y/95QHIW9ozJmy9NWQVyoOWNY/tgzH Sz6n4W9W50GeJFR/+UmXxMs1F0WODeeKVJi3TUbTalTEhL7QbyuWZtJYfunKNPl4+cZ1 eK6Q== X-Received: by 10.107.137.101 with SMTP id l98mr6121254iod.23.1424452430455; Fri, 20 Feb 2015 09:13:50 -0800 (PST) Received: from [10.1.69.81] (gs-sv-1-49-ac1.gsfc.nasa.gov. [198.119.56.43]) by mx.google.com with ESMTPSA id t41sm17290785ioi.0.2015.02.20.09.13.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Feb 2015 09:13:46 -0800 (PST) Message-ID: <54E76B47.8080907@gmail.com> Date: Fri, 20 Feb 2015 12:13:43 -0500 From: John Jasen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Jack Vogel Subject: Re: FreeBSD 10.1: Intel dual port 10GbE card (82599EB) second port not present? References: <54DCB8F2.5090809@gmail.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2015 17:13:51 -0000 I'll also note this seems to be somewhat unpredictable. I installed a dual port intel 10GbE card into one of the systems, I have not plugged SFP+ modules into them, and three out of four interfaces were available with the fourth completely AWOL. Rebooting with hw.ix.unsupported_sfp=1 presented all four, as expected. As for a use case as to why someone would want this, building out systems before deployment comes to mind. Thanks! On 02/12/2015 11:11 AM, Jack Vogel wrote: > > > On Thu, Feb 12, 2015 at 6:30 AM, John Jasen > wrote: > > > > Date: Wed, 11 Feb 2015 20:47:15 +0000 > > From: Steven Hartland > > > 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 > > > > Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > 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". > > Thanks! hw.ix.unsupported_sfp=1 corrected the immediate problem. > > The network port that didn't come up does not yet have an SFP module > installed > > It seems the default behavior in FreeBSD is to not have the interface > available until a SFP is inserted. While a corner case, this does make > configuration prior to installation a bit more annoying. > > > Well, exactly what use would there be in having it "available" > with no media, its like saying you want your car available with > no wheels :) The media can make operation quite different, it > could be copper it could be fiber, the driver won't know until > there is something actually present, hence it cannot really do > "init" until then. > > Jack > > > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > " > >