From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 7CA6F1B32A for ; Tue, 14 Nov 2017 07:29:20 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Nov 2017 22:29:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,393,1505804400"; d="scan'208";a="1243782401" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga002.fm.intel.com with ESMTP; 13 Nov 2017 22:29:18 -0800 Received: from lcsmsx153.ger.corp.intel.com (10.186.165.228) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 13 Nov 2017 22:29:15 -0800 Received: from HASMSX110.ger.corp.intel.com ([169.254.6.201]) by LCSMSX153.ger.corp.intel.com ([169.254.8.218]) with mapi id 14.03.0319.002; Tue, 14 Nov 2017 08:29:12 +0200 From: "Rosen, Rami" To: "Wiles, Keith" , James Bensley CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Hard Crash with X710 and Pktgen Thread-Index: AQHTXLaxmRjnBHJ8WEW9ufEPwtnAE6MSt7IAgACyHRA= Date: Tue, 14 Nov 2017 06:29:11 +0000 Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F9444D7AEC@HASMSX110.ger.corp.intel.com> References: <3FEF1E9E-C001-4BD1-ACD7-84AD394F4C52@intel.com> In-Reply-To: <3FEF1E9E-C001-4BD1-ACD7-84AD394F4C52@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.254.154.91] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Hard Crash with X710 and Pktgen 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: Tue, 14 Nov 2017 06:29:21 -0000 Hi, James, First I agree with Keith about that this means something in that configurat= ion is not setup correctly and DPDK is not finding the ports in the system, and has nothing to do with= Pktgen.=20 It seems to me that if you will try to run any application (like testpmd) o= n this setup you will get the same problem. Can you please check and confirm ?=20 Second, I think the root cause for not finding the ports is around this mes= sage ("failed to select IOMMU type") in: ... > EAL: probe driver: 8086:1572 net_i40e > EAL: 0000:09:00.0 failed to select IOMMU type > EAL: Requested device 0000:09:00.0 cannot be used > EAL: PCI device 0000:09:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1572 net_i40e > EAL: 0000:09:00.1 failed to select IOMMU type > EAL: Requested device 0000:09:00.1 cannot be used ... What does " find /sys/kernel/iommu_groups/ -type l" give ?=20 Could it be that 0000:09:00.0 and 0000:09:00.1 belongs to an IOMMU group in= which there are other devices ?=20 Regards, Rami Rosen -----Original Message----- From: users [mailto:users-bounces@dpdk.org] On Behalf Of Wiles, Keith Sent: Monday, November 13, 2017 23:50 To: James Bensley Cc: users@dpdk.org Subject: Re: [dpdk-users] Hard Crash with X710 and Pktgen > On Nov 13, 2017, at 11:35 AM, James Bensley wrote: >=20 > Hi All, >=20 > I have some HPE DL boxes that use "HP" NICs (OEM Intel X710s). I have=20 > compiled DPDK & Pktgen but when I try to run Pktgen the box hard=20 > crashes (it locks up and I have bounce it using IPMI). >=20 > The main output is below although a full transcript of my attempt is > here:=20 > https://null.53bits.co.uk/uploads/linux/applications/dpdk/CentOS-DL120 > -DPDK-NIC-Bind.txt >=20 > Essentially I can bind the NICs to DPDK using the igb_uio driver,=20 > which leads to the hard crash, or I can bind the NICs to DPDK using=20 > the vfio-pci driver but then Pktgen reports that there are no NICs=20 > available to use and exits. In Pktgen I just use the normal rte_eth_device_count() (whatever it is call= ed) to find the ports in the system. This means something in that configura= tion is not setup and DPDK is not finding the ports in the system. Has noth= ing to do with Pktgen that I know of, but I have not tried vfio-pci driver = and can not as I am out of town. >=20 > Does anyone have any ideas whats going on here? What is "failed to=20 > select IOMMU type" telling me? For the hard lockup problem try using testpmd application and see if that t= he same problem if not then it will be next week before I can look at. Let me know if testpmd works or not. >=20 > CentOS 7 / Kernel 4.13 / DPDK 17.08 / Pktgen 3.4.2. >=20 > Cheers, > James. >=20 >=20 > $ sudo ./app/x86_64-native-linuxapp-gcc/pktgen -l 2-6 -n 1 -w 09:00.0=20 > -w 09:00.1 -v -- -P -m [3-4].0 [5-6].1 >=20 > Copyright (c) <2010-2017>, Intel Corporation. All rights reserved. > Powered by DPDK > EAL: Detected 16 lcore(s) > EAL: RTE Version: 'DPDK 17.08.0' > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: PCI device 0000:09:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1572 net_i40e >=20 > << HARD LOCK-UP >> >=20 >=20 > $ sudo ./app/x86_64-native-linuxapp-gcc/pktgen -l 2-6 -n 1 -w 09:00.0=20 > -w 09:00.1 -v -- -P -m [3-4].0 [5-6].1 >=20 > Copyright (c) <2010-2017>, Intel Corporation. All rights reserved. > Powered by DPDK > EAL: Detected 16 lcore(s) > EAL: RTE Version: 'DPDK 17.08.0' > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: VFIO support initialized > EAL: PCI device 0000:09:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1572 net_i40e > EAL: 0000:09:00.0 failed to select IOMMU type > EAL: Requested device 0000:09:00.0 cannot be used > EAL: PCI device 0000:09:00.1 on NUMA socket 0 > EAL: probe driver: 8086:1572 net_i40e > EAL: 0000:09:00.1 failed to select IOMMU type > EAL: Requested device 0000:09:00.1 cannot be used >=20 > Copyright (c) <2010-2017>, Intel Corporation. All rights reserved. > Pktgen created by: Keith Wiles -- >>> Powered by DPDK <<< >=20 >>>> Packet Burst 64, RX Desc 1024, TX Desc 2048, mbufs/port 16384, mbuf=20 >>>> cache 2048 > !PANIC!: *** Did not find any ports to use *** PANIC in=20 > pktgen_config_ports(): > *** Did not find any ports to use ***6: > [./app/x86_64-native-linuxapp-gcc/pktgen() [0x44ba76]] > 5: [/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f16b7238c05]] > 4: [./app/x86_64-native-linuxapp-gcc/pktgen(main+0x57c) [0x448edc]] > 3:=20 > [./app/x86_64-native-linuxapp-gcc/pktgen(pktgen_config_ports+0x15b7) > [0x470d37]] > 2: [./app/x86_64-native-linuxapp-gcc/pktgen(__rte_panic+0xb8)=20 > [0x4432bc]] > 1: [./app/x86_64-native-linuxapp-gcc/pktgen(rte_dump_stack+0x1a)=20 > [0x4b245a]] Aborted Regards, Keith