From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1909] bnxt: crash in bnxt_alloc_async_cp_ring
Date: Mon, 23 Mar 2026 13:34:44 +0000 [thread overview]
Message-ID: <bug-1909-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1909
Bug ID: 1909
Summary: bnxt: crash in bnxt_alloc_async_cp_ring
Product: DPDK
Version: 26.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: oleksandrn@interfacemasters.com
Target Milestone: ---
commit 7a1f9c782b50a1045a560782717fab20bc370877 (HEAD) net/bnxt: add
multi-doorbell support, causing crash in bnxt_alloc_async_cp_ring, on 57608.
dpdk-testpmd -l 0-5 -a 0000:04:00.1 -- -i
#0 bnxt_alloc_async_cp_ring (bp=0x17ffc9740) at
../drivers/net/bnxt/bnxt_ring.c:839
#1 0x00005555559e5cc1 in bnxt_alloc_mem (reconfig=<optimized out>,
bp=0x17ffc9740)
at ../drivers/net/bnxt/bnxt_ethdev.c:429
#2 bnxt_init_resources (reconfig_dev=<optimized out>, bp=<optimized out>)
at ../drivers/net/bnxt/bnxt_ethdev.c:5988
#3 bnxt_init_resources (bp=0x17ffc9740, reconfig_dev=<optimized out>)
at ../drivers/net/bnxt/bnxt_ethdev.c:5929
#4 0x00005555559e64fa in bnxt_dev_init (eth_dev=0x555556736ac0
<rte_eth_devices>,
params=0x16c640510) at ../drivers/net/bnxt/bnxt_ethdev.c:6727
#5 0x00005555558fc95d in rte_eth_dev_create
(device=device@entry=0x5555569e77b0,
name=0x5555569e78b0 "0000:04:00.1",
priv_data_size=priv_data_size@entry=968,
bus_specific_init=bus_specific_init@entry=0x5555559e2ab0
<eth_dev_pci_specific_init>,
bus_init_params=bus_init_params@entry=0x5555569e77a0,
ethdev_init=ethdev_init@entry=0x5555559e5f90 <bnxt_dev_init>,
init_params=0x0)
at ../lib/ethdev/ethdev_driver.c:370
#6 0x00005555556eb51d in bnxt_pci_probe (pci_drv=<optimized out>,
pci_dev=0x5555569e77a0)
at ../drivers/net/bnxt/bnxt_ethdev.c:7140
#7 0x00005555556b1cb0 in rte_pci_probe_one_driver (dr=dr@entry=0x555556108cc0
<bnxt_rte_pmd>,
dev=dev@entry=0x5555569e77a0) at ../drivers/bus/pci/pci_common.c:299
#8 0x000055555597590c in pci_probe_all_drivers (dev=0x5555569e77a0)
at ../drivers/bus/pci/pci_common.c:383
#9 pci_probe () at ../drivers/bus/pci/pci_common.c:410
#10 0x0000555555941963 in rte_bus_probe () at
../lib/eal/common/eal_common_bus.c:84
--Type <RET> for more, q to quit, c to continue without paging--
#11 0x00005555556ad01c in rte_eal_init (argc=argc@entry=20,
argv=argv@entry=0x7fffffffe3b8)
at ../lib/eal/linux/eal.c:894
#12 0x0000555555846770 in main (argc=20, argv=0x7fffffffe3b8) at
../app/test-pmd/testpmd.c:4584
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-03-23 13:34 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-1909-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