From: jinag <15720603159@163.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, users@dpdk.org
Subject: Re:Re: vfio module crash when i used dpdk secondary process send pkts
Date: Thu, 24 Aug 2023 09:06:44 +0800 (CST) [thread overview]
Message-ID: <d85421f.126c.18a25145784.Coremail.15720603159@163.com> (raw)
In-Reply-To: <20230823054138.32e6c318@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
This is definitely a bug in the kernel, I am looking to see if there's a bugfix patch in the kernel community. but maybe the app passed an incorrect parameter that caused kernel crash?
The kernel version is 4.18.0-147.5.1.9, it is based on upstream linux at version 4.18.0
At 2023-08-23 20:41:38, "Stephen Hemminger" <stephen@networkplumber.org> wrote:
>On Tue, 22 Aug 2023 09:33:39 +0800 (CST)
>jinag <15720603159@163.com> wrote:
>
>> when I use dpdk to call rte_eth_tx_burst function for sending data from the secondary process, vfio will crash:
>>
>>
>> PID: 60699 TASK: ffff8f0152235df00 CPU: 14 COMMAND: "testlstack02"
>> #0 [ffffa7d8cecc39a8] machine_kexec at ffffffff9045d67b
>> #1 [ffffa7d8ceec3a00] __crash_kexec at ffffffff90562e92
>> #2 [ffffa7d8ceec3ac0] panic at ffffffff904b9b79
>> #3 [ffffa7d8ceec3b48] oops_end at ffffffff904231fc
>> #4 [ffffa7d8ceec3b70] remap_pfn_range at ffffffff90664772
>> #5 [ffffa7d8ceec3c58] remap_pfn_range at ffffffff90664772
>> #6 [ffffa7d8ceec3da0] vfio_pci_mmap_fault at ffffffffc-bda821 [vfio_pci]
>> #7 [ffffa7d8ceec3dc0] __do_fault at ffffffff90662ee9
>> #8 [ffffa7d8ceec3df0] do fault at ffffffff90663b2c
>> #9 [ffffa7d8ceec3e90] __handle_mm_fault at ffffffff90663c9c
>> #10 [ffffa7d8ceec3ec0] handle_mm_fault at ffffffff9047103b
>> #11 [ffffa7d8ceec3ee0] __do_page_fault at ffffffff904712e1
>> #12 [ffffa7d8ceec3f20] do_page_fault at ffffffff9047122e
>> #13 [ffffa7d8ceec3f50] page_fault at ffffffff90e012de
>>
>>
>> The crash occurs when the secondary queue of the secondary process send pkts. I have tested that the primary process and the first queue of the secondary process do not crash. I use i40e X710 nic.
>>
>>
>> Has anyone ever encountered simlilar issue? please provide some ideas for fixing the issue.
>> Thanks!
>>
>If this is a kernel crash, it is a kernel bug. No matter what application does VFIO in kernel
>should not panic. What kernel version are you using? Is it an upstream long-term-stable kernel?
[-- Attachment #2: Type: text/html, Size: 2332 bytes --]
next prev parent reply other threads:[~2023-08-25 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 1:33 jinag
2023-08-23 12:41 ` Stephen Hemminger
2023-08-24 1:06 ` jinag [this message]
2023-09-05 23:25 ` Stephen Hemminger
2023-09-06 1:28 ` jinag
2023-08-28 1:22 ` vfio module crash know " wangpcmic
2023-08-28 1:32 ` Pathak, Pravin
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=d85421f.126c.18a25145784.Coremail.15720603159@163.com \
--to=15720603159@163.com \
--cc=stephen@networkplumber.org \
--cc=users@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).