[dpdk-test-report] |FAILURE| pw65934[2/2] net/bnxt: fix race when port is stopped and async events are received

[sys_stv at intel.com]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65934

_apply issues_

Submitter: Kalesh A P <kalesh-anakkur.purayil at broadcom.com>
Date: 2020-02-20 04:12:14
Reply_mail: 20200220041214.18053-3-kalesh-anakkur.purayil at broadcom.com
DPDK git baseline:
	Repo:dpdk-next-net-brcm, CommitID: 8f8a67919c98bb3ee71db3c22697fc4808630126
	Repo:dpdk, CommitID: fbd54248bb18040166a3e6d792282bd5ca5ed240

*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
    
--
	case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY:
		event_data = rte_le_to_cpu_32(async_cmp->event_data1);
		/* timestamp_lo/hi values are in units of 100ms */
		bp->fw_reset_max_msecs = async_cmp->timestamp_hi ?

error: patch failed: drivers/net/bnxt/bnxt_cpr.c:76
error: drivers/net/bnxt/bnxt_cpr.c: patch does not apply
*Repo: dpdk
case HWRM_ASYNC_EVENT_CMPL_EVENT_ID_RESET_NOTIFY:
		event_data = rte_le_to_cpu_32(async_cmp->event_data1);
		/* timestamp_lo/hi values are in units of 100ms */
		bp->fw_reset_max_msecs = async_cmp->timestamp_hi ?

error: patch failed: drivers/net/bnxt/bnxt_cpr.c:76
error: drivers/net/bnxt/bnxt_cpr.c: patch does not apply

DPDK STV team