From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1214] BCM57508 bnxt_hwrm_send_message Error(timeout) sending msg
Date: Wed, 12 Apr 2023 05:55:17 +0000 [thread overview]
Message-ID: <bug-1214-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1214
Bug ID: 1214
Summary: BCM57508 bnxt_hwrm_send_message Error(timeout) sending
msg
Product: DPDK
Version: 21.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: saurin.suthar@trellix.com
Target Milestone: ---
We are using BCM57508 based add-on Card
AOC-A100G-b2CM(https://www.supermicro.com/en/products/accessories/addon/AOC-A100G-b2CM.php).
This is two port 100G NIC.
Here are the versions:
bnxt_hwrm_ver_get(): 1.10.2:220.0.59.0
Normally traffic goes through with 100G ports. But when i restart my
application multiple times, i start getting following errors. The only way to
recover is to powercycle the appliance. what could be the issue? is there any
sticky behavior in firmware? Is there already patch available for this problem?
Max hw rxq allowed :520
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x00b0, seq_id 25
bnxt_hwrm_stat_ctx_alloc(): failed rc:-110
bnxt_init_chip(): HWRM stat ctx alloc failure rc: ffffff92
bnxt_hwrm_stat_ctx_free(): error 4:0:00000000:0000
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x000d, seq_id 27
bnxt_hwrm_if_change(): failed rc:-110
rte_eth_dev_start(port 6) failed, error=-110
Failed to start port 6
Max hw rxq allowed :520
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x00b0, seq_id 23
bnxt_hwrm_stat_ctx_alloc(): failed rc:-110
bnxt_init_chip(): HWRM stat ctx alloc failure rc: ffffff92
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x000d, seq_id 24
bnxt_hwrm_if_change(): failed rc:-110
rte_eth_dev_start(port 7) failed, error=-110
Failed to start port 7
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3897 bytes --]
reply other threads:[~2023-04-12 5:55 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=bug-1214-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).