From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 85D11A0588 for ; Thu, 16 Apr 2020 06:01:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BE4B51DA6C; Thu, 16 Apr 2020 06:01:20 +0200 (CEST) Received: from smtp1.kaist.ac.kr (smtp1.kaist.ac.kr [143.248.5.228]) by dpdk.org (Postfix) with ESMTP id CCBDC1DA62 for ; Thu, 16 Apr 2020 06:01:18 +0200 (CEST) Received: from unknown (HELO mail1.kaist.ac.kr) (143.248.5.69) by 143.248.5.228 with ESMTP; 16 Apr 2020 13:01:12 +0900 X-Original-SENDERIP: 143.248.5.69 X-Original-MAILFROM: sunghyuk.kay@kaist.ac.kr X-Original-RCPTTO: users@dpdk.org Received: from kaist.ac.kr (209.85.166.52) by kaist.ac.kr with ESMTP imoxion SensMail SmtpServer 7.0 id <2db4535d5c834282b7d259733a2afd41> for from ; Thu, 16 Apr 2020 13:01:13 +0900 Received: by mail-io1-f52.google.com with SMTP id f3so19659624ioj.1 for ; Wed, 15 Apr 2020 21:01:14 -0700 (PDT) X-Gm-Message-State: AGi0PuaV8yShteXukCtzNT+UwZibLCbkT1vU7dM2IVPIfi00M+UXaHJ5 OhD0nmE5DeIZBzSKd/djJQUQ7p/UMUmLqfPApefCQw== X-Google-Smtp-Source: APiQypIjhVTY5dvMshMyNDJ5iD/gQe4wJ1HcOA18aeoZfPFfuzjBhKrPjMoaZqSU173/CpHVmvDqb6JnqYzfEsbye5M= X-Received: by 2002:a02:9445:: with SMTP id a63mr28787433jai.10.1587009672829; Wed, 15 Apr 2020 21:01:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sunghyuk Kay Date: Thu, 16 Apr 2020 13:00:57 +0900 X-Gmail-Original-Message-ID: Message-ID: To: Dheeraj Dang Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] "eth_i40e_dev_init(): Failed to init adminq: -66" problem 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: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, sorry for the late reply. I had done more digging on the message, and I guess the issue was because of NIC's low firmware version. (I found IO_PAGE_FAULT on dmesg) Since I didn't want to screw up with the current environment (including firmware), I managed to run DPDK on other hardware with your advice on GRUB settings, so I might be able to see what my real problem was later in the future :) Thanks for the kind response. Regards, Sunghyuk On Fri, Apr 10, 2020 at 11:30 PM Dheeraj Dang wrote: > Hi, > > If you want to use igb_uio instead of vfio-pci, then you have to make the > following changes in the GRUB > GRUB_CMDLINE_LINUX=3D"iommu=3Dpt, intel_iommu=3Don" > > update grub settings and reboot the machine. > > When we are running DPDK on virtual functions, then it is recommended to > use vfio-pci instead of igb_uio. > You can refer this link > http://mails.dpdk.org/archives/dev/2014-August/004610.html for more > details. > > Regards > Dheeraj Dang > > > On Fri, Apr 10, 2020 at 7:01 PM Sunghyuk Kay > wrote: > >> Hi, >> Thanks for the solution. >> >> Actually, I was trying with igb_uio driver, rather than vfio-pci. >> Would that make a difference? >> >> Thank you, >> Sunghyuk >> >> 2020=EB=85=84 4=EC=9B=94 10=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 9:54= , Dheeraj Dang =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84= =B1: >> >>> Hi, >>> >>> I think you are using virtual functions while running your test. If yes= , >>> please try the following commands >>> >>> Make changes in GRUB setting, update grub and reboot the machine. >>> GRUB_CMDLINE_LINUX=3D"intel_iommu=3Don amd_iommu=3Don" >>> When machine is up, check that iommu is enabled in the output of cat >>> /proc/cmdline. If iommu is enabled, then run the following commands. >>> modprobe vfio enable_unsafe_noiommu_mode=3DY modprobe vfio-pci >>> >>> Bind your dpdk interfaces to vfio-pci (*dpdk-devbind.py -b vfio-pci >>> *) and run the test. >>> >>> Regards >>> Dheeraj Dang >>> >>> >>> On Fri, Apr 10, 2020 at 6:16 PM Sunghyuk Kay >>> wrote: >>> >>>> Hi all, >>>> I'm setting DPDK on our hardware to do some experiment, but suffering >>>> from . >>>> >>>> I was trying to use DPDK on Ubuntu 18.04 with Intel XL710 Ethernet >>>> Adapter >>>> with igb_uio driver. I've compiled DPDK from source, and bound the >>>> driver >>>> to NIC. >>>> But when I run `testpmd` application, it returns an error like this. >>>> >>>> ``` >>>> $ sudo ./build/app/testpmd >>>> EAL: Detected 128 lcore(s) >>>> EAL: Detected 1 NUMA nodes >>>> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket >>>> EAL: Selected IOVA mode 'PA' >>>> EAL: No available hugepages reported in hugepages-1048576kB >>>> EAL: Probing VFIO support... >>>> EAL: PCI device 0000:81:00.0 on NUMA socket 0 >>>> EAL: probe driver: 8086:1583 net_i40e >>>> eth_i40e_dev_init(): Failed to init adminq: -66 >>>> EAL: ethdev initialisation failedEAL: Requested device 0000:81:00.0 >>>> cannot >>>> be used >>>> EAL: PCI device 0000:81:00.1 on NUMA socket 0 >>>> EAL: probe driver: 8086:1583 net_i40e >>>> eth_i40e_dev_init(): Failed to init adminq: -66 >>>> EAL: ethdev initialisation failedEAL: Requested device 0000:81:00.1 >>>> cannot >>>> be used >>>> EAL: PCI device 0000:c4:00.0 on NUMA socket 0 >>>> EAL: probe driver: 8086:1533 net_e1000_igb >>>> EAL: PCI device 0000:c5:00.0 on NUMA socket 0 >>>> EAL: probe driver: 8086:1533 net_e1000_igb >>>> testpmd: No probed ethernet devices >>>> testpmd: create a new mbuf pool : n=3D1163456, >>>> size=3D2176, >>>> socket=3D0 >>>> testpmd: preferred mempool ops selected: ring_mp_mc >>>> Done >>>> No commandline core given, start packet forwarding >>>> io packet forwarding - ports=3D0 - cores=3D0 - streams=3D0 - NUMA supp= ort >>>> enabled, MP allocation mode: native >>>> >>>> io packet forwarding packets/burst=3D32 >>>> nb forwarding cores=3D1 - nb forwarding ports=3D0 >>>> Press enter to exit >>>> >>>> Telling cores to stop... >>>> Waiting for lcores to finish... >>>> >>>> +++++++++++++++ Accumulated forward statistics for all >>>> ports+++++++++++++++ >>>> RX-packets: 0 RX-dropped: 0 RX-total: 0 >>>> TX-packets: 0 TX-dropped: 0 TX-total: 0 >>>> >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++++++ >>>> >>>> Done. >>>> >>>> Bye... >>>> ``` >>>> I tried to find what return code -66 from adminq means, but I couldn't >>>> find >>>> it. >>>> Some say this might have to do with Intel IOMMU pass-through, but I'm >>>> not >>>> sure that's the case. >>>> >>>> Has anyone had this issue before? Maybe some tip on this issue would b= e >>>> very helpful. >>>> >>>> Thank you, >>>> Sunghyuk >>>> >>> -- >> =EA=B0=90=EC=82=AC=ED=95=A9=EB=8B=88=EB=8B=A4 >> =EA=B3=84=EC=84=B1=ED=98=81 =EB=93=9C=EB=A6=BC >> =3D=3D=3D=3D=3D=3D=3D=3D=3D >> =EA=B3=84=EC=84=B1=ED=98=81 (Kay, Sung Hyuk) >> KAIST Concurrency and Parallelism Laboratory >> Masters Student @ Software Graduate Program >> Mobile: 010-2794-6906 >> >