From owner-freebsd-net@FreeBSD.ORG Thu Jun 10 02:56:22 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 285A21065672; Thu, 10 Jun 2010 02:56:22 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E89EA8FC19; Thu, 10 Jun 2010 02:56:21 +0000 (UTC) Received: by pwj1 with SMTP id 1so3678568pwj.13 for ; Wed, 09 Jun 2010 19:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aXnfubl7vHblrAsaa1VE0QxsZYsIzxQCIy/utcvZQ0A=; b=XNtTuyxj62IpLEswquwx4O2xykUhoc6v8D1d8NOxMfJaJj9mg5P8D6cHnUZu715+lf rak9XkdRMyWwAQ2dnlDCJAFCzbC/VCCDD7clLJkkzaSKpbmAr/zbbHxdr+8sMQkN+Jlt 3WqBraJ/klT8HLoRIANckEkgi/SMHdEqtctt0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=opPbvGe/J5+4VbytqQK4pgF+n/7FpH1iIhKDqKGl0412onVTXfpT0THQ4x2boWs5yf idQb/PXSVq8Uj+9EyIgZopj+h9UeG/Csop0SxhGV6ykJiG5f3BG+gOT0u8DiVQMMmzP+ /3v5ykL/4mkMaIHoNPt0/ef5w31d2NAO/IxlY= MIME-Version: 1.0 Received: by 10.115.84.4 with SMTP id m4mr15023276wal.222.1276138581150; Wed, 09 Jun 2010 19:56:21 -0700 (PDT) Received: by 10.114.174.14 with HTTP; Wed, 9 Jun 2010 19:56:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Jun 2010 22:56:21 -0400 Message-ID: From: Alexander Sack To: Juli Mallett Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, Jack Vogel Subject: Re: Dual-rate transceivers with ixgbe? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jun 2010 02:56:22 -0000 On Fri, May 28, 2010 at 5:12 PM, Juli Mallett wrote: > On Wed, May 19, 2010 at 00:26, Jack Vogel wrote: >> Hmmm, this is odd, I'm sure that was tested by my validation engineer. >> Tell me what the hardware looks like, ie what the 1G link partner is >> and I'll have him check into it... it SHOULD work. > > It's plugged in to an Extreme Networks gigabit switch with Finisar SFP > transceivers. =A0The Intel NIC is populated with an Intel-branded > Finisar dual-rate SFP+ transceiver, model #FTLX8571D3BCV. > > Here's pciconf -lv: > ix0@pci0:8:0:0: class=3D0x020000 card=3D0x00038086 chip=3D0x10fb8086 rev= =3D0x01 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Intel Corporation' > =A0 =A0class =A0 =A0 =A0=3D network > =A0 =A0subclass =A0 =3D ethernet > ix1@pci0:8:0:1: class=3D0x020000 card=3D0x00038086 chip=3D0x10fb8086 rev= =3D0x01 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Intel Corporation' > =A0 =A0class =A0 =A0 =A0=3D network > =A0 =A0subclass =A0 =3D ethernet > > Is there anything it would help for me to instrument in the driver? > >> You could just ask me you know :) > > I think E-Mails from me are getting caught in your spam filter unless > they go through a list :( > > Thanks! > Juli. > _______________________________________________ > 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" > Jack: I am running into a slightly different issue after back porting ixgbe driver to 7.x (btw you are missing DEBUGOUT6 from your #ifdef and the build logic for the buf_ring's stuff is a little off I think). I am using a Finisar multi-mode transceiver connected to an IxIa 10G traffic generator (I don't know the model number, let me know if you absolutely need it) and everything seems to be working until I hit this block of code: ixgbe_phy.c: 1125 if (!(enforce_sfp & IXGBE_DEVICE_CAPS_ALLOW_ANY_SFP)) = { 1126 /* Make sure we're a supported PHY type */ 1127 if (hw->phy.type =3D=3D ixgbe_phy_sfp_intel) { 1128 status =3D IXGBE_SUCCESS; 1129 } else { 1130 DEBUGOUT("SFP+ module not supported\n"= ); 1131 hw->phy.type =3D ixgbe_phy_sfp_unsuppo= rted; 1132 status =3D IXGBE_ERR_SFP_NOT_SUPPORTED= ; 1133 } 1134 } else { 1135 status =3D IXGBE_SUCCESS; 1136 } Some more goodies: comp_codes_1g 0 comp_codes_10g 20 cable_tech 0 sfp_type: 6 vendor_oui: 906500 device caps: 0xfffc What's interesting is that according to the datasheet, 0x2C of the EEPROM is software reserved (Intel black magic!). Based on the logic, it seems if its an Intel SFP, its okay otherwise claim its not supported. If I #ifdef out this code, the driver comes up but does not autonegotiate on the first shot. If I then do ifconfig ix0 up/down everything comes up and I can use it. I noticed that there has been some churn in this area of recognizing SFPs between 7.x - CURRENT. (obviously Juli's issue might be related to this as well). $ ifconfig ix1 ix1: flags=3D8802 metric 0 mtu 1500 options=3D5bb ether 00:1b:21:40:4b:2d media: Ethernet autoselect status: no carrier # ifconfig ix1 down # ifconfig ix1 up # ifconfig ix1 ix1: flags=3D8843 metric 0 mtu 1500 options=3D5bb ether 00:1b:21:40:4b:2d media: Ethernet autoselect (10Gbase-SR ) status: active Jack, any idea on what's going on? (and what the heck is 0x2C in the EEPRO= M?) Thanks! -aps