From: Stephen Hemminger <stephen@networkplumber.org>
To: "junwang01@cestc.cn" <junwang01@cestc.cn>
Cc: dev <dev@dpdk.org>
Subject: Re: dumpcap coredump for 82599 NIC
Date: Wed, 13 Mar 2024 09:29:53 -0700 [thread overview]
Message-ID: <20240313092953.517ac6c7@hermes.local> (raw)
In-Reply-To: <202403131000157988276@cestc.cn>
On Wed, 13 Mar 2024 10:00:17 +0800
"junwang01@cestc.cn" <junwang01@cestc.cn> wrote:
> Hi, when I use dumpcap to capture packets on the 82559 network card, coredump appears.
> The network card bound to ovs-dpdk is 82599, but when I capture packets in other non-82599 network cards (mellanox CX5/C6 or Intel's E810), it is normal. ,
> the dpdk version I am using is 22.11.1, but I see that the call stack is strange, so I am asking you for help.
>
>
>
>
>
> I thought the new version of dpdk might solve it, so I upgraded the dpdk version to 23.11, but the problem is still the same, but the call stack is different and weirder.
>
>
>
>
>
>
> junwang01@cestc.cn
This is not an issue with dumpcap. The problem is in ixgbe driver.
Some part of the code for checking link status is not safe to be called in
secondary process.
The backtrace looks a bit messed up, since ixgbe driver should not be calling i40e code.
Maybe do a debug build (so more complete symbols available).
next prev parent reply other threads:[~2024-03-13 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 2:00 junwang01
2024-03-13 16:29 ` Stephen Hemminger [this message]
2024-03-14 9:22 ` junwang01
2024-03-18 2:48 ` junwang01
2024-03-18 15:06 ` Stephen Hemminger
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=20240313092953.517ac6c7@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=junwang01@cestc.cn \
/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).