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 8DEBB455C5 for ; Mon, 8 Jul 2024 10:27:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4FFBB4028C; Mon, 8 Jul 2024 10:27:50 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id ACE174025E for ; Mon, 8 Jul 2024 10:27:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1720427268; 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=K6ALUmjUE1j4yJvRLTXQsa8DAsHHCI8Yihrrh9dNb9E=; b=gq17SIC868v165Oe/GGY5UBhg7mFlL4mY8Fkbiz61vbl/P1JX/sIa/tnTmJ+/5VBDXR9Bb oSiL8kcImyE5PBc3wCd+uwxu11VL55anPYMYdz5G6ETmBvUotmuKD6IlJzgQ24cX/zCuSW dQMTOB0lbNHSwjGhtP7DYf2lzUXzuPk= Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-118-C_Dp5tfTPXuOmnEtQ9retg-1; Mon, 08 Jul 2024 04:27:46 -0400 X-MC-Unique: C_Dp5tfTPXuOmnEtQ9retg-1 Received: by mail-lf1-f71.google.com with SMTP id 2adb3069b0e04-52eaef92c91so1322332e87.1 for ; Mon, 08 Jul 2024 01:27:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720427265; x=1721032065; 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=K6ALUmjUE1j4yJvRLTXQsa8DAsHHCI8Yihrrh9dNb9E=; b=w7MatiQuyD6BjARLbO01Cda6oGdLzrc81VfyloL8niZAis5mCZxFOiOldw7eby4GtN 5gGtf+QeIZjIvTyKVicixlHHdLlWZKAmn4W3ko3DvbM14hkcXFuEgO12kHuTlVmT26m/ D7Nh1+F0xewnc81APqQxWVRvw35sMZTj9/Za6/V1H9Xs/6qRw9CedeaYZLaIez2XuuTA iW+BN4S8P2aksKQtVE1h8JnMl0L9FD/h2uxlv7EKpnmNzSWslLTZwgmjOnmLPXm570Ox Wsb+u5Fc5w85F0Ov/5aW0NkiABEaqFyDHZOVYNdlVYeFY/isCMsUAqGRma5pfIXSaubL K0/A== X-Gm-Message-State: AOJu0Yzv53KSr41BF01P/hEwgF9dv8LnpkN3XFHKu8UEtgxyE8aZtZGm FBAm8qb9uVyepmHAmzXD9wDVEMJNw1nqrF7DLXY/yvxnY2jqrCm/kxNgsI5Z5wO3crPNgvgQ02H nkmKOCavLgFzzqf/PTjz8g8FJCs/7wbPg5utOQDkVbXjCOt4iEZ3wp8QENgaAorbfGOXdOl7dLx CsBjAgbjS7OhC23KyW2A== X-Received: by 2002:ac2:5e69:0:b0:52c:de00:9c04 with SMTP id 2adb3069b0e04-52ea06e4c8emr7397992e87.48.1720427265308; Mon, 08 Jul 2024 01:27:45 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGUoDfMA5g44JezZFgyORCA+CguWShaLcw7QyZdgRQLFWInpdlxbST6EhMXM/mOlWc/yDe1n1R3v9CFyLCMDOI= X-Received: by 2002:ac2:5e69:0:b0:52c:de00:9c04 with SMTP id 2adb3069b0e04-52ea06e4c8emr7397983e87.48.1720427264930; Mon, 08 Jul 2024 01:27:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Mon, 8 Jul 2024 10:27:33 +0200 Message-ID: Subject: Re: dpdk-dumpcap To: "Lombardo, Ed" Cc: "users@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: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Sun, Jul 7, 2024 at 10:59=E2=80=AFPM Lombardo, Ed wrote: > > Hi, > I am looking to debug my issue with dpdk and E810 NIC for transmit with G= RE header. The dpdk-dumpcap utility is my focus to see what dpdk is transm= itting. I have carefully studied the mbufs for the packet and looks correc= t. > I built dpdk-dumpcap utility with debug enabled in meson in dpdk.22.11 an= d copied dpdk-dumpcap to the VM running our application. > Our application is using the same version of dpdk 22.11 and built with st= atic libraries. Also rebuilt our application with the EAL argument of =E2= =80=9Cproc-type=3Dprimary=E2=80=9D. > When I run dpdk-dumpcap I get errors for RTE_FIB tailq. I don=E2=80=99t = understand this error, why tailq for RTE_FIB is not created in the dpdk-dum= pcap application. Do I need the RTE_FIB for packet capture, can I bypass t= he need for RTE_FIB? > > EAL: Cannot initialize tailq: RTE_FIB > Tailq 0: qname:, tqh_first:(nil), tqh_last:0x100000198 > Tailq 1: qname:, tqh_first:(nil), tqh_last:0x1000001c8 > Tailq 2: qname:, tqh_first:(nil), tqh_last:0x1000001f8 > Tailq 3: qname:, tqh_first:(nil), tqh_last:0x100000228 > Tailq 4: qname:, tqh_first:(nil), tqh_last:0x100000= 258 > Tailq 5: qname:, tqh_first:(nil), tqh_last:0x100000288 > Tailq 6: qname:, tqh_first:(nil), tqh_last:0x1000002b8 > Tailq 7: qname:, tqh_first:(nil), tqh_last:0x1000002e8 > Tailq 8: qname:, tqh_first:(nil), tqh_last:0x100000318 > Tailq 9: qname:, tqh_first:(nil), tqh_last:0x100000348 > Tailq 10: qname:, tqh_first:(nil), tqh_last:0x100000378 > Tailq 11: qname:, tqh_first:0x1bff3b580, tqh_last:0x1bff3b58= 0 > Tailq 12: qname:, tqh_first:0x1bff3b4c0, tqh_last:0x1bff41f40 > Tailq 13: qname:, tqh_first:0x1bff3b800, tqh_last:0x15= 04000c0 > Tailq 14: qname:, tqh_first:(nil), tqh_last:0x100000438 > Tailq 15: qname:, tqh_first:0x1bffd8dc0, tqh_last:0x1b= ff37dc0 > Tailq 16: qname:, tqh_first:(nil), tqh_last:0x1000004= 98 > Tailq 17: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 18: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 19: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 20: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 21: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 22: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 23: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 24: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 25: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 26: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 27: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 28: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 29: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 30: qname:<>, tqh_first:(nil), tqh_last:(nil) > Tailq 31: qname:<>, tqh_first:(nil), tqh_last:(nil) > EAL: FATAL: Cannot init tail queues for objects > EAL: Cannot init tail queues for objects > EAL: Error - exiting with code: 1 > Cause: EAL init failed: is primary process running? This means that the primary process binary (your application) does not have the FIB library builtin. Since v22.11, I see no fix in main that could explain this. Did you perhaps link your application manually? (I mean, not using pkg-conf= ig) --=20 David Marchand