On Mon, Aug 23, 2021 at 8:49 AM Somnath Kotur
<[email protected]> wrote:
>
> On chips like Thor, port stop/start sequence could result in a crash
> in the application. This is because of false detection of a bad
> opaque in the Rx completion and the subsequent kicking-in of the ring
> reset code to recover from the condition.
> The root cause being that the port stop/start would result in the HW
> starting with fresh values, while the driver internal tracker variable
> `rx_next_cons` is still pointing to a stale value.
> Fix this by resetting rx_next_cons to 0 in bnxt_init_one_rx_ring()
>
> Fixes: 03c8f2fe111c ("net/bnxt: detect bad opaque in Rx completion")
> Cc: [email protected]
>
> Signed-off-by: Somnath Kotur <[email protected]>
> Reviewed-by: Kalesh AP <[email protected]>
> Reviewed-by: Ajit Khaparde <[email protected]>
Thanks Ferruh.
Patch applied to dpdk-next-net-brcm
