[dpdk-test-report] |FAILURE| pw65626[3/7] net/bnxt: log firmware debug notifications
sys_stv at intel.com
sys_stv at intel.com
Fri Feb 21 14:06:16 CET 2020
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65626
_apply issues_
Submitter: Kalesh A P <kalesh-anakkur.purayil at broadcom.com>
Date: 2020-02-06 16:33:10
Reply_mail: 20200206163314.12755-4-kalesh-anakkur.purayil 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
--
break;
default:
PMD_DRV_LOG(DEBUG, "handle_async_event id = 0x%x\n", event_id);
break;
error: patch failed: drivers/net/bnxt/bnxt_cpr.c:133
error: drivers/net/bnxt/bnxt_cpr.c: patch does not apply
*Repo: dpdk
break;
default:
PMD_DRV_LOG(DEBUG, "handle_async_event id = 0x%x\n", event_id);
break;
error: patch failed: drivers/net/bnxt/bnxt_cpr.c:133
error: drivers/net/bnxt/bnxt_cpr.c: patch does not apply
DPDK STV team
More information about the test-report
mailing list