From owner-freebsd-net@freebsd.org Wed Nov 11 16:18:32 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 0F85EA2CDF9 for ; Wed, 11 Nov 2015 16:18:32 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 9C628125C for ; Wed, 11 Nov 2015 16:18:31 +0000 (UTC) (envelope-from steven@multiplay.co.uk) Received: by wmvv187 with SMTP id v187so63414930wmv.1 for ; Wed, 11 Nov 2015 08:18:29 -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=MkGdpCboqzeUAP8MVlrF3NPQwZYIRSKJxbwk4orWB74=; b=NIUolOL2wqJrlDmC7sjF1o4rEKi3ZikFt8r7MJLDsgh8LS79GsQsp5EzVahEL830fT FgfuUYfoKV0Qz/2GqdaKwmGgFLHsyhph/itGaPHvv/HSKzMrkP9k6vTrFDqTXvUDv0bs wWBIpxa7cNMjKjqXaU8nkjPeKhL4S1JD3u6QhrPqX0AhEA7JzMamruc7k3+TxxRBH7fp tLDlgwzf9qJ6Oha+f6ayGpBAb6BDJI4yTzeqdGmTCxO5JmieaVt5/uWUIfCqpJjQgJ/T ilounp+midR9CuvTnnLiCZDYlPBYzj5D31Pnk1YsoYjhDkNc4RJpusKY6Saq7dwdwAj8 k0Qw== 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=MkGdpCboqzeUAP8MVlrF3NPQwZYIRSKJxbwk4orWB74=; b=Pyfstw5iJlLKIwTA8yYJVGREu8mlXVpzV7/6OzU/vMtcazL/QOH+kuPI4dSfPd19pt +dzngUUGIos0eOOwPwnIGRprMeLACbv7X7AXF2GrUHnNiVp/5MTS9ym/iJt8GOd0NYaN w1bOHQFmQBfsbGVin8+GclxLmHc02RS/oe68QrJ2TkTXtxJvPDJpJxf1xtpqS26GMyQ7 0w53ZiYamtfYD0N9hobCoeHP4z1/fKd9iNNC5ZYTDUKMov83GuaGU3JhHgJqHK8tLLkL 2y+KMkh9ZIgm2lyVHSSbBBLEpMNy3I37FdF53adeU49MWqf242aqTyo2296ms7NRAqdd t5jQ== X-Gm-Message-State: ALoCoQmn7TQEIwBY2jfyyN/uwEQSy6TTjVuoJ7fk2nCtdzpNDzuPIKr7uElFMG23KRbMjG9cE7bL X-Received: by 10.28.218.7 with SMTP id r7mr11420554wmg.17.1447258709799; Wed, 11 Nov 2015 08:18:29 -0800 (PST) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id b134sm26012649wmf.9.2015.11.11.08.18.28 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Nov 2015 08:18:28 -0800 (PST) Subject: Re: Intel XL710 broken link down detection? To: "freebsd-net@freebsd.org" References: <564357E0.1050002@freebsd.org> Cc: Jack F Vogel From: Steven Hartland Message-ID: <56436A5F.4020102@multiplay.co.uk> Date: Wed, 11 Nov 2015 16:18:39 +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: <564357E0.1050002@freebsd.org> Content-Type: text/plain; charset=utf-8; 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: Wed, 11 Nov 2015 16:18:32 -0000 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? On 11/11/2015 14:59, Steven Hartland wrote: > Seems the Intel XL710 (ixl) has broken link detection, it triggers on > link up but not on link down. > > I'm currently running HEAD (r290610) on the box which has 1.4.3 and > have tried the latest driver from downloads.intel.com which is listed > as 1.4.8 but reports 1.4.5. > > We've updated to the latest NVM image today to see if that would help > but no change. > > Tracing with dtrace shows that ixl_do_adminq process a link event and > fires off ixl_link_event for link up but not for link down for some > reason. > > Running ifconfig against the interface updates the status as runs > ixl_update_link_status in ixl_media_status, so the device can > determine the link is down its just not noticing the event. > > From dmesg: > ixl0: mem > 0xc5000000-0xc57fffff,0xc5808000-0xc580ffff irq 34 at device 0.0 on pci5 > ixl0: Using MSIX interrupts with 33 vectors > ixl0: f4.40 a1.4 n04.53 e80001ccc > ixl0: Using defaults for TSO: 65518/35/2048 > ixl0: Ethernet address: 0c:c4:7a:3a:2d:60 > ixl0: PCI Express Bus: Speed 8.0GT/s Width x8 > queues is 0xfffffe00015bd000 > ixl0: netmap queues/slots: TX 32/1024, RX 32/1024 > ixl1: mem > 0xc4800000-0xc4ffffff,0xc5800000-0xc5807fff irq 34 at device 0.1 on pci5 > ixl1: Using MSIX interrupts with 33 vectors > ixl1: f4.40 a1.4 n04.53 e80001ccc > ixl1: Using defaults for TSO: 65518/35/2048 > ixl1: Ethernet address: 0c:c4:7a:3a:2d:61 > ixl1: PCI Express Bus: Speed 8.0GT/s Width x8 > queues is 0xfffffe0001ad1000 > ixl1: netmap queues/slots: TX 32/1024, RX 32/1024 > > When its up it reports 10GBase-KR > > Any ideas? > > Regards > Steve