From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3E340A0471 for ; Tue, 13 Aug 2019 09:25:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1F76C5681; Tue, 13 Aug 2019 09:25:25 +0200 (CEST) Received: from mail-vk1-f196.google.com (mail-vk1-f196.google.com [209.85.221.196]) by dpdk.org (Postfix) with ESMTP id 56EE45681 for ; Tue, 13 Aug 2019 09:25:23 +0200 (CEST) Received: by mail-vk1-f196.google.com with SMTP id b64so21263224vke.13 for ; Tue, 13 Aug 2019 00:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=hlgEcX4SKgGwUkIumfaNjUCy91QKSJ0d5ha3SCA5hVc=; b=am6+kg2bwCQ7/4jy/yoqB/RSMGTKcrucEdKBMq2d8u3DH+HLxrE3WHKZs4QkV/PLZS 955t9/u+3Scor+zhw4FLIkSLmF6UOnhAAGg1pVCPnKuvuzoqP9lcPpfm+Rcw5Fr2t8kd eyeqHXdBB3+IU3EHAvpnlJWku8SdikamqxNXKp6bVBtu2iv1hKw8rgnT16XTLccmDrXT DGjxO9VarPEjqOc4543kigir/DReExrzvRav4TOMy4GHvYoPfJMWbtnxq89xwnkM8I1i xcvD5E3wjYeGFnNdDJK2W34Xv7JRETFrehilczJsQPMifCEDmcYEmiE6muFOFollO6wo L1Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=hlgEcX4SKgGwUkIumfaNjUCy91QKSJ0d5ha3SCA5hVc=; b=dCHcaGTDjWN5LwncpSIzgoSXqv0hWu4blgsh56o3rEkhZtWcM5HtkU4dnms9R2eEyb FXpxNFofpuovCIbAv7bNe0nT7FqxOib24f1NwJnBghcvYackpfbvIOAvlzn9dp8Mc2Rn HdxuMq1Bpv3CvLnZH1+wYvirGccvznGs8hi3+pyl2f4zSn8UTughYWBxQueluw00R7QC saDvR6YcNLaZbCfqto+PuLD81Y1TR0ikgJueTHekUNzUsKezhhq3hhhHbD2fpqI7kF0M j0J9RsFPFYbb0nLGyKN71jncyHC7QpOGPOXyko2Cj2v/VM9WHeiEIDWJvH6g8F2dUAKD 2hew== X-Gm-Message-State: APjAAAVOyjiE/wQsiMLAn7qpZS8hOO2X7IWaV+V/JUlSewMfVXqwGqTp UyrEtIruDEirEj7MXx2LfPkSPmVNpPYzX7mXXGIouNzhjTM= X-Google-Smtp-Source: APXvYqycYa+mfLRWq/iOk4q82jwiREKlM0PIG40rDBwQ3wDsyIXKffKu+NMMS35cByfIFU2YdHW8+/1EOYG/vvtTUl4= X-Received: by 2002:a1f:3146:: with SMTP id x67mr3421480vkx.47.1565681122300; Tue, 13 Aug 2019 00:25:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: vikram T Date: Tue, 13 Aug 2019 12:55:10 +0530 Message-ID: To: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] DPDK failes to initailze on VMXNet3 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Additionally the dpdk-devbind.py shows as follows: [root@vprobe mnt]# /var/cache/ocsm/dpdk/dpdk-18.11/usertools/dpdk-devbind.py -s Network devices using DPDK-compatible driver ============================================ 0000:03:00.0 'VMXNET3 Ethernet Controller 07b0' drv=igb_uio unused=vmxnet3 Network devices using kernel driver =================================== 0000:02:00.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' if=ens32 drv=e1000 unused=igb_uio *Active* Any pointers would be very helpful Thanks in Advance Regards Vikram On Tue, Aug 13, 2019 at 9:39 AM vikram T wrote: > Hi, > When initialing the DPDK failed with the Below error on VMXNet3: > > > > > > > > > > *Aug 9 14:05:34 vprobe rat_dpdk_sniffer[10768]: EAL: Probing VFIO > support...Aug 9 14:05:34 vprobe rat_dpdk_sniffer[10768]: EAL: PCI device > 0000:02:00.0 on NUMA socket -1Aug 9 14:05:34 vprobe > rat_dpdk_sniffer[10768]: EAL: Invalid NUMA socket, default to 0Aug 9 > 14:05:34 vprobe rat_dpdk_sniffer[10768]: EAL: probe driver: 8086:100f > net_e1000_emAug 9 14:05:34 vprobe rat_dpdk_sniffer[10768]: EAL: PCI device > 0000:03:00.0 on NUMA socket 0Aug 9 14:05:34 vprobe kernel: igb_uio > 0000:03:00.0: uio device registered with irq 58Aug 9 14:05:34 vprobe > rat_dpdk_sniffer[10768]: EAL: probe driver: 15ad:7b0 net_vmxnet3Aug 9 > 14:05:34 vprobe rat_dpdk_sniffer[10768]: PANIC in > rte_eth_dev_shared_data_prepare():Aug 9 14:05:34 vprobe > rat_dpdk_sniffer[10768]: Cannot allocate ethdev shared data* > > With the BackTrace pointing to : > > > > > > > > > > > > > > *(gdb) bt#0 0x00007ffff54612c7 in raise () from /lib64/libc.so.6#1 > 0x00007ffff54629b8 in abort () from /lib64/libc.so.6#2 0x00000000004eab34 > in __rte_panic ()#3 0x000000000050cbf8 in rte_eth_dev_shared_data_prepare > ()#4 0x000000000050de1c in rte_eth_dev_allocate ()#5 0x0000000000667025 > in eth_vmxnet3_pci_probe ()#6 0x00000000005b4178 in pci_probe_all_drivers > ()#7 0x00000000005b42bc in rte_pci_probe ()#8 0x000000000053642c in > rte_bus_probe ()#9 0x00000000005242ee in rte_eal_init ()#10 > 0x00000000006c24c7 in rat::dpdk::init (cfg=...) at > ../../rat/src/sniffer/dpdk_utils.cc:71* > > The sample application testpmd was running successfully: > > > > > > > > > > > > > > > > > > > > > > > > > > > > *[root@vprobe test-pmd]# ./testpmd -l 0-3 -n 4 -- -i --portmask=0x1 > --nb-cores=2EAL: Detected 16 lcore(s)EAL: Detected 4 NUMA nodesEAL: > Multi-process socket /var/run/dpdk/rte/mp_socketEAL: No free hugepages > reported in hugepages-2048kBEAL: No free hugepages reported in > hugepages-2048kBEAL: Probing VFIO support...EAL: PCI device 0000:02:00.0 on > NUMA socket -1EAL: Invalid NUMA socket, default to 0EAL: probe driver: > 8086:100f net_e1000_emEAL: PCI device 0000:03:00.0 on NUMA socket 0EAL: > probe driver: 15ad:7b0 net_vmxnet3Interactive-mode selectedtestpmd: create > a new mbuf pool : n=171456, size=2176, socket=0testpmd: > preferred mempool ops selected: ring_mp_mcWarning! port-topology=paired and > odd forward ports number, the last port will pair with itself.Configuring > Port 0 (socket 0)Port 0: 00:0C:29:36:B2:F1Checking link > statuses...Donetestpmd> startio packet forwarding - ports=1 - cores=1 - > streams=1 - NUMA support enabled, MP allocation mode: nativeLogical Core 1 > (socket 0) forwards packets on 1 streams: RX P=0/Q=0 (socket 0) -> TX > P=0/Q=0 (socket 0) peer=02:00:00:00:00:00* > > Additionally I observed that on this virtual machine file > *"/sys/bus/pci/devices/0000:03:00.0/numa_node"* is set as -1 and when > sample application are run the programs detects 4 NUMA Nodes. > But on any other physical machine it is properly set to appropriate > numa_node. > > > It would be of great help if I get pointers on why the initialization > fails here. > > Regards > Vikram >