From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65934[2/2] net/bnxt: fix race when port is stopped and async events are received
Date: 24 Feb 2020 19:41:09 -0800 [thread overview]
Message-ID: <ee68f5$9e8hkb@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65934
_apply issues_
Submitter: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Date: 2020-02-20 04:12:14
Reply_mail: 20200220041214.18053-3-kalesh-anakkur.purayil@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@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
reply other threads:[~2020-02-25 3:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ee68f5$9e8hkb@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).