From: Suresh Reddy <suresh.re...@broadcom.com> Date: Mon, 23 Jul 2018 10:25:23 -0400
> Driver dumps tx_queue, tx_compl, pending SKBs information in tx_timeout. > This debug data used to idenfiy the cause of the time out. > > Also reset Lancer chip in tx_timeout. > > Signed-off-by: Suresh Reddy <suresh.re...@broadcom.com> The purpose of the tx timeout NDO operation is to do whatever is necessary to handle the TX timeout. Outputting debugging information is useful, but is secondary. I see that you do reset the Lancer, but that is far from what really needs to happen here. When you get a TX timeout, the hardware is not processing TX ring entries, nor signalling completion any longer. Therefore the only way to get things going again is to reset all of the TX side data structure and logic. This means shutting down the TX engine, freeing up all of the TX SKBs in the ring, resetting the TX ring software state, and then finally reprogramming the head/tail pointer registers and re-enabling TX DMA processing.
