From: Stephen Hemminger <stephen@networkplumber.org>
To: deleleaf <deleleaf@126.com>
Cc: dev@dpdk.org
Subject: Re: a bug in r8169_rxtx.c in dpdk 25.07 version
Date: Tue, 16 Sep 2025 06:47:50 -0700 [thread overview]
Message-ID: <20250916064750.6127fb0c@hermes.local> (raw)
In-Reply-To: <410a3e7a.3866.19950982d33.Coremail.deleleaf@126.com>
On Tue, 16 Sep 2025 11:36:14 +0800 (CST)
deleleaf <deleleaf@126.com> wrote:
> hi ,
> I try to driver a nic ('RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller 8168') ,
> when I use 'rte_eth_dev_configure' which tx port set to 0, then running 'rte_eth_dev_start' may crash !
> because at this time 'tx_queues' is null, but still access with 'dev->data->tx_queue' at r8169_rxtx.c:1102.
> detail stack info picture in the attachment.
A small program (or using testpmd) to reproduce would help.
An application needs call rte_eth_tx_queue_setup() on the transmit queue.
See any of the examples like examples/l3fwd to see the startup order.
prev parent reply other threads:[~2025-09-16 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 3:36 deleleaf
2025-09-16 13:47 ` Stephen Hemminger [this message]
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=20250916064750.6127fb0c@hermes.local \
--to=stephen@networkplumber.org \
--cc=deleleaf@126.com \
--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).