From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1564] Broadcom doesn't receive network packets via RX Interrupt (infinite lock rte_epoll_wait)
Date: Sat, 12 Oct 2024 21:40:08 +0000 [thread overview]
Message-ID: <bug-1564-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1564
Bug ID: 1564
Summary: Broadcom doesn't receive network packets via RX
Interrupt (infinite lock rte_epoll_wait)
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: lucas@easy-way.app
Target Milestone: ---
The rte_epoll_wait function is never returning, I believe that the interrupts
are not being properly configured for the bnxt_en driver after upgrade.
Bug NIC: Broadcom NetXtreme-E BCM57508
It is important to note that the same code works on Mellanox NIC, more
precisely Mellanox ConnectX-5 Ex MT28800
Steps to reproduce:
1. Update the NIC firmware using niccli utility
Download:
https://docs.broadcom.com/docs/NXE_Linux_niccli_231.0.162.1
Command:
./niccli -i 1 install -online
Online Tutorial:
https://techdocs.broadcom.com/us/en/storage-and-ethernet-connectivity/ethernet-nic-controllers/bcm957xxx/adapters/software-installation/updating-the-firmware/updating-the-firmware-online.html
2. Change IP 67.159.40.18/24 to your network IP
3. Change IP 67.159.40.17 to your default gateway
4. Compile the code below
The final C++ code (cpp):
https://pastebin.com/VH6PLiTU
5. Run the binary generated by the previous compilation
You will see the error, if you remove rte epoll_wait the ping works normally,
but if you use rte_epoll_wait it will never return
If necessary, I can provide access to my dedicated server that uses this
specific Broadcom NIC.
I can also provide access to the VNC console to access the server even after
starting the application.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4130 bytes --]
reply other threads:[~2024-10-12 21:40 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-1564-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.