On Tue, 15 Sep 2015 18:45:35 +0000
"Pieper, Jeffrey E" <jeffrey.e.pie...@intel.com> wrote:
> -----Original Message-----
> From: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
> Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann
> <ohart...@zedat.fu-berlin.de>; freebsd-current <firstname.lastname@example.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 of
> > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy
> > 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 amd64 I
> > had no problems.
> > Any ideas?
> > Thanks in advance,
> > Oliver
> >Just to rule out r287775, can you disable TSO?
> I'm using r827826 (just pulled this morning) with igb and it seems to be
> working (icmp and ssh).
> email@example.com mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Well, driver igb covers a lot of different hardware. We have a Fujitsu
Primergy287700 RX 1330 M1 and it is equipted with a i210 Intel dual GBit NIC.
I double checked today, r287910 doesn't work. Since I use nanoBSD, I can change
the underlying OS with the very same configuration and I did today with
different revisions and 10-STABLE. r287420 and r287700 work also, r287750 also,
r287800 does NOT!
There were changes to sys/dev/e1000/ between 287750 and r287800 and those
obviously do break the igb interface in CURRENT for, at least, i210 NICs.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"