From owner-freebsd-current@freebsd.org Wed Jan 18 15:21:00 2017 Return-Path: Delivered-To: freebsd-current@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 22304CB6447 for ; Wed, 18 Jan 2017 15:21:00 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EAD315CA; Wed, 18 Jan 2017 15:20:59 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LcSWg-1csVd02kjO-00jozG; Wed, 18 Jan 2017 16:20:56 +0100 Date: Wed, 18 Jan 2017 16:20:55 +0100 From: "O. Hartmann" To: Sean Bruno Cc: freebsd-current Subject: Re: HEADS-UP: IFLIB implementations of sys/dev/e1000 em, lem, igb pending Message-ID: <20170118162051.17c9b88b@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <1abc7c08-8664-a22e-dcab-fa884acbfce9@freebsd.org> References: <30f21c75-d3a2-edcd-1999-d5ed9f970c06@freebsd.org> <20170118083400.11156f23@freyja.zeit4.iv.bundesimmobilien.de> <1abc7c08-8664-a22e-dcab-fa884acbfce9@freebsd.org> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:/RJkn91eyT1VgcQ420GR5qFZpL5y448vIDuUKG4EPMIgU7/twYQ 8qAEQK9/Egg/PAypzpFpyUUc9Z0wIgiWxJyLsudRYewnuDP08odW0v5LyUakqWMTOfmjfMq jiVm1wPmfNyf9W/Ysk69NvNggjQstPxHCkr+6YL2eviAL7eM+PLt1ZFptiDqVWNIpxQOabc 0kGpm+CICIM5o0sSACuDw== X-UI-Out-Filterresults: notjunk:1;V01:K0:kgURFytU+fs=:gMKxlImLUdB0qRKrK6GtsX jDT9o/fn4FvG2foab2YH9gWLy14rh4Na9yO8C9rqYp+C5tNy71O1T+fnaq/otyRUTq0oeFtWa MSu2b6TzH380olhkO88PzR4/o9hUHnPWhVPtUTDpvP1z8jZVBBP2WuGQECxTbnaVSUnIsv0nP 9NTs67uG+e3LdtJVJ23sQQtIBa4pHOh47/5hh1NCEDA3ndgbTv40oCPsVkA2pEA441Rp9oR2/ NdZYDIGGNbFY7QLhaZkOEzuM0+6dnV9FS2aSsyGxYrSQaDBsb91Iqw9fRT8SPOFFt5+Ywfccr DcYTQU65LDRB/1swFzq9qIXld9ClAqrOFIBaByz17IVyjTATfT8i7MuGJc+6nkuPk6nv6hIm8 5otzeOH0A2c3KLrz6yyfT1tgvXxgr6zlZtzAgP9x+2obFIpMWYR97br9dKI3VBrs5WbXKL2kX GF3S18zPNK6E0sLiMn6TSrTlUVP84WKBvMXyWJ9QmUUfhT279KC2+JdNILxJgv3RPedWaR5iE Mr9QrnS7jYR2INnRV1m8lsoaUoNFw73odGH/ZmFSCAy/Ay4Upt9GrSSSsU6OxNod7HGWycMqf X4j+8UN5/FD3FYGqkOlrQGGjyGx85p1XoMRrqbOq7bz9kA92CSYFBZzQCu3DqWTD6LAgERrZy tdQ6hBqlQOSsUMjzdr6swEW58lyYWmiA/coORauDzEHnZOiBp3F3Gz9GlThdfwGJ7lFaOtn3j tGnZ88LUDi2HtR9WYZCv+nnBL202GUpr1NsIm8u+hgTyxCS6JdmSW8i6WtMb4tLGb9tun5Prz PNyNlaj X-Mailman-Approved-At: Wed, 18 Jan 2017 16:42:22 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 15:21:00 -0000 On Wed, 18 Jan 2017 07:59:17 -0700 Sean Bruno wrote: > On 01/18/17 07:41, Sean Bruno wrote: > > > > > > On 01/18/17 00:34, O. Hartmann wrote: > >> On Thu, 5 Jan 2017 20:17:56 -0700 > >> Sean Bruno wrote: > >>> > >> On a Fujitsu Celsius M740, the "em0" device gets stuck on heavy I/O. I can > >> still trigger this behaviour on recent CURRENT (12.0-CURRENT #17 r312369: > >> Wed Jan 18 06:18:45 CET 2017 amd64) by rsync'ing a large poudriere ports > >> repository onto a remote NFSv4 fileserver. The freeze always occur on large > >> tarballs. > >> > >> Again, here is the pciconf output of the device: > >> > >> em0@pci0:0:25:0: class=0x020000 card=0x11ed1734 chip=0x153a8086 > >> rev=0x05 hdr=0x00 vendor = 'Intel Corporation' > >> device = 'Ethernet Connection I217-LM' > >> class = network > >> subclass = ethernet > >> bar [10] = type Memory, range 32, base 0xfb300000, size 131072, > >> enabled bar [14] = type Memory, range 32, base 0xfb339000, size 4096, > >> enabled bar [18] = type I/O Port, range 32, base 0xf020, size 32, enabled > >> > >> On another box. equipted with a dual-port Intel i350 NIC, the igb0 and > >> igb1 do have negotiation problems with several types of switches (in my > >> SoHo environment, I use a Netgear GS110TP, at work there are several types > >> of Cisco Catalyst 3XXX types). The igbX very often fall back to 100MBit/s. > >> > >> Since yesterday, the igbX on that specific i350 basesd NIC (we have plentz > >> of them and they show similar phenomena with FreeBSD), although the switch > >> reports an uplink with 1 GBit, FreeBSD CURRENT shows this weird crap > >> message: > >>> igb0: flags=8843 metric 0 mtu > >>> 1500 > >>> options=653dbb > >>> ether xx:xx:xx:xx:xx:xx inet 192.168.0.111 netmask 0xffffff00 broadcast > >>> 192.168.0.255 nd6 options=29 > >>> media: Ethernet autoselect (100baseTX ) > >>> status: active > >> > > I just checked my test machines (which are auto/auto on the Juniper > EX4200 switches in use) and I see them come up with 1000baseTX. Do you > set any options in /etc/rc.conf? > > sean > No, I don't. The line is: ifconfig_igb0="inet 192.168.0.10 netmask 0xffffff00" Nothing else.