From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by dpdk.org (Postfix) with ESMTP id 381D4595E for ; Mon, 31 Mar 2014 20:14:42 +0200 (CEST) Received: by mail-qg0-f47.google.com with SMTP id 63so7672952qgz.6 for ; Mon, 31 Mar 2014 11:16:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=oHX5gJ1aCA064byy9stgwtYGlSX6dC41w8vMrLFEA2Y=; b=dUns6J5L9Dk/ONfw6wfosjR3dVKldJs1hxqU1tlLPDvBDMNuvCHCJLb6lF9fwJk+Ww YqMDXJ123lj+5Fe0Chz77Jv0ZYZa49MxDzMFAJzvKkXlzDaeU8cIGN4qCC3Z3QvI5VsE VTPhROpoSkuvfYue8fOEDnTaNSkOm04RZXzAkRY1QINPBTgqaYBLT1WOpSl3CAo3U/Et CBgI8vcsAv0AG238Nxp3fbPG7xj3M+/HE9d1kOu1QTAnAjSFYlpFfEYCEnQRG4kN2p3w SWCViTd6gxAD7E7+6toyPcy5A+nw7UaZi2Q0NpReiqoIYUhsUWjNatOQBKibfh8ykmCg 18bQ== MIME-Version: 1.0 X-Received: by 10.140.83.37 with SMTP id i34mr4126193qgd.100.1396289776618; Mon, 31 Mar 2014 11:16:16 -0700 (PDT) Sender: hyunseok.chang@gmail.com Received: by 10.140.19.136 with HTTP; Mon, 31 Mar 2014 11:16:16 -0700 (PDT) In-Reply-To: <4032A54B6BB5F04B8C08B6CFF08C59285540EDBB@FMSMSX103.amr.corp.intel.com> References: <4032A54B6BB5F04B8C08B6CFF08C59285540EDBB@FMSMSX103.amr.corp.intel.com> Date: Mon, 31 Mar 2014 14:16:16 -0400 X-Google-Sender-Auth: ppxwKeH9RPnZj9OxK8xFLW5hquY Message-ID: From: HS To: "Shaw, Jeffrey B" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] 82599ES NIC support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: hyunseok@ieee.org List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 18:14:42 -0000 > Can you check if your PCI device ID is listed in "lib/librte_eal/common/ include/rte_pci_dev_ids.h"? 82599ES is not listed in lib/librte_eal/common/ include/rte_pci_dev_ids.h On the other hand, 82599EB (which works okay with DPDK) is not listed there either. > Can you verify that you have bound your device to "igb_uio", perhaps using "tools/pci_unbind.py" (maybe renamed to tools/igb_uio_bind.py)? Yes: $ sudo pci_unbind.py --status Network devices using IGB_UIO driver ==================================== 0000:07:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused= > You might also try to edit the ".config" (in your build directory, NOT the Linux .config) to enable any of the "CONFIG_RTE_LIBRTE_IXGBE_ DEBUG_*" options, in case there are more error messages. I enabled debugging as you said, and run testpmd app. It ends with an error "Cause: No probed ethernet devices - check that CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file" Here is the detailed debug output: http://pastebin.com/tWkUZBKj Thanks, -hs On Mon, Mar 31, 2014 at 1:38 PM, Shaw, Jeffrey B wrote: > Can you check if your PCI device ID is listed in > "lib/librte_eal/common/include/rte_pci_dev_ids.h"? > Can you verify that you have bound your device to "igb_uio", perhaps using > "tools/pci_unbind.py" (maybe renamed to tools/igb_uio_bind.py)? > You might also try to edit the ".config" (in your build directory, NOT the > Linux .config) to enable any of the "CONFIG_RTE_LIBRTE_IXGBE_DEBUG_*" > options, in case there are more error messages. > > Thanks, > Jeff > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of HS > Sent: Monday, March 31, 2014 10:30 AM > To: dev@dpdk.org > Subject: [dpdk-dev] 82599ES NIC support > > Hi, > > I was trying to test DPDK 1.6 with "82599ES" Intel NIC, but noticed that > DPDK does not seem to work with this NIC. DPDK app fails because > rte_eth_dev_count() returns 0. > > On the other hand, I confirmed DPDK works okay with "82599EB". > > So looks like not all 82599 (ixgbe) chipsets are supported by DPDK while > it says so in http://dpdk.org/doc/nics > > What is the discrepancy between 82599ES and 82599EB, which causes the > former to fail to work with DPDK? > > Is it possible to fix this problem? I'll be glad to help fix it. > > Thanks, > -HS >