From owner-freebsd-net@FreeBSD.ORG Wed Jul 2 17:15:38 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3DB44B35 for ; Wed, 2 Jul 2014 17:15:38 +0000 (UTC) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id 7BEE62C11 for ; Wed, 2 Jul 2014 17:15:36 +0000 (UTC) Received: (qmail 68570 invoked from network); 2 Jul 2014 17:08:54 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 2 Jul 2014 17:08:54 -0000 Date: Wed, 02 Jul 2014 19:07:39 +0200 (CEST) Message-Id: <20140702.190739.74686622.sthaug@nethelp.no> To: jeffrey.e.pieper@intel.com Subject: Re: Network Intel X520-SR2 stopping From: sthaug@nethelp.no In-Reply-To: <2A35EA60C3C77D438915767F458D65687E8F859E@ORSMSX111.amr.corp.intel.com> References: <53B3F1B6.9010606@bsdinfo.com.br> <2A35EA60C3C77D438915767F458D65687E8F859E@ORSMSX111.amr.corp.intel.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, gondim@bsdinfo.com.br X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 17:15:38 -0000 > Is there any way that you can try a reproduce this using a B2B configuration, or something that doesn't use XFP as a link partner? I'm thinking that you are correct regarding an incompatibility issue between SFP+ and XFP. Why do you believe that? The optical signals are the same for SFP+ and XFP. We have lots of 10G SFP+ / XFP links in production. It just works... Steinar Haug, Nethelp consulting, sthaug@nethelp.no