On Tue, Feb 02, 2016 at 09:49:59AM -0500, Mike Tancsa wrote: > On 1/30/2016 12:26 PM, Marius Strobl wrote: > > On Sat, Jan 30, 2016 at 11:47:19AM -0500, Mike Tancsa wrote: > >> On 1/29/2016 8:23 PM, Marius Strobl wrote: > >>> On Fri, Jan 29, 2016 at 03:41:57PM -0500, Mike Tancsa wrote: > >>>> > >>>> No multi queue. Stock GENERIC kernel with a couple of things removed. > >>>> hw.em are just the defaults. I will try without TSO > >>>> > >>>> % ifconfig em0 > >>>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > >>>> > >>>> options=4209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO> > >>>> > >>> > >>> Hrm, that's strange, TSO4 should be enabled by default so apparently > >>> you are already disabling it; what is the behavior if you turn it on? > >>> Do you use a < Gigabit link? > >> > >> Hi Marius, > >> Thanks for looking. The ifconfig output was after I turned off tso as > >> Harry suggested to try. Its been 24hrs and I have not seen any resets. > >> I will wait another 36hrs or so and then turn it back on to see if the > >> problem comes back. > >> > >> this link is 100Mb. > > > > Ah, okay, that at least makes sense. Can you please verify that with > > the attached patch applied, you have a setup that works out of the > > box? > > Hi, > Should the nic come up with TSO disabled by default ? After reboot, I > see >
Yes, that's expected; the default still is to enable TSO4, but with the patch, em(4) will silently ignore/disable administratively set TSO4 if the link speed negotiated is < Gigabit Ethernet. However, could you please do an experiment? Revert the patch again and in if_em.h change EM_MAX_SCATTER from 64 to 40, recompile and test. Thanks Marius _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
