Date: Wed, 18 Jan 2017 16:20:55 +0100 From: "O. Hartmann" <o.hartmann@walstatt.org> To: Sean Bruno <sbruno@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> 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> <eba93bf8-2acf-d7bc-0192-10e75b7b993b@freebsd.org> <1abc7c08-8664-a22e-dcab-fa884acbfce9@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Jan 2017 07:59:17 -0700 Sean Bruno <sbruno@freebsd.org> 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 <sbruno@freebsd.org> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > >>> 1500 > >>> options=653dbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> > >>> ether xx:xx:xx:xx:xx:xx inet 192.168.0.111 netmask 0xffffff00 broadcast > >>> 192.168.0.255 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > >>> media: Ethernet autoselect (100baseTX <full-duplex>) > >>> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170118162051.17c9b88b>