be2net: Handle transmit completion errors in Lancer

Browse source

If the driver receives a TX CQE with status as 0x1 or 0x9 or 0xb,
the completion indexes should not be used. The driver must stop
consuming CQEs from this TXQ/CQ. The TXQ from this point on-wards
to be in a bad state. Driver should destroy and recreate the TXQ.

0x1: LANCER_TX_COMP_LSO_ERR
0x9 LANCER_TX_COMP_SGE_ERR
0xb: LANCER_TX_COMP_PARITY_ERR

Reset the adapter if driver sees this error in TX completion. Also
adding sge error counter in ethtool stats.

Signed-off-by: Suresh Reddy <suresh.reddy@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Suresh Reddy 2018-02-06 08:52:42 -05:00 • committed by David S. Miller

parent 3df40aad1a

commit ffc3962010

4 changed files with 69 additions and 48 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

drivers/net/ethernet/emulex/benet/be.h

View file

1

drivers/net/ethernet/emulex/benet/be_ethtool.c

View file

1

drivers/net/ethernet/emulex/benet/be_hw.h

View file

108

drivers/net/ethernet/emulex/benet/be_main.c

View file