From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: users@dpdk.org
Subject: Sporadic SIGSEGV crash in secondary process, what could be the culprit?
Date: Tue, 21 May 2024 14:20:57 +0200 [thread overview]
Message-ID: <CAO8pfF=Nzt+UKTr9jNht63ah5kHKLvpa3eJeV7k4ZXpRSH7FjA@mail.gmail.com> (raw)
#0 0x00007f427f1e5e51 in pci_vfio_map_resource_secondary () from
/usr/local/lib64/dpdk/pmds-22.0/librte_bus_pci.so.22.0
#1 0x00007f427f1e0c0d in pci_plug.cold () from
/usr/local/lib64/dpdk/pmds-22.0/librte_bus_pci.so.22.0
#2 0x00007f42801bda2f in local_dev_probe () from
/usr/local/lib64/librte_eal.so.22
#3 0x00007f42801d60cc in __handle_primary_request () from
/usr/local/lib64/librte_eal.so.22
#4 0x00007f42801d9cec in eal_alarm_callback () from
/usr/local/lib64/librte_eal.so.22
#5 0x00007f42801dc682 in eal_intr_thread_main () from
/usr/local/lib64/librte_eal.so.22
#6 0x00007f428053c802 in start_thread () from /lib64/libc.so.6
#7 0x00007f42804dc450 in clone3 () from /lib64/libc.so.6
I need a clue about what could cause this crash, on a machine, in
particular, when this crash appears it stays forever, I mean if I
relaunch the primary I get steadily the same crash till I do a power
off and on (a software reboot doesn't help)
I'm on Rocky Linux
reply other threads:[~2024-05-21 12:21 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='CAO8pfF=Nzt+UKTr9jNht63ah5kHKLvpa3eJeV7k4ZXpRSH7FjA@mail.gmail.com' \
--to=a.dibacco.ks@gmail.com \
--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).