Test-Label: Intel-compilation Test-Status: FAILURE http://dpdk.org/patch/65625 _apply issues_ Submitter: Kalesh A P Date: 2020-02-06 16:33:08 Reply_mail: 20200206163314.12755-2-kalesh-anakkur.purayil@broadcom.com DPDK git baseline: Repo:dpdk-next-net-brcm, CommitID: 8f8a67919c98bb3ee71db3c22697fc4808630126 Repo:dpdk, CommitID: d0e160a00233b00ba6d242d5fc054438caae6873 *Repo: dpdk-next-net-brcm forwarding is not started on Stingray devices, driver will not receive the async event from FW when there is a FW reset. While exiting testpmd, as part of port stop driver sees this event and this in turn causes a race between port stop and error recovery task. Fixed this by ignoring the fatal/non-fatal async event from FW while stopping port. Fixes: df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW") Cc: stable@dpdk.org -- if (!is_bnxt_in_error(bp)) bnxt_link_update(eth_dev, 1, ETH_LINK_DOWN); /* Clean queue intr-vector mapping */ error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:948 error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply *Repo: dpdk if (!is_bnxt_in_error(bp)) bnxt_link_update(eth_dev, 1, ETH_LINK_DOWN); /* Clean queue intr-vector mapping */ error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:948 error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply DPDK STV team