From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3426.houston.hp.com (g4t3426.houston.hp.com [15.201.208.54]) by dpdk.org (Postfix) with ESMTP id E2B94569C for ; Fri, 20 Mar 2015 16:31:35 +0100 (CET) Received: from G4W6310.americas.hpqcorp.net (g4w6310.houston.hp.com [16.210.26.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g4t3426.houston.hp.com (Postfix) with ESMTPS id CEC8073; Fri, 20 Mar 2015 15:31:33 +0000 (UTC) Received: from G4W6302.americas.hpqcorp.net (16.210.26.227) by G4W6310.americas.hpqcorp.net (16.210.26.217) with Microsoft SMTP Server (TLS) id 14.3.169.1; Fri, 20 Mar 2015 15:30:36 +0000 Received: from G4W3231.americas.hpqcorp.net ([169.254.11.35]) by G4W6302.americas.hpqcorp.net ([16.210.26.227]) with mapi id 14.03.0169.001; Fri, 20 Mar 2015 15:30:36 +0000 From: "Roberts, Lee A." To: Nissim Nisimov , "dev@dpdk.org" Thread-Topic: Queries on DPDK working with XL710 intel NIC Thread-Index: AdBiaigzoMVE8bpXSxeCGNqpWpVq4QAsxVcgAAD5P6A= Date: Fri, 20 Mar 2015 15:30:35 +0000 Message-ID: References: <94AA676E9B9A384A844E7692F3CAD906423BDF6F@ILMB1.corp.radware.com> <94AA676E9B9A384A844E7692F3CAD906423BF271@ILMB1.corp.radware.com> In-Reply-To: <94AA676E9B9A384A844E7692F3CAD906423BF271@ILMB1.corp.radware.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [16.210.48.14] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Queries on DPDK working with XL710 intel NIC X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2015 15:31:36 -0000 Nissim, Recent HP ProLiant servers use RMRRs (see https://www.kernel.org/doc/Docume= ntation/Intel-IOMMU.txt) to communicate management information. Use of these RMRRs conflicts with I= OMMU usage. On ProLiant Gen8 servers, you have a couple options: 1) If you are doing bare-metal testing and don't require the IOMMU, turn it= off. Some kernels have "intel_iommu=3Don" set by default. You should be able= to use "intel_iommu=3Doff" if your kernel enables IOMMU by default. 2) If your application requires the IOMMU, there are BIOS parameters that c= an be configured to eliminate the RMRRs on a slot-by-slot basis. (I will send= instructions for this separately, since it is not a DPDK issue.) - Lee Roberts -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov Sent: Friday, March 20, 2015 8:56 AM To: Nissim Nisimov; dev@dpdk.org Subject: Re: [dpdk-dev] Queries on DPDK working with XL710 intel NIC Seems like the issue related to the following errors I see in dmesg: [48459.391753] dmar: DRHD: handling fault status reg 302 [48459.392092] dmar: DMAR:[DMA Read] Request device [21:00.1] fault addr fb= addd000=20 [48459.392092] DMAR:[fault reason 06] PTE Read access is not set I am running on HP ProLiant DL380p Gen8. Ubuntu 3.11.0-26-generic Is anyone encounter this kind of issue with Intel XL710 NICs (Fortville)? Thx Nissim -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov Sent: Thursday, March 19, 2015 7:58 PM To: dev@dpdk.org Subject: [dpdk-dev] Queries on DPDK working with XL710 intel NIC Hi all, I am trying to work with intel XL710 40GIG NIC but for some reason when try= ing to load it via dpdk I am getting the following error: EAL: PCI device 0000:21:00.1 on NUMA socket 1 EAL: probe driver: 8086:1583 rte_i40e_pmd EAL: PCI memory mapped at 0x7fff939f9000 EAL: PCI memory mapped at 0x7fffd54b8000 EAL: Error - exiting with code: 1 Cause: Requested device 0000:21:00.1 cannot be used It seems that the "problematic" functions is i40e_aq_get_firmware_version()= in the following line: status =3D i40e_asq_send_command(hw, &desc, NULL, 0, cmd_details); (gdb) p status $3 =3D I40E_ERR_ADMIN_QUEUE_TIMEOUT I did read in another mail thread (attached below) that this might be a fir= mware issue so i upgraded my NIC firmware version to latest but still not a= ble to get it work: root@lagavulin:~# ethtool -i eth24 driver: i40e version: 1.2.37 firmware-version: f4.33.31377 a1.2 n4.42 e1932 bus-info: 0000:21:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes any idea why I still see the issue? thanks! Nissim Hi Yan Please tell me what version of firmware are you using? If it is too old, pl= ease update to at least 4.2.6. If it is still there, check that if your firmware updating is really succes= sful. You can try to run linux kernel driver to have a double check. Regards, Helin From: Yan Freedland [mailto:YanF at Radware.com] Sent: Thursday, March 19, 2015 12:28 AM To: Zhang, Helin Cc: dev at dpdk.org Subject: [dpdk-dev] i40e_aq_get_firmware_version failure Hi, I am trying to start DPDK with 40G Intel NIC and get a failure at initializ= ation stage in i40e_aq_get_firmware_version(). For some reason this functio= n reaches TIMEOUT for more than maximum allowed times (10 times). In the no= te below I understand that several failures may be considerable but not as = many as I have. Should I enlarge the retries number ? Is it a HW issue ? Anyone who faced it or may assist please comment. Thanks, Yan