From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1948] bnxt: bnxt_hwrm_send_message timeout
Date: Thu, 21 May 2026 08:03:37 +0000 [thread overview]
Message-ID: <bug-1948-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1948
Bug ID: 1948
Summary: bnxt: bnxt_hwrm_send_message timeout
Product: DPDK
Version: 26.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: oleksandrn@interfacemasters.com
Target Milestone: ---
Randomly, on rte_eth_dev_configure, see this error, it seems like after that,
traffic doesn't work on this port anymore(or at least returned counters are 0)
Happens somewhat rarely, like 1 out of 10. The problem is that dev_configure
doesn't return failure, so not sure if there is a way to detect this
automatically; maybe rte_eth_link_get can be used.
I also see that there is a similar old Bug 1214
BNXT: bnxt_hwrm_send_message(): Error(timeout) sending msg 0x002a, seq_id 598
BNXT: bnxt_get_hwrm_link_config(): Get link config failed with rc -110
BNXT: bnxt_hwrm_send_message(): Error(timeout) sending msg 0x002a, seq_id 621
BNXT: bnxt_get_hwrm_link_config(): Get link config failed with rc -110
Part Number : BCM957608-P2100GQF20
Chip Number : BCM57608
Chip Name : THOR2
Description : Broadcom BCM57608 2x100G PCIe Ethernet
NIC
Firmware Name : PRIMATE_FW
Firmware Version : 237.1.148.0
RoCE Firmware Version : 237.1.148.0
HWRM Interface Spec : 1.10.3
Kong mailbox channel : Not Applicable
Active Package Version : 237.1.148.0
Package Version on NVM : 237.1.148.0
Active NVM config version : 236.0.2
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-05-21 8:03 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-1948-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