automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw65636[v2, 2/7] net/bnxt: fix default timeout for command to get FW version
Date: 21 Feb 2020 05:35:33 -0800	[thread overview]
Message-ID: <ee68f5$9dd7bt@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3972 bytes --]

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

_apply issues_

Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: 2020-02-06 18:44:27
Reply_mail: 20200206184432.34360-3-ajit.khaparde@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
    
--
#define HWRM_CMD_TIMEOUT		50000
	/* default HWRM request timeout value */
	uint32_t			hwrm_cmd_timeout;


error: patch failed: drivers/net/bnxt/bnxt.h:606
error: drivers/net/bnxt/bnxt.h: patch does not apply
Checking patch drivers/net/bnxt/bnxt_ethdev.c...
error: while searching for:
	bp->flags &= ~BNXT_FLAG_FATAL_ERROR;

	do {
		rc = bnxt_hwrm_ver_get(bp);
		if (rc == 0)
			break;
		rte_delay_ms(BNXT_FW_READY_WAIT_INTERVAL);

error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:3998
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_hwrm.c...
error: while searching for:
	if (bp->flags & BNXT_FLAG_FATAL_ERROR)
		return 0;

	/* For VER_GET command, set timeout as 50ms */
	if (rte_cpu_to_le_16(req->req_type) == HWRM_VER_GET)
		timeout = HWRM_CMD_TIMEOUT;
--
		timeout = bp->hwrm_cmd_timeout;

	if (bp->flags & BNXT_FLAG_SHORT_CMD ||
	    msg_len > bp->max_req_len) {

error: patch failed: drivers/net/bnxt/bnxt_hwrm.c:100
error: drivers/net/bnxt/bnxt_hwrm.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_hwrm.h...
error: while searching for:
int bnxt_hwrm_ctx_qstats(struct bnxt *bp, uint32_t cid, int idx,
			 struct rte_eth_stats *stats, uint8_t rx);
--
int bnxt_hwrm_ver_get(struct bnxt *bp);

int bnxt_hwrm_vnic_alloc(struct bnxt *bp, struct bnxt_vnic_info *vnic);
int bnxt_hwrm_vnic_cfg(struct bnxt *bp, struct bnxt_vnic_info *vnic);

error: patch failed: drivers/net/bnxt/bnxt_hwrm.h:120
error: drivers/net/bnxt/bnxt_hwrm.h: patch does not apply
*Repo: dpdk
#define HWRM_CMD_TIMEOUT		50000
	/* default HWRM request timeout value */
	uint32_t			hwrm_cmd_timeout;


error: patch failed: drivers/net/bnxt/bnxt.h:606
error: drivers/net/bnxt/bnxt.h: patch does not apply
Checking patch drivers/net/bnxt/bnxt_ethdev.c...
error: while searching for:
	bp->flags &= ~BNXT_FLAG_FATAL_ERROR;

	do {
		rc = bnxt_hwrm_ver_get(bp);
		if (rc == 0)
			break;
		rte_delay_ms(BNXT_FW_READY_WAIT_INTERVAL);

error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:3998
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_hwrm.c...
error: while searching for:
	if (bp->flags & BNXT_FLAG_FATAL_ERROR)
		return 0;

	/* For VER_GET command, set timeout as 50ms */
	if (rte_cpu_to_le_16(req->req_type) == HWRM_VER_GET)
		timeout = HWRM_CMD_TIMEOUT;
--
		timeout = bp->hwrm_cmd_timeout;

	if (bp->flags & BNXT_FLAG_SHORT_CMD ||
	    msg_len > bp->max_req_len) {

error: patch failed: drivers/net/bnxt/bnxt_hwrm.c:100
error: drivers/net/bnxt/bnxt_hwrm.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_hwrm.h...
error: while searching for:
int bnxt_hwrm_ctx_qstats(struct bnxt *bp, uint32_t cid, int idx,
			 struct rte_eth_stats *stats, uint8_t rx);
--
int bnxt_hwrm_ver_get(struct bnxt *bp);

int bnxt_hwrm_vnic_alloc(struct bnxt *bp, struct bnxt_vnic_info *vnic);
int bnxt_hwrm_vnic_cfg(struct bnxt *bp, struct bnxt_vnic_info *vnic);

error: patch failed: drivers/net/bnxt/bnxt_hwrm.h:120
error: drivers/net/bnxt/bnxt_hwrm.h: patch does not apply

DPDK STV team

                 reply	other threads:[~2020-02-21 13:35 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$9dd7bt@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).