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?
Marius
Index: sys/dev/e1000/if_em.c
===================================================================
--- sys/dev/e1000/if_em.c (revision 294962)
+++ sys/dev/e1000/if_em.c (working copy)
@@ -1377,8 +1377,15 @@ em_init_locked(struct adapter *adapter)
ifp->if_hwassist = 0;
if (ifp->if_capenable & IFCAP_TXCSUM)
ifp->if_hwassist |= (CSUM_TCP | CSUM_UDP);
- if (ifp->if_capenable & IFCAP_TSO4)
- ifp->if_hwassist |= CSUM_TSO;
+ /*
+ ** There have proven to be problems with TSO when not
+ ** at full gigabit speed, so disable the assist automatically
+ ** when at lower speeds. -jfv
+ */
+ if (ifp->if_capenable & IFCAP_TSO4) {
+ if (adapter->link_speed == SPEED_1000)
+ ifp->if_hwassist |= CSUM_TSO;
+ }
/* Configure for OS presence */
em_init_manageability(adapter);
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[email protected]"