* Sporadic SIGSEGV crash in secondary process, what could be the culprit?
@ 2024-05-21 12:20 Antonio Di Bacco
0 siblings, 0 replies; only message in thread
From: Antonio Di Bacco @ 2024-05-21 12:20 UTC (permalink / raw)
To: users
#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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-05-21 12:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-21 12:20 Sporadic SIGSEGV crash in secondary process, what could be the culprit? Antonio Di Bacco
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).