From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 104] "dpdk-procinfo" received signal SIGSEGV, Segmentation fault.
Date: Fri, 02 Nov 2018 05:35:02 +0000 [thread overview]
Message-ID: <bug-104-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=104
Bug ID: 104
Summary: "dpdk-procinfo" received signal SIGSEGV, Segmentation
fault.
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
version: make showversion - 18.11.0-rc1
steps:
1. make config T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
2. primary: ./build/l2fwd -c 0xf00 --vdev net_tap0 --vdev net_tap1
--socket-mem=128,0 -- -p 0x3 -T 1
3. secondary: ./x86_64-native-linuxapp-gcc/app/dpdk-procinfo -- --stats
debug logs:
(gdb) bt
#0 find_next (used=true, start=0, arr=0x7f31156090a4)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_fbarray.c:264
#1 fbarray_find (used=true, next=true, start=0, arr=arr@entry=0x7f31156090a4)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_fbarray.c:1001
#2 rte_fbarray_find_next_used (arr=arr@entry=0x7f31156090a4, start=0)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_fbarray.c:1018
#3 0x00005555556d87bc in rte_memseg_walk_thread_unsafe (func=<optimized out>,
arg=<synthetic pointer>)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_memory.c:589
#4 rte_memseg_walk (func=<optimized out>, arg=<synthetic pointer>)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_memory.c:609
#5 rte_eal_check_dma_mask (maskbits=48 '0')
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_memory.c:465
#6 0x0000555555700c0f in pci_one_device_iommu_support_va
(dev=dev@entry=0x55555616dd00)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/drivers/bus/pci/linux/pci.c:618
#7 0x0000555555701cf8 in pci_devices_iommu_support_va ()
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/drivers/bus/pci/linux/pci.c:651
#8 rte_pci_get_iommu_class ()
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/drivers/bus/pci/linux/pci.c:675
#9 0x00005555556da853 in rte_bus_get_iommu_class ()
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_common_bus.c:237
#10 0x00005555556c4d45 in rte_eal_init (argc=<optimized out>, argv=<optimized
out>)
at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/linuxapp/eal/eal.c:919
#11 0x00005555555ecfbd in main (argc=6, argv=0x7fffffffe188)
at /home/saesrv02/Downloads/dpdksrc/procifno/dpdk/app/proc-info/main.c:615
(gdb)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-11-02 5:35 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=bug-104-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).