From owner-freebsd-net@freebsd.org Wed Nov 11 16:40:42 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 5E718A2C5E2 for ; Wed, 11 Nov 2015 16:40:42 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (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 1B16A1C62; Wed, 11 Nov 2015 16:40:42 +0000 (UTC) (envelope-from ricera10@gmail.com) Received: by qgec40 with SMTP id c40so27191106qge.2; Wed, 11 Nov 2015 08:40:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=6AQfFTVP+gS8abju3j1s6FxT57bEB0aKDTqQzgqdBMc=; b=QzVqxqs9Eb9/eTXpPtovf54cc31se2KJ3zRDn4YS4JlOl7viTFIRFZTsoucT+2o9QZ eTQjLg2/M7QZUveuc/SB+O/3aLF5Pn5cy51b70hRPNqcAuV2/LwSkB8JJraw5cJG7T/F 9tp6aWL+liUSlMlfSeq4mLSI12RUJZkgIfo+j8SUmDwiCwY0Yn7Vj7cUugKdLBJOfhTU TOUwdBCcm7gnD0sWGvlewgl0BRkkty+mkLA+xP7ltpHVgpyqUNNdXVNylzbhBpGm///D Un+rmz656OhbDzJBVygG5Fdm7xGUui/Naqu3PUMEdcVmVGbt7Kbj+EB3OsFVXOAJ2QNZ c23g== X-Received: by 10.140.30.101 with SMTP id c92mr11465294qgc.74.1447260040803; Wed, 11 Nov 2015 08:40:40 -0800 (PST) MIME-Version: 1.0 References: <564357E0.1050002@freebsd.org> <56436A5F.4020102@multiplay.co.uk> In-Reply-To: From: Eric Joyner Date: Wed, 11 Nov 2015 16:40:31 +0000 Message-ID: Subject: Re: Intel XL710 broken link down detection? To: Jack Vogel , Ryan Stone Cc: Jack F Vogel , "freebsd-net@freebsd.org" , Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Wed, 11 Nov 2015 16:40:42 -0000 I think the early versions of the description of the command were vague, so that's why it got everyone. We caught it and fixed it a few days ago internally. On Wed, Nov 11, 2015, 8:37 AM Jack Vogel wrote: > LOL, Damn, what's the world coming to when you can't trust them Linux guys > :) > > Jack > > > > > On Wed, Nov 11, 2015 at 8:31 AM, Ryan Stone wrote: > > > On Wed, Nov 11, 2015 at 11:18 AM, Steven Hartland < > steven@multiplay.co.uk> > > 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" >