From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8A8C2A0C47 for <public@inbox.dpdk.org>; Fri, 19 Nov 2021 06:23:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1A75D40143; Fri, 19 Nov 2021 06:23:22 +0100 (CET) Received: from mail-pg1-f178.google.com (mail-pg1-f178.google.com [209.85.215.178]) by mails.dpdk.org (Postfix) with ESMTP id 0B7FB40140 for <users@dpdk.org>; Fri, 19 Nov 2021 06:23:20 +0100 (CET) Received: by mail-pg1-f178.google.com with SMTP id p17so7670748pgj.2 for <users@dpdk.org>; Thu, 18 Nov 2021 21:23:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=PcuGrOwDpWWwl/3PHx2fug3bQ3aSgeXDPdo4stE2qfU=; b=YJnSO0yXHt48VDEuJaBS2GHI0tFHB3SlYaMJRJdh6Ocyu4WM7ALKzhdxeYerEuXlmU tpGxkikICGTV+E6Q2rul2gnKy2TE6+6wL/wq3wAK8i7KzU/NOHoj/lGHJOtx3BrwBfrr G16CJ3QphCc74g5OwK7gu0eNCkM8AnYgg/8NOREuHRcHKYqQfcRr9UUEQiB2yDsL2s/+ SIzUl9jPKWq+CZaal8mnhoEODonCPQuO2KFoQdGu/Jw0hK9flv3ic2AYOGuLFzcuAUJ5 GtjHL0CT/LnNOMjKO956cHldWqsdrztc+/0ZyMvz6hWMbX8ak/gJduistm3guOjZkVLV BAYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=PcuGrOwDpWWwl/3PHx2fug3bQ3aSgeXDPdo4stE2qfU=; b=xFgPsVM4aNeNclLEcWqoaEbQpOXWBAFS15AqlNSTEqtHrxE5VsBtz3g9P0+S9gTTzj p62oK25sOhCnECZuGo8VhiGQBUpKSRla4qVdPSVhih0IiJcOkwyUwQW6MBA4Eh68IA1v cl8h8pPTTByOrxGCooFx8xC+hDatBnByNBi2ZFcrnR06hwuTRbRheGxkPdDIHJ3xdV1o 0Fi6WX2gzpdBvIXGZXPsXbK9vffuv2RoLmRjzFe5xs8Hlp8YkwRokmRCjMQlTJ8Lklpj EEUfRAt2+zBGOxtbN5M6h7Zzbm3+likyas7VMCDh0gTj+vsYxfNE0DkJ3V/oMnAZw0oH 49yQ== X-Gm-Message-State: AOAM530zTYJsCpO3jSxoDvLm5mvpvO1M/sbwAKdYjH1SxbD2uAK9W1Xl GpUURypnlSNpELK0yocQcz3Dlg== X-Google-Smtp-Source: ABdhPJyhrbYnq0tRr440dneL59kMgqjbSbMo4hY7lMWGBoO+U9IsP9hzlmm5YfG+1uaWPX+5q4V2yA== X-Received: by 2002:a63:b4a:: with SMTP id a10mr5177156pgl.360.1637299400068; Thu, 18 Nov 2021 21:23:20 -0800 (PST) Received: from hermes.local (204-195-33-123.wavecable.com. [204.195.33.123]) by smtp.gmail.com with ESMTPSA id h6sm1370597pfi.174.2021.11.18.21.23.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Nov 2021 21:23:19 -0800 (PST) Date: Thu, 18 Nov 2021 21:23:16 -0800 From: Stephen Hemminger <stephen@networkplumber.org> To: =?UTF-8?B?5buW5pu46I+v?= <sim860927@gmail.com> Cc: "Pattan, Reshma" <reshma.pattan@intel.com>, "users@dpdk.org" <users@dpdk.org> Subject: Re: Pdump Didn't capture the packet Message-ID: <20211118212316.256bc14a@hermes.local> In-Reply-To: <CANq=q41cE4zNw0Wi_O+05mnCBixf=aYoXBgy2g-AXf9Sn00vhg@mail.gmail.com> References: <CANq=q43rnJEJf=cer5Z9Hg1aF6ZQFoa7NDuYd8YEzuRKH8fL2A@mail.gmail.com> <BYAPR11MB3366BF65069293CCD771AE63FF989@BYAPR11MB3366.namprd11.prod.outlook.com> <CANq=q40o_4OpLFOxDssvnRaS1Ku0pdifvRTwK19C_By2oxxhgA@mail.gmail.com> <BYAPR11MB3366D0C24079D21F31D629B3FF9A9@BYAPR11MB3366.namprd11.prod.outlook.com> <CANq=q41cE4zNw0Wi_O+05mnCBixf=aYoXBgy2g-AXf9Sn00vhg@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org On Fri, 19 Nov 2021 09:47:52 +0800 =E5=BB=96=E6=9B=B8=E8=8F=AF <sim860927@gmail.com> wrote: > Dear, >=20 >=20 >=20 > Yes, for the pcap, it is empty. >=20 > I observe that on the pdump side, it will stuck in *EAL: VFIO support > initialized *(red log below). After the primary application terminates, it > will print the remaining log (blue log below). Is that normal ? >=20 > *- Here's the log of pdump* > [oran@localhost pdump]$ sudo ./dpdk-pdump --file-prefix wls_1 -- --pdump > 'port=3D0,queue=3D*,tx-dev=3D/home/oran/Music/tx.pcap,rx-dev=3D/home/oran= /Music/rx.pcap' > [sudo] password for oran: EAL: Detected 96 lcore(s) EAL: Detected 2 NUMA > nodes EAL: Multi-process socket > /var/run/dpdk/wls_1/mp_socket_9612_d352314e70d54 EAL: Selected IOVA mode > 'VA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI > device 0000:00:04.0 on NUMA socket 0 EAL: probe driver: 8086:2021 > rawdev_ioat EAL: PCI device 0000:00:04.1 on NUMA socket 0 EAL: probe > driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.2 on NUMA socket= 0 > EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.3 on > NUMA socket 0 EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device > 0000:00:04.4 on NUMA socket 0 EAL: probe driver: 8086:2021 rawdev_ioat EA= L: > PCI device 0000:00:04.5 on NUMA socket 0 EAL: probe driver: 8086:2021 > rawdev_ioat EAL: PCI device 0000:00:04.6 on NUMA socket 0 EAL: probe > driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.7 on NUMA socket= 0 > EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:18:00.0 on > NUMA socket 0 EAL: probe driver: 8086:1572 net_i40e EAL: PCI device > 0000:18:00.1 on NUMA socket 0 EAL: probe driver: 8086:1572 net_i40e EAL: > PCI device 0000:18:0a.0 on NUMA socket 0 EAL: probe driver: 8086:154c > net_i40e_vf EAL: using IOMMU type 1 (Type 1) EAL: PCI device 0000:18:0a.1 > on NUMA socket 0 EAL: probe driver: 8086:154c net_i40e_vf EAL: PCI device > 0000:3d:00.0 on NUMA socket 0 EAL: probe driver: 8086:37d2 net_i40e EAL: > PCI device 0000:3d:00.1 on NUMA socket 0 EAL: probe driver: 8086:37d2 > net_i40e EAL: PCI device 0000:80:04.0 on NUMA socket 1 EAL: probe driver: > 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.1 on NUMA socket 1 EAL: > probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.2 on NUMA > socket 1 EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device > 0000:80:04.3 on NUMA socket 1 EAL: probe driver: 8086:2021 rawdev_ioat EA= L: > PCI device 0000:80:04.4 on NUMA socket 1 EAL: probe driver: 8086:2021 > rawdev_ioat EAL: PCI device 0000:80:04.5 on NUMA socket 1 EAL: probe > driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.6 on NUMA socket= 1 > EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.7 on > NUMA socket 1 EAL: probe driver: 8086:2021 rawdev_ioat Port 2 MAC: 02 70 = 63 > 61 70 00 Port 3 MAC: 02 70 63 61 70 01 core (0), capture for (1) tuples - > port 0 device ((null)) queue 65535 Primary process is no longer active, > exiting... EAL: failed to send to (/var/run/dpdk/wls_1/mp_socket) due to > Connection refused EAL: Fail to send request > /var/run/dpdk/wls_1/mp_socket:mp_pdump PDUMP: client request for pdump > enable/disable failed EAL: failed to send to > (/var/run/dpdk/wls_1/mp_socket) due to Connection refused EAL: Fail to se= nd > request /var/run/dpdk/wls_1/mp_socket:eal_dev_mp_request EAL: Cannot send > request to primary EAL: Failed to send hotplug request to primary EAL: > failed to send to (/var/run/dpdk/wls_1/mp_socket) due to Connection refus= ed > EAL: Fail to send request /var/run/dpdk/wls_1/mp_socket:eal_dev_mp_request > EAL: Cannot send request to primary EAL: Failed to send hotplug request to > primary ##### PDUMP DEBUG STATS ##### -packets dequeued: 0 -packets > transmitted to vdev: 0 -packets freed: 0 Since pdump relies on primary secondary process setup to be working, it is best to debug that first. It might be easier to make sure dpdk-procinfo works.