From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 104] "dpdk-procinfo" received signal SIGSEGV,
 Segmentation fault.
Date: Fri, 02 Nov 2018 05:35:02 +0000
Message-ID: <bug-104-3@http.bugs.dpdk.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://bugs.dpdk.org/show_bug.cgi?id=3D104

            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:=20
1. make config T=3Dx86_64-native-linuxapp-gcc O=3Dx86_64-native-linuxapp-gcc
2. primary:  ./build/l2fwd -c 0xf00 --vdev net_tap0 --vdev net_tap1
--socket-mem=3D128,0  -- -p 0x3 -T 1
3. secondary: ./x86_64-native-linuxapp-gcc/app/dpdk-procinfo -- --stats

debug logs:
(gdb) bt
#0  find_next (used=3Dtrue, start=3D0, arr=3D0x7f31156090a4)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_fbarray.c:264
#1  fbarray_find (used=3Dtrue, next=3Dtrue, start=3D0, arr=3Darr@entry=3D0x=
7f31156090a4)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_fbarray.c:1001
#2  rte_fbarray_find_next_used (arr=3Darr@entry=3D0x7f31156090a4, start=3D0)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_fbarray.c:1018
#3  0x00005555556d87bc in rte_memseg_walk_thread_unsafe (func=3D<optimized =
out>,
    arg=3D<synthetic pointer>)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_memory.c:589
#4  rte_memseg_walk (func=3D<optimized out>, arg=3D<synthetic pointer>)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_memory.c:609
#5  rte_eal_check_dma_mask (maskbits=3D48 '0')
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/common/eal_co=
mmon_memory.c:465
#6  0x0000555555700c0f in pci_one_device_iommu_support_va
(dev=3Ddev@entry=3D0x55555616dd00)
    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_co=
mmon_bus.c:237
#10 0x00005555556c4d45 in rte_eal_init (argc=3D<optimized out>, argv=3D<opt=
imized
out>)
    at
/home/saesrv02/Downloads/dpdksrc/procifno/dpdk/lib/librte_eal/linuxapp/eal/=
eal.c:919
#11 0x00005555555ecfbd in main (argc=3D6, argv=3D0x7fffffffe188)
    at /home/saesrv02/Downloads/dpdksrc/procifno/dpdk/app/proc-info/main.c:=
615
(gdb)

--=20
You are receiving this mail because:
You are the assignee for the bug.=