[dpdk-test-report] |FAILURE| pw65637[v2, 5/7] net/bnxt: fix to call port stop when error recovery fails
sys_stv at intel.com
sys_stv at intel.com
Fri Feb 21 14:35:39 CET 2020
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65637
_apply issues_
Submitter: Ajit Khaparde <ajit.khaparde at broadcom.com>
Date: 2020-02-06 18:44:30
Reply_mail: 20200206184432.34360-6-ajit.khaparde at 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 at dpdk.org
--
goto err;
PMD_DRV_LOG(INFO, "Recovered from FW reset\n");
return;
err:
bp->flags |= BNXT_FLAG_FATAL_ERROR;
bnxt_uninit_resources(bp, false);
error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:4022
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
*Repo: dpdk
goto err;
PMD_DRV_LOG(INFO, "Recovered from FW reset\n");
return;
err:
bp->flags |= BNXT_FLAG_FATAL_ERROR;
bnxt_uninit_resources(bp, false);
error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:4022
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
DPDK STV team
More information about the test-report
mailing list