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 E9D3F1B1C9 for ; Mon, 16 Apr 2018 08:35:39 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Apr 2018 23:35:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,458,1517904000"; d="scan'208";a="220700140" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga005.fm.intel.com with ESMTP; 15 Apr 2018 23:35:36 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.164]) by IRSMSX153.ger.corp.intel.com ([169.254.9.3]) with mapi id 14.03.0319.002; Mon, 16 Apr 2018 07:35:35 +0100 From: "Weglicki, MichalX" To: "Rosen, Rami" , "dev@dpdk.org" Thread-Topic: Problem with using VF: Initialization Failure: -15 Thread-Index: AdPRjMTVr6vLYvvXTN+HKRE6ljE6LwBZ9tawAJYGibA= Date: Mon, 16 Apr 2018 06:35:35 +0000 Message-ID: <1AFA2937E172CD4DB2FD9318443C060E40DBD4AC@IRSMSX102.ger.corp.intel.com> References: <1AFA2937E172CD4DB2FD9318443C060E40DB9C32@IRSMSX102.ger.corp.intel.com> <9B0331B6EBBD0E4684FBFAEDA55776F9531D579E@HASMSX110.ger.corp.intel.com> In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F9531D579E@HASMSX110.ger.corp.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-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzE2ODYxOWYtM2ZhMC00YmRkLTk3YjMtNGVkNjg2ZmQ2YmJjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkFqSFlGQ2lJbU5WczQyVWlGWDlnWXE5VnlGODZ1alpJK2U2am1Kd2dYclE9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Problem with using VF: Initialization Failure: -15 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2018 06:35:40 -0000 Hello,=20 Yes, sorry, the code flow I've presented was taken from investigation of vf= io_pci, but I'm not sure which hardware exactly (I've tested also some othe= r HWs). If it still doesn't make sense, maybe those are wrong assumptions.= =20 Should I resent this question to user@dpdk.org ? I don't want to cause conf= usion now when it's here already. Br, Michal.=20 > -----Original Message----- > From: Rosen, Rami > Sent: Friday, April 13, 2018 9:03 AM > To: Weglicki, MichalX ; dev@dpdk.org > Subject: RE: Problem with using VF: Initialization Failure: -15 >=20 > Hi, Michal, >=20 > First, I believe that such questions suit better to the dpdk-users mailin= g list. >=20 > >I've investigated the issue, and the problem is with: > >diag =3D hw->mac.ops.reset_hw(hw); > >which calls: > >e1000_reset_hw_vf > >and it calls: > >e1000_read_posted_mbx > >Which returns: E1000_ERR_MBX (-15) >=20 > Are you sure about it ? the path that you present in your investigation > is from drivers/net/e1000, whereas the test that you ran is on top of ixg= be, > which has a different PMD driver (drivers/net/ixgbe). The setup that you = describe does not use e1000 device at all, according to my > understanding. >=20 > Regards, > Rami Rosen >=20 >=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Weglicki, MichalX > Sent: Wednesday, April 11, 2018 15:01 > To: dev@dpdk.org > Subject: [dpdk-dev] Problem with using VF: Initialization Failure: -15 >=20 > Hello, >=20 > I'm trying to test very simple scenario, creating two VFs and testing it = with test-pmd. Unfortunately I can't make it to work DPDK > Version: v17.11 (I've checked also 18.02) > NIC: Niantic 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb > Kernel: 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x8= 6_64 x86_64 x86_64 GNU/Linux >=20 > Steps: > Creating two VFs. Binding each VF to a driver (I also tried vfio_pci with= same results): > ../dpdk/usertools/dpdk-devbind.py --bind=3Digb_uio 0000:81:10.0 ../dpdk/u= sertools/dpdk-devbind.py --bind=3Digb_uio 0000:81:10.1 >=20 > ./testpmd -c 0x3 -n 4 --socket-mem 512 -- --burst=3D64 -i --txqflags=3D0x= f00 --disable-hw-vlan > EAL: Detected 56 lcore(s) > EAL: Probing VFIO support... > EAL: VFIO support initialized > EAL: PCI device 0000:03:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:1521 net_e1000_igb > EAL: PCI device 0000:03:00.3 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:1521 net_e1000_igb > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:81:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:81:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:81:10.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10ed net_ixgbe_vf > PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15 > EAL: Requested device 0000:81:10.0 cannot be used > EAL: PCI device 0000:81:10.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10ed net_ixgbe_vf > PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15 > EAL: Requested device 0000:81:10.1 cannot be used > EAL: PCI device 0000:83:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:83:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: No probed ethernet devices > Interactive-mode selected >=20 > I've investigated the issue, and the problem is with: > diag =3D hw->mac.ops.reset_hw(hw); > which calls: > e1000_reset_hw_vf > and it calls: > e1000_read_posted_mbx > Which returns: E1000_ERR_MBX (-15) >=20 > Is this common issue, or some configuration problem? >=20 > Thank you all in advance. >=20 > Br, > Michal.