> On Dec 7, 2020, at 9:57 AM, Damjan Marion <damjan.mar...@gmail.com> wrote: > > > Anything in dmesg output on PF side?
VF setup script running > [ 168.765633] i40e 0000:65:00.2: FW LLDP is enabled > [ 168.765635] i40e 0000:65:00.2: Allocating 1 VFs. > [ 168.870431] pci 0000:65:0a.0: [8086:154c] type 00 class 0x020000 > [ 168.870441] pci 0000:65:0a.0: enabling Extended Tags > [ 168.870609] pci 0000:65:0a.0: Adding to iommu group 101 > [ 168.881032] iavf: Intel(R) Ethernet Adaptive Virtual Function Network > Driver - version 3.2.3-k > [ 168.881033] Copyright (c) 2013 - 2018 Intel Corporation. > [ 168.881136] iavf 0000:65:0a.0: enabling device (0000 -> 0002) > [ 168.925644] iavf 0000:65:0a.0: Device is still in reset (-16), retrying > [ 168.971405] i40e 0000:65:00.2: Setting MAC 02:41:0b:0b:0b:0b on VF 0 > [ 169.061729] i40e 0000:65:00.2: Bring down and up the VF interface to make > this change effective. > [ 169.154400] i40e 0000:65:00.2: VF 0 is now trusted > [ 169.332527] i40e 0000:65:00.0: FW LLDP is enabled > [ 169.332528] i40e 0000:65:00.0: Allocating 1 VFs. > [ 169.438431] pci 0000:65:02.0: [8086:154c] type 00 class 0x020000 > [ 169.438441] pci 0000:65:02.0: enabling Extended Tags > [ 169.438588] pci 0000:65:02.0: Adding to iommu group 102 > [ 169.438668] iavf 0000:65:02.0: enabling device (0000 -> 0002) > [ 169.483272] iavf 0000:65:02.0: Device is still in reset (-16), retrying > [ 169.539244] i40e 0000:65:00.0: Setting MAC 02:41:0d:0d:0d:0b on VF 0 > [ 169.629728] i40e 0000:65:00.0: Bring down and up the VF interface to make > this change effective. > [ 169.722387] i40e 0000:65:00.0: VF 0 is now trusted > [ 169.902916] i40e 0000:65:00.3: FW LLDP is enabled > [ 169.902917] i40e 0000:65:00.3: Allocating 1 VFs. > [ 170.010432] pci 0000:65:0e.0: [8086:154c] type 00 class 0x020000 > [ 170.010441] pci 0000:65:0e.0: enabling Extended Tags > [ 170.010573] pci 0000:65:0e.0: Adding to iommu group 103 > [ 170.010641] iavf 0000:65:0e.0: enabling device (0000 -> 0002) > [ 170.055217] iavf 0000:65:0e.0: Device is still in reset (-16), retrying > [ 170.110941] i40e 0000:65:00.3: Setting MAC 02:42:0c:0c:0c:0c on VF 0 > [ 170.201737] i40e 0000:65:00.3: Bring down and up the VF interface to make > this change effective. > [ 170.294398] i40e 0000:65:00.3: VF 0 is now trusted VPP starts running > [ 178.922603] ixgbe 0000:17:00.0: complete > [ 178.928006] i40e 0000:65:00.0 enp101s0f0: NIC Link is Down > [ 179.186499] vfio-pci 0000:17:00.0: enabling device (0142 -> 0143) > [ 180.105670] i40e 0000:65:00.0 enp101s0f0: NIC Link is Up, 10 Gbps Full > Duplex, Flow Control: None > [ 180.247071] vfio-pci 0000:65:0a.0: enabling device (0000 -> 0002) > [ 180.841280] i40e 0000:65:00.2: VF 0 failed opcode 24, retval: -5 > [ 181.721005] vfio-pci 0000:65:0e.0: enabling device (0000 -> 0002) > [ 182.304338] i40e 0000:65:00.3: VF 0 failed opcode 24, retval: -5 > What kernel and driver version do you use? Host Config: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.10 DISTRIB_CODENAME=groovy DISTRIB_DESCRIPTION="Ubuntu 20.10" $ uname -a Linux labnh 5.8.0-31-generic #33-Ubuntu SMP Mon Nov 23 18:44:54 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Docker Config (compiled and run inside): root@p1:/# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS" > > Have you tried latest PF driver from intel? No; however, I am running such a new ubuntu (5.8 kernel) so I was hoping that was sufficient. Thanks, Chris. > > — > Damjan > >> On 07.12.2020., at 15:42, Christian Hopps <cho...@chopps.org> wrote: >> >> I'm hitting a problem with the native AVF driver. The issue does not seem to >> exist when using the DPDK driver. This is on stable/2009, with the DPDK bump >> to 2008 reverted (b/c 2008 doesn't work with mellanox anymore apparently). >> >> I have an x710 card configured with a 4x10G breakout cable. The code that is >> failing is >> >> if ((ad->feature_bitmap & VIRTCHNL_VF_OFFLOAD_RSS_PF) && >> (error = avf_op_config_rss_lut (vm, ad))) >> return error; >> >> Here's the debug log: >> >> 2020/12/07 14:19:25:639 debug avf 0000:65:0a.0: >> request_queues: num_queue_pairs 6 >> 2020/12/07 14:19:25:779 debug avf 0000:65:0a.0: version: >> major 1 minor 1 >> 2020/12/07 14:19:25:779 debug avf 0000:65:0a.0: >> get_vf_reqources: bitmap 0xb00a1 >> 2020/12/07 14:19:25:789 debug avf 0000:65:0a.0: >> get_vf_reqources: num_vsis 1 num_queue_pairs 6 max_vectors 5 max_mtu 0 >> vf_offload_flags 0xb000 rss_key_size 52 rss_lut_size 64 >> 2020/12/07 14:19:25:789 debug avf 0000:65:0a.0: >> get_vf_reqources_vsi[0]: vsi_id 18 num_queue_pairs 6 vsi_type 6 qset_handle >> 6 default_mac_addr 02:41:0b:0b:0b:0b >> 2020/12/07 14:19:25:789 debug avf 0000:65:0a.0: >> disable_vlan_stripping >> 2020/12/07 14:19:25:800 debug avf 0000:65:0a.0: >> config_rss_lut: vsi_id 18 rss_lut_size 64 lut >> 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 >> 2020/12/07 14:19:25:906 err avf 1313:13:13.0: error: >> avf_send_to_pf: error [v_opcode = 24, v_retval -5] >> >> If I comment out the 2 calls to VIRTCHNL_CF_OFFLOAD_RSS_PF, the device >> initializes. >> >> Is there something about the breakout cable configuration that needs special >> attention from this code? >> >> Thanks, >> Chris. >> >> >> >
signature.asc
Description: Message signed with OpenPGP
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18266): https://lists.fd.io/g/vpp-dev/message/18266 Mute This Topic: https://lists.fd.io/mt/78779141/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
