Date: Tue, 15 Sep 2015 18:45:35 +0000 From: "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com> To: Hans Petter Selasky <hps@selasky.org>, "O. Hartmann" <ohartman@zedat.fu-berlin.de>, freebsd-current <freebsd-current@freebsd.org> Subject: RE: CURRENT: net/igb broken Message-ID: <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> In-Reply-To: <55F7FCB5.5090809@selasky.org> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freeb= sd.org] On Behalf Of Hans Petter Selasky Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann <ohartman@zedat.fu-berlin.de>; freebsd-current <freebsd-cur= rent@freebsd.org> Subject: Re: CURRENT: net/igb broken On 09/15/15 12:56, O. Hartmann wrote: > Running CURRENT as of today (r287817), it seems that the network system o= f > CURRENT is corrupted. The machine in question is a Fujitsu server Primerg= y RX > 1330 with two Intel "igb" devices (igb0 and igb1). > > the network is now on both devices unreachable. With or without IPFW > (disabling, having first rule to allow everything in/out) doesn't matter. > Nothing get to or from that box on any device. > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep 9 09:09:23 CEST 2015 amd6= 4 I > had no problems. > > Any ideas? > > Thanks in advance, > > Oliver > >Just to rule out r287775, can you disable TSO? > >--HPS I'm using r827826 (just pulled this morning) with igb and it seems to be wo= rking (icmp and ssh). Jeff _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2A35EA60C3C77D438915767F458D65688077F87B>