Re: [PATCH 2/2] 8139cp: Call __cp_set_rx_mode() from cp_tx_timeout()

On Sun, 2015-09-20 at 22:24 -0700, David Miller wrote: > From: David Woodhouse > Date: Fri, 18 Sep 2015 00:21:54 +0100 > > > Unless we reset the RX config, on real hardware I don't seem to > receive > > any packets after a TX timeout. > > > > Signed-off-by: David Woodhouse

Re: [PATCH 2/2] 8139cp: Call __cp_set_rx_mode() from cp_tx_timeout()

On Mon, 2015-09-21 at 14:59 +0100, David Woodhouse wrote: > After which, I think we might be able to turn on TX checksumming by > default and I also have a way to implement early detection of the TX > stall I've been seeing. This is a patch I've been playing with to catch the TX stall. When it

Re: [PATCH 2/2] 8139cp: Call __cp_set_rx_mode() from cp_tx_timeout()

-- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/2] 8139cp: Call __cp_set_rx_mode() from cp_tx_timeout()

From: David Woodhouse Date: Fri, 18 Sep 2015 00:21:54 +0100 > Unless we reset the RX config, on real hardware I don't seem to receive > any packets after a TX timeout. > > Signed-off-by: David Woodhouse Applied. -- To unsubscribe from this list:

[PATCH 2/2] 8139cp: Call __cp_set_rx_mode() from cp_tx_timeout()

Unless we reset the RX config, on real hardware I don't seem to receive any packets after a TX timeout. Signed-off-by: David Woodhouse --- Now it does actually recover from the TX timeout, lots of the time. Sometimes it still hits that IRQ storm, which probably