Try turning TSO off.. i.e. ifconfig igb3 -tso or sysctl net.inet.tcp.tso=0 The transition to iflib has exposed much jankiness in the Intel "shared code" of the e1000 drivers. In particular, the locking contracts may not align with FreeBSD locking primitives. I have boxes running the legacy driver that are clearly reliant on the watchdog reset for steady state which is unacceptable. We are actively looking into this at LLNW, but additional reports and help are appreciated.
Regards, On Fri, Mar 24, 2017 at 6:33 PM, Ben Woods <woods...@gmail.com> wrote: > Morning! > > Since my recent update from FreeBSD12-current r313908 to r315466, I have > noticed some strange behaviour with one of my network interfaces. > > The interface seems to work fine for a day or so, but on a number of > occasions I have found it to be down, and constantly outputting the > following message to the console every few seconds: > igb3: TX(7) desc avail = 41, pidx = 308 > igb3: TX(7) desc avail = 41, pidx = 308 > igb3: TX(7) desc avail = 41, pidx = 308 > ... > > The problem is quickly worked around by issuing the following commands: > # service netif stop igb3 > # service netif start igb3 > > Details of this particular network interface card: > $ pciconf -lv | grep igb3 -A4 > igb3@pci0:0:20:1: class=0x020000 card=0x1f418086 chip=0x1f418086 rev=0x03 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'Ethernet Connection I354' > class = network > subclass = ethernet > > Any ideas what this could be, or how to investigate further? > > Regards, > Ben > > -- > From: Benjamin Woods > woods...@gmail.com > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
