From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by dpdk.org (Postfix) with ESMTP id DA7509179; Tue, 1 Aug 2017 11:55:56 +0200 (CEST) Received: by mail-it0-f49.google.com with SMTP id 77so5242159itj.1; Tue, 01 Aug 2017 02:55:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ANJc2Ve1orqJrvKd9bx+Tk4upOH7XxuC8GMmNZBBlaM=; b=Itssl5J7uFVB+1uogSytECXQ+NPjWT0poKD/mtLoVXGTTNzesZ1Y89SpmCXqQVtFOj Lxf4jAt3r6u7fsa36YPLFY9TO39ZU/DhcchfkkCaBfR/3/ch6/fWH1CKwazCbxm4VSQr 3USeGokNwsgEWh/Kh1km7G4EXybBZtuzYa0zIYgHjxjU/OfPimy4UWgFPjbhkN6jVqik IwIEbOQHcpgFHfSRr2TrUGXBqtb8MUT3UFD4J07qHn2/6OMYWmTEboKtV6f783bDcVnj tczomcIcm+xwwFHDhVOSrfGLAAJDoQQ3HEKhFIQREv1S0C2KYrd4brG3ju9enz53mc7B L55Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ANJc2Ve1orqJrvKd9bx+Tk4upOH7XxuC8GMmNZBBlaM=; b=SAZd1C5HCAypfXWpayG0cHBzTHQ8uAVN++T7mp6Uz3/05h/r/iKiyFBwz89LInaWSc pZ2rkms98Xkv161W6XGgN14nYm3mkub4eaTONoxrLtYsRI4NYTYjYMbAom1aV32/cBtm CmqC5QApQoD2aDNAyJ9dwvSO9gHuLosZVQm4yD+SpWe1LEySmYl7oUt6CArog/uX3aSa hZzo39SkBWh6/NF7MPjDOENAN/t0ii/njzRnyysrT+THSSQiqVTPYZwWIbVRyjp4usYh iQ9CwpicIQFQwblLzpTcorcqXFBg4PZa0rINS7jWvQRxsElFmlsOcxm9xV4k/zsfdhQu zKow== X-Gm-Message-State: AIVw111Oy9YD1C/+2czsUIu02YP8wJFWATEeikJ1EBWllHLT3wdGMCah gqwUScqg7JiuLEk4ieMvrzO7S+fnkTC8 X-Received: by 10.36.250.129 with SMTP id v123mr1158880ith.17.1501581356043; Tue, 01 Aug 2017 02:55:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.58.5 with HTTP; Tue, 1 Aug 2017 02:55:35 -0700 (PDT) In-Reply-To: References: From: Dumitru Ceara Date: Tue, 1 Aug 2017 11:55:35 +0200 Message-ID: To: dev@dpdk.org Cc: "Wu, Jingjing" , "Xing, Beilei" , users@dpdk.org Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-users] DPDK16.11.2 LTS: i40e PMD fails to start X710 port 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, 01 Aug 2017 09:55:57 -0000 Hi all, I'm reposting the following bug report on the dev mailing list. I was wondering if this is a known issue or not. In our application code, the only way to overcome the problem is to introduce a delay after each rte_eth_dev_stop/start call when using X710 cards. However, this seems like a hacky temporary fix as it increases the "start-up" time unnecessarily. Thanks, Dumitru On Wed, Jul 19, 2017 at 3:49 PM, Dumitru Ceara wrote: > Hi all, > > With DPDK 16.11.2 LTS we see "intermittent" errors when trying to > start an X710 interface (latest firmware - FW 5.05). > > Due to the fact that the i40e PMD requires the port to be stopped when > setting MTU we use the following sequence in our code: > 1. rte_eth_dev_ stop > 2. rte_eth_dev_set_mtu > 3. rte_eth_dev_start > > If rte_eth_dev_start is called shortly after stop (as is in our case), > the i40e_phy_conf_link sometimes fails and returns -ENOTSUP. This > happens because i40e_aq_get_phy_capabilities returns status > I40E_ERR_UNKNOWN_PHY. I double checked and the transceivers we use are > Intel FTLX8571D3BCV-IT. > > Moreover, if we introduce a delay (e.g., 10 seconds) after > rte_eth_dev_stop then rte_eth_dev_start works fine. > > In order to eliminate potential issues with our code I tried to > replicate with test-pmd with "disable-link-check" in order to avoid > the delay introduced by link state checking: > > # $RTE_SDK/tools/dpdk-devbind.py -s > > Network devices using DPDK-compatible driver > ============================================ > 0000:82:00.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused= > 0000:82:00.1 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused= > > # $RTE_SDK/x86_64-native-linuxapp-gcc/build/app/test-pmd/testpmd -w > 0000:82:00.0 -w 0000:82:00.1 -- --disable-link-check -i > EAL: Detected 32 lcore(s) > EAL: Probing VFIO support... > EAL: PCI device 0000:82:00.0 on NUMA socket 1 > EAL: probe driver: 8086:1572 net_i40e > PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.05 eetrack 8000289d > EAL: PCI device 0000:82:00.1 on NUMA socket 1 > EAL: probe driver: 8086:1572 net_i40e > PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.05 eetrack 8000289d > Interactive-mode selected > USER1: create a new mbuf pool : n=395456, > size=2176, socket=0 > Configuring Port 0 (socket 0) > Port 0: 3C:FD:FE:9C:79:F0 > Configuring Port 1 (socket 0) > Port 1: 3C:FD:FE:9C:79:F1 > Done > testpmd> port stop 1 > Stopping ports... > Done > testpmd> port start 1 > Port 1: 3C:FD:FE:9C:79:F1 > Done > testpmd> port stop 1 > Stopping ports... > Done > testpmd> port start 1 > Fail to start port 1 > Please stop the ports first <<<<<<< Here we fail to stop port 1 > Done > > I saw there were some more reports of similar I40E_ERR_UNKNOWN_PHY > issues but I'm not sure if they were related to the device stop/start > sequence. Is this a known limitation of the driver/firmware? Is the > application supposed to deal with this specific behavior of the X710? > If so, how would an application detect that the rte_eth_dev_stop > operation has completed? Or are we missing some hardware specific > initialization? > > Thanks, > Dumitru -- Dumitru Ceara