From owner-freebsd-net@freebsd.org Thu Nov 26 16:41:52 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06B4AA3A7A4 for ; Thu, 26 Nov 2015 16:41:52 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 8FE641042 for ; Thu, 26 Nov 2015 16:41:51 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by wmww144 with SMTP id w144so27951819wmw.1 for ; Thu, 26 Nov 2015 08:41:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=zGaCqlfEIyjkycC5lVbrA2dzIttoGT3UhSnIc9uUsmg=; b=Ym0//sDfx7OCjmEgNh+olVlxqUzaGW6TZBrgrEPr/wqsjg+X1GD/li/okeKp5oO5W6 da/d6TwYLjQ33813k6T5/AcZ2ZvN/YO9TN2SzZFYXQ7wQ6/Xfrb7Ww0rBbBgZwHFt85Y LNED3jwNpvyc3yMSFGhQE/FTWM1+KEJ4iCKR6xd+rWmNAG81tr7dxj7JzgQD+V7tRJil rnJGOtx/dZ/sUsEsKrama/VwNQhcUOo3O13mQKWUtUpUa1nCdQ59PzpvEkiqmKQOATJw 46LyInd9GuqC0hV4n/TpwK6ZjkUNVguIdQmrJ1oc3hpMneF2+TWm8SQhwAtVzA4Q+Nqr rR4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=zGaCqlfEIyjkycC5lVbrA2dzIttoGT3UhSnIc9uUsmg=; b=lEnstK5NusFe8sAv1IiiQmnh04FdXjq47kzN++68TVwxkT105gb0wooeVuWEgw/QKs 042aZHQDQihsqqLvzwTUdsEGwXWMbn/g6Xpfas8vEvliaaDTL8Tz2HZqN+ytUndlvSwx qTSO1WOxX2j4kK9S+KY353JbtmWFi2vAmGlPpsJoCF5TSCEQCt0w3vtathsrCURdGfMc nwzrYQ4XpFrHfoLctjByELR9BfOvDLN59sFaOjJLUEs9aB2LIjyZWesa5PURpTqB7uW+ THFY8vyuLH2AkgH+VVNJ9ThZcQbYrClgFaF12MAnkYVs2IeFAZqvR7tIJ/KQ1GUCl8Ao eDbw== X-Gm-Message-State: ALoCoQmP5A3hTGRL1C6A2KSMuwJcGm6wywPj+4MaiGbBdcQWdDmnfPi+6F040UM6L5pvedpmfEkA X-Received: by 10.28.4.7 with SMTP id 7mr4600539wme.85.1448556109659; Thu, 26 Nov 2015 08:41:49 -0800 (PST) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id jz1sm28811223wjc.27.2015.11.26.08.41.48 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 Nov 2015 08:41:48 -0800 (PST) Subject: Re: Intel XL710 broken link down detection? To: "Pieper, Jeffrey E" , Ryan Stone References: <564357E0.1050002@freebsd.org> <56436A5F.4020102@multiplay.co.uk> <56446159.3080405@multiplay.co.uk> <2A35EA60C3C77D438915767F458D65688080C4A8@ORSMSX111.amr.corp.intel.com> Cc: Jack F Vogel , "freebsd-net@freebsd.org" From: Steven Hartland Message-ID: <5657364C.10806@multiplay.co.uk> Date: Thu, 26 Nov 2015 16:41:48 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <2A35EA60C3C77D438915767F458D65688080C4A8@ORSMSX111.amr.corp.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 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, 26 Nov 2015 16:41:52 -0000 Its been a couple of weeks now so wanted to check if you had any news on this Pieper? Also for extra visibility I'm looking to bring ixl in stable/10 up to date with the MFC's commits present in HEAD, which are quite a way behind. One commit requires big changes between HEAD and stable/10, due to it being a combination of RSS support (not going to MFC'ed) and some bug fixes, is up for review here: https://reviews.freebsd.org/D4265 I'm looking to use this for a 10.x based DC rollout over the next few weeks, so if anyone can look at that it would be most appreciated. Regards Steve On 12/11/2015 15:18, Pieper, Jeffrey E wrote: > We already have a fix in place that will be committed for review shortly. > > Thanks, > Jeff > > -----Original Message----- > From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Steven Hartland > Sent: Thursday, November 12, 2015 1:52 AM > To: Ryan Stone > Cc: Jack F Vogel ; freebsd-net@freebsd.org > Subject: Re: Intel XL710 broken link down detection? > > Yes this works but a better way IMO would be to invert the bits we want: > https://people.freebsd.org/~smh/ixl_int_init.patch > > If there are no objections then I'll commit this later today. > > Also just fixed the debug sysctls from causing panics when compiled with > INVARIANTS see: > https://svnweb.freebsd.org/base?view=revision&revision=290708 > > Regards > Steve > > On 11/11/2015 16:31, Ryan Stone wrote: >> On Wed, Nov 11, 2015 at 11:18 AM, Steven Hartland >> > wrote: >> >> Comparing this to the Linux driver which does detect the link down >> I've discovered it actually polls the link status by default in >> its watchdog. >> >> Disabling this with "ethtool --set-priv-flags eth1 LinkPolling >> off" and the Linux driver also fails to detect link down. >> >> So this seems like a firmware or even hardware bug where it should >> be reporting down events and the Linux driver has been updated to >> workaround the problem? >> >> >> No, apparently the Linux devs just didn't read the datasheet closely >> enough (and presumably the FreeBSD driver copied the mistake). There >> is a mask of interrupt causes that works backwards from how one would >> expect; you mask out events that you *don't* want rather than events >> that you do want. Both the Linux and FreeBSD drivers pass a mask of >> events that they want interrupts for (the only reason why it appears >> to work on link up is that the the AN Completed event fires when link >> is up, as far as I can tell). Try the following patch: >> >> https://people.freebsd.org/~rstone/patches/ixl_link_int.diff >> >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"