From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 929CC42542; Fri, 8 Sep 2023 09:11:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3980B40274; Fri, 8 Sep 2023 09:11:17 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 4B9CC40042 for ; Fri, 8 Sep 2023 09:11:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1694157074; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1mMcYAtFP42g92m5ilALaGwXFl8qW1zBSUPM1qNBH4w=; b=Xeth2tEiHVQAHBG/uAWiy1xZdJax1z40sdP5ia8TBJAFmXYHNyCfxv3OkfMxF9dxtTvfdV G5412Fme2zPgiixPkEQQ3vtSP9VQjXRwa0WeJyXTJGiacav7RC0V71ZXKUtdKEbPs8dyIS MkWBXyKo9XHbTDudxB5DaU3SiWsvbP0= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-173-HDkczfsOMCicALqdPvgEqw-1; Fri, 08 Sep 2023 03:11:13 -0400 X-MC-Unique: HDkczfsOMCicALqdPvgEqw-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2b8405aace3so20003711fa.3 for ; Fri, 08 Sep 2023 00:11:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694157072; x=1694761872; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1mMcYAtFP42g92m5ilALaGwXFl8qW1zBSUPM1qNBH4w=; b=j+g0DACZ27u3bFWFapJmv8w9e77rUlzJ+UdThagXqF/xzk7RMzIY3VjDnF2L4UPzU+ Pt/+ifefjaIxk1xHuKIdXdcsRexud2wuUmGyCIDMPXr0wMeN5tuvgT3HnRgvNoKUrFGl CDa4dZ/qBqqbVFCQWhVJ08Sf1BWw+UDwkieGSwbt/+hrKa3Idm6jqDN5DuE5FtfIcpFa HMpBuqPkiX8xzvMf24/OudB6tNZ9o4K3l6kQB/whZLRNjycvMvb3GBnx6la2+EzVdeS6 AZj9CpQ1k9RFmRU7nL/+8CUL5DFDViLWf3MmOO/DFyoCZOn38sfckI386kdME/b1w1fX 6QIQ== X-Gm-Message-State: AOJu0YwjOkESFs1hn+cgt50UVxF/+fLERa1qR0vUt+Luhv4KKV73VRy+ Jg3Gvt9iHs6O/VrYZqw/LxNnDZHfWTyM/6jUeL7x08MzaTidaiIv3E287P/zJmBfSH516qureJ7 MPAMME8KFSF1tU0PIS5A= X-Received: by 2002:a2e:b247:0:b0:2bc:fdb9:5bf4 with SMTP id n7-20020a2eb247000000b002bcfdb95bf4mr965701ljm.11.1694157071730; Fri, 08 Sep 2023 00:11:11 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEfPNZh8KklZgNTl5IhMMS22EuhUSYh33pE9o9b2Exa0AJToNnnXCo0qTE17/yIO2zF81N7krwkPD03h7KUOs4= X-Received: by 2002:a2e:b247:0:b0:2bc:fdb9:5bf4 with SMTP id n7-20020a2eb247000000b002bcfdb95bf4mr965688ljm.11.1694157071324; Fri, 08 Sep 2023 00:11:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Fri, 8 Sep 2023 09:10:59 +0200 Message-ID: Subject: Re: Troubleshooting DPDK in Intel Ethernet NIC To: =?UTF-8?Q?Ant=C3=B3n_Rey_Villaverde?= Cc: dev@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello, On Fri, Sep 8, 2023 at 8:42=E2=80=AFAM Ant=C3=B3n Rey Villaverde wrote: > > Hi, > I have a problem while trying to manage my physical Ethernet interface fr= om DPDK (latest version compiled from source). > I have a: > NIC: 0000:00:1f.6 Ethernet controller: Intel Corporation Ethernet Connect= ion (13) I219-LM (rev 20) > > which belongs to the list of supported NICs in DPDK. > > Also, I have bound my NICto vfio-pci, not the kernel: > > dpdk-23.07$ usertools/dpdk-devbind.py --status > Network devices using DPDK-compatible driver =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 0000:00:1f.6 'Ethernet Connection (13) I219-= LM 15fb' drv=3Dvfio-pci unused=3De1000e > > I also enabled hugepages (2G). > > when I enter "sudo build/app/dpdk-testpmd -c7 -- -i" I get: > EAL: Detected CPU lcores: 8 > EAL: Detected NUMA nodes: 1 > EAL: Detected static linkage of DPDK > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > EAL: Selected IOVA mode 'VA' > EAL: VFIO support initialized > TELEMETRY: No legacy callbacks, legacy socket not created > testpmd: No probed ethernet devices > Interactive-mode selected > testpmd: create a new mbuf pool : n=3D163456, size=3D2176, soc= ket=3D0 > testpmd: preferred mempool ops selected: ring_mp_mc > Done > testpmd> > > When I enter "show port info all" in the testpmd CLI I get nothing (no po= rts). > > When I start testpmd with "-a 0000:00:1f.6" (the address of the ethernet = NIC I want to manage from DPDK), The same happens (no ports). Afaics, this nic is not supported by DPDK drivers. You will have to find some other nic, or run on another server with supported nics. Some details below. For a statically linked DPDK application (which is the default for testpmd), you can check with dpdk-pmd-info.py which PCI devices are supported. Example: $ ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | grep -i 15fb > > If I try to start testpmd with "-d build/drivers/librte_net_e1000.so" (th= e shared library of the driver of that device), I get a crash: > > dpdk-23.07$ sudo build/app/dpdk-testpmd -c7 -a 0000:00:1f.6 -d build/driv= ers/librte_net_e1000.so -- -i > EAL: Detected CPU lcores: 8 > EAL: Detected NUMA nodes: 1 > EAL: Detected static linkage of DPDK Your testpmd binary has been statically linked (as I said above, this is the default) and you can see the log message confirming it. > EAL: UIO_RESOURCE_LIST tailq is already registered PANIC in tailqinitfn_r= te_uio_tailq(): Cannot initialize tailq: UIO_RESOURCE_LIST > 0: build/app/dpdk-testpmd (rte_dump_stack+0x32) [55be1839afe2] > 1: build/app/dpdk-testpmd (__rte_panic+0xf1) [55be18369e68] > 2: /home/anton/tdr/dpdk-23.07/build/drivers/librte_bus_pci.so.23 (7f52153= f6000+0x5d86) [7f52153fbd86] > 3: /lib64/ld-linux-x86-64.so.2 (7f5215f90000+0x11b9a) [7f5215fa1b9a] > 4: /lib64/ld-linux-x86-64.so.2 (7f5215f90000+0x11ca1) [7f5215fa1ca1] > 5: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_exception+0xe5) [7f52159709= 85] > 6: /lib64/ld-linux-x86-64.so.2 (7f5215f90000+0x160cf) [7f5215fa60cf] > 7: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_exception+0x88) [7f52159709= 28] > 8: /lib64/ld-linux-x86-64.so.2 (7f5215f90000+0x1560a) [7f5215fa560a] > 9: /lib/x86_64-linux-gnu/libdl.so.2 (7f5215e15000+0x134c) [7f5215e1634c] > 10: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_exception+0x88) [7f5215970= 928] > 11: /lib/x86_64-linux-gnu/libc.so.6 (_dl_catch_error+0x33) [7f52159709f3] > 12: /lib/x86_64-linux-gnu/libdl.so.2 (7f5215e15000+0x1b59) [7f5215e16b59] > 13: /lib/x86_64-linux-gnu/libdl.so.2 (dlopen+0x4a) [7f5215e163da] > 14: build/app/dpdk-testpmd (55be17b79000+0x8013ee) [55be1837a3ee] > 15: build/app/dpdk-testpmd (eal_plugins_init+0x14f) [55be1837a6d8] > 16: build/app/dpdk-testpmd (rte_eal_init+0x1af) [55be1839ec21] > 17: build/app/dpdk-testpmd (main+0xde) [55be17da108b] > 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [7f521583408= 3] > 19: build/app/dpdk-testpmd (_start+0x2e) [55be17cef1fe] > Aborted This is not a crash, EAL willingly aborts because initialising UIO shared tailq has been requested twice and this is not something supported. This happened as you requested to load a driver that is embedded in the testpmd binary and has already been initialised. --=20 David Marchand