From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) by dpdk.org (Postfix) with ESMTP id 049354C8A for ; Wed, 24 Oct 2018 07:11:56 +0200 (CEST) Received: by mail-ot1-f41.google.com with SMTP id k9so3750238otl.10 for ; Tue, 23 Oct 2018 22:11:56 -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 :cc:content-transfer-encoding; bh=7SOC5kFQhS2/LuAqh+eiqojSGkeEToTHE9TBLXdKlKA=; b=IgLKiUAWDEU9LXgF2KMPlwFNKq3OM67+6ZjRMVPNATtyF0sLIkYTHSY0lsCon/FIAr jg/bT0+6I1/R37oqjBTUU94l/+AXIHwO46nnnM4TJZFAB90diFylJkRDtOjpfO1DzV6c mH1hgez3TxhQL2crQQR2U5/fLrGHVFZMIfO7TeIpONLcWsrWto14sOsujpjCvXA7fA9c MMDaFWZy3u3KiYHA/AlZplv8Y4ulcNZsGiN1b37l1meq0acnP5pIHQBv0pFiT8B0bttY W4KP0LbugAtXQBJ6dxo257tp3WSmBNzCKTRt/Elh9UQrROtI60ygdAyESfqtTSdTW7hG n7TQ== 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:cc:content-transfer-encoding; bh=7SOC5kFQhS2/LuAqh+eiqojSGkeEToTHE9TBLXdKlKA=; b=XLPREdWxTVPdguIUQZtSPYvhjbSJV+0cwIy3XgJdieIB4UdmGaH+cD9/ZRJU91SVCf xpcl7N+n7YUFm5lb98NzI1y+ruej0u7MJi1zRAnJauvY5f9idtQkZfAPA7gm1ddpkXuL 9uKMVeuqiOQmkaynpRKKsE0VzZgPkyjb0lkTHDwu4vZIyhsnz0i3Z+MTsLYmO36hy3ov e9sq8zctGsLt+bOofVsltwLD5mEXXlzc02SF++iRj/1aydZZMEsexODyGryY3gy8NzcF vD0cNHOeDIJLjljNt9hIbcTCHCpwB4MsqbLKQhVverEA811nlva9BShLmO3n75N1Wj3j QyKw== X-Gm-Message-State: AGRZ1gJFV0p6Vapw/9SFIZm5UMYcEnLT9KxJgQW0/ZLEbYgKTBQgDg7g 695bn3rc9lUuJqIuLehuHEd6ulM5UGNSoAhHQ+0X1beYK38= X-Google-Smtp-Source: AJdET5cdYfFblazC6TAdJumkv9gtOgNg7SBgToLXfBIBOogU+cbHemG1zHE5noIM+kibLA5HKiPjtsEgjozKe9oqX2Q= X-Received: by 2002:a9d:cd4:: with SMTP id o20mr754223otd.207.1540357916184; Tue, 23 Oct 2018 22:11:56 -0700 (PDT) MIME-Version: 1.0 References: <8A47B1032B7A634D8DEF55F102DE2C9BC089363F@MBX021-E5-VA-2.exch021.domain.local> <8A47B1032B7A634D8DEF55F102DE2C9BC0893A7C@MBX021-E5-VA-2.exch021.domain.local> In-Reply-To: <8A47B1032B7A634D8DEF55F102DE2C9BC0893A7C@MBX021-E5-VA-2.exch021.domain.local> From: Rami Rosen Date: Wed, 24 Oct 2018 08:11:44 +0300 Message-ID: To: srinivas_kotamarti@affirmednetworks.com Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] issues with dpdk-pdump X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 05:11:57 -0000 Hi Srinivas, This works for me on dpdk-18.05, with an I40E nic, running testpmd with the same parameters that you use, " -c ff -n 4 -r 1 -m 800", launching dpdk-pdump as you did, namely with /dpdk-pdump -- --pdump 'port=3D0,queue=3D*,rx-dev=3D/tmp /rc.pcapng,tx-dev=3D/tmp/tc.pcapng' Did you ran testpmd in your successful test I suggested with the same parameters that you are using now for your app, namely "-c ff -n 4 -r 1 -m 800"? if not, I suggest doing so. Also, to be on the safe side, I suggest running DPDK- 18.05 on a clean branch. I see that in the log you posted there is the message: rte_eth_promiscuous_enable: Function not supported Girish rte_eth_dev_confugure called 5 0 1 rte_eth_promiscuous_disable: Function not supported And it seems as if you added logging "Girish rte_eth_dev_confugure called 5= 0 1" so it could be that by mistake you changed something in the DPDK core. Regards, Rami Rosen On Mon, 22 Oct 2018 at 23:49, Srinivas Kotamarti wrote: > > Hi Rami, > Thanks for replying to my message. > > I followed the procedure like you said and here is what I get when I run = the dpdk-pdump after running the testpmd. > > .(8.4.0.0-490.REL)root@an3000-26-5-ssm:/opt/thoroughbred/dpdk/tools# ./dp= dk-pdump -- --pdump 'port=3D0,queue=3D*,rx-dev=3D/tmp/rc.pcapng,tx-dev=3D/= tmp/tc.pcapng' > EAL: Detected 7 lcore(s) > EAL: Detected 1 NUMA nodes > > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_10550_2ce0b99fb94 > EAL: PCI device 0000:03:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > EAL: PCI device 0000:04:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > EAL: PCI device 0000:0b:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > EAL: PCI device 0000:0c:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > EAL: PCI device 0000:13:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > EAL: PCI device 0000:1b:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 15ad:7b0 net_vmxnet3 > rte_eth_promiscuous_disable: Function not supported > rte_eth_allmulticast_disable: Function not supported > Port 4 MAC: 00 00 00 01 02 03 > rte_eth_promiscuous_enable: Function not supported > Girish rte_eth_dev_confugure called 5 0 1 > rte_eth_promiscuous_disable: Function not supported > rte_eth_allmulticast_disable: Function not supported > Port 5 MAC: 00 00 00 01 02 03 > rte_eth_promiscuous_enable: Function not supported > > > I actually past the crash (because of rte_memconfig) that I reported earl= ier. It seems to be because of the --no-shconf that we are passing for rte= _eal_init. Once I removed it I got past the error but now I get the followi= ng error > > dpdk-pump[25734]: EAL: Probing VFIO support... > dpdk-p DPDPK_PDUMP rte_eal_init internal_config.process_type: 1 RTE_PROC= _PRIMARY:0EAL: Probing VFIO support... > dpdk-p EAL: Cannot initialize tailq: RTE_ACL > dpdk-pump[25734]: EAL: Cannot initialize tailq: RTE_ACL > dpdk-pump[25734]: EAL: Cannot init tail queues for objects#012 > dpdk-pump[25734]: PANIC in main(): > dpdk-pump[25734]: Cannot init EAL > dpdk-p Tailq 0: qname:, tqh_first:(nil), tqh_last:0x7= f2b9d85f07c > dpdk-p Tailq 1: qname:, tqh_first:0x7f27fe1f3e40, tqh_= last:0x7f27fe1b8bc0 > dpdk-p Tailq 2: qname:, tqh_first:0x7f27e2a8b300, tqh_last:0x7f= 27e2c05140 > dpdk-p Tailq 3: qname:, tqh_first:(nil), tqh_last:0x7f2b9d8= 5f10c > dpdk-p Tailq 4: qname:, tqh_first:0x7f27fe1b7ec0, tqh_last:0= x7f27fe1b7ec0 > dpdk-p Tailq 5: qname:, tqh_first:0x7f27fe0f6d00, tqh_last:0x7f= 27fde03f40 > dpdk-p Tailq 6: qname:, tqh_first:(nil), tqh_last:0x7f2b9d85f19c > dpdk-p Tailq 7: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 8: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 9: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 10: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 11: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 12: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 13: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 14: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 15: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 16: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 17: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 18: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 19: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 20: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 21: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 22: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 23: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 24: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 25: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 26: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 27: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 28: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 29: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 30: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p Tailq 31: qname:<>, tqh_first:(nil), tqh_last:(nil) > dpdk-p EAL: FATAL: Cannot init tail queues for objects > > > These are the arguments now that we pass to rte_eal_init ' -c ff -n 4 -r = 1 -m 800'. > > And, here is how I start the dpdk-pdump > ./dpdk-pdump -- --pdump 'port=3D0, queue=3D*, rx-dev=3D/tmp/rx.pcap, tx-= dev=3D/tmp/tx.pcap' > > > And I am running with DPDK 18.05. > > Any help is greatly appreciated. > > Thanks. > > --Srinivas > > > -----Original Message----- > From: Rami Rosen [mailto:roszenrami@gmail.com] > Sent: Saturday, October 20, 2018 8:55 AM > To: Srinivas Kotamarti > Cc: users@dpdk.org > Subject: Re: [dpdk-users] issues with dpdk-pdump > > Hi Srinivas, > Can you do a simple test to make sure your setup is ok ? > The suggested test is: instead od running you app, simply do the followin= g: > First, bind a port to DPDK. > Then, run testpmd app (build/app/testpmd; as testpmd calls > rte_pdump_init() if RTE_LIBRTE_PDUMP is defined). > Then run again the dpdk-pdump, and post the result. > For me this works with dpdk-18.08, I am aware that you are using an older= version, but it should work also for you I believe. > Please note that I had to remove the while spaces in the command, but any= how these whitespaces did not cause the error about rte_eal_config_attach()= you had, but a parsing error; after I removed these whitespaces, everythin= g was fine, no errors; what I actually ran is; ./build/app/dpdk-pdump -- -= -pdump 'port=3D0,queue=3D*,rx-dev=3D/work/rc.pcapng,tx-dev=3D/work/tc.pcapn= g' > > and the log shows: > > EAL: Detected 4 lcore(s) > EAL: Detected 1 NUMA nodes > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_15023_7a49f061eb1 > EAL: Probing VFIO support... > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:1584 net_i40e > EAL: PCI device 0000:02:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:1528 net_ixgbe > EAL: PCI device 0000:02:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:1528 net_ixgbe > Port 2 MAC: 00 00 00 01 02 03 > Port 3 MAC: 00 00 00 01 02 03 > > > Regards, > Rami Rosen > http://ramirose.wixsite.com/ramirosen