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 53C0746254 for ; Tue, 18 Feb 2025 05:18:52 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C3B574014F; Tue, 18 Feb 2025 05:18:51 +0100 (CET) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mails.dpdk.org (Postfix) with ESMTP id 525F1400EF for ; Tue, 18 Feb 2025 05:18:50 +0100 (CET) Received: by mail-pj1-f43.google.com with SMTP id 98e67ed59e1d1-2fc0d44a876so7146349a91.3 for ; Mon, 17 Feb 2025 20:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739852329; x=1740457129; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=E18AfnPKasytnonU5oyEtRWuo/V9nZiU88PWZOtYuP0=; b=jUhEWR35jLCorjGc3LjwIgWFB8guFaN8Nw6x7sXeMzNN5juyZQe8pTb8IU05WyKN3O XJMmDiCBFupzxXLsnJ/5xg8dryasyF6WtEfUXSmWew8YX6C2jwdHUb5sL8rQrU8NQBVY AL6t+bHlF5f1wpzyixxXAyEgPWAnp/cXEK8rfM6WMiRJAPTpvkbe2bnmEX8mRppPDGZ+ qXJDzMASGh/cFgRI+832dZs6ne2WxK5qS7OwVKUjVq2FYSko12qEtevl5PdXIOtMWLDt 7JSeCa+IfzpIq6wRjZdXLKbns/TlsvDDU4Sjenhqm4uO8B8x5XknhCvfVdWzTpdPVrt5 c4Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739852329; x=1740457129; h=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=E18AfnPKasytnonU5oyEtRWuo/V9nZiU88PWZOtYuP0=; b=P0G4yXUAv+PtnVLjZkKQWz9GFFoCiT/z/M5yWNiQvlj8euog+CqJXev8V7Cair5b6i ILTxg+E77VGPJ+POFwbbI4x+542k3zuv+Q3NWyt4vOUtu059Q8sqom2QrDQiBuUiYShS QUr4XIWjXWPdSilRE8ORnR+nnEwLUjIqqelOw+gY4gFwdstmAHjSUe+gfMo91f5zsyJk M4N7Ow4e4vrDJtbO3NeMMIofOwmfzhM58xytdzlFlEAumGsxyNv+StZPNQbiOFChFVT4 wXhPRgoDu924ZhvfArntuycoT5UnUH3dNRWmmh2Nq3PRjCI00/5aAEb+nEKOSAF8eS2L sXMw== X-Gm-Message-State: AOJu0YxZ5fLDxq9BDjQnd72MRmPW97nmMrXnrB6OdNeGGm2UbfMlpC5Y esajU/3IewkAuyMAiT55emlGBOKfP9rd1DNpADFmp55WydiEap5/7B6XmnAcejjB0imL45WS2LX aZt3UnYyOwFw7Pfj17Oa5vykMH6NNfUP6 X-Gm-Gg: ASbGncvD7NnGPqNwVKclfHm/9oFe4uR5wiNnxE1/oVj3gas4isyFU3TZJlC9OzBoZB5 mBbku0nnL4ccyVUo/sHGvzoAIWtx8mK8a7is+ktydrmQhLSrNlKB6RqjnJY4zbGs/+TPqv6PZGW tKx2sFnWdanM/FMPn2zOYaySfs2DXdNUM= X-Google-Smtp-Source: AGHT+IEPGvRwUAGTlgRBc5OT2xEqUjn9nQJFwpZmI03L/kuKmsLEkC/r88vZjHUJRY1MRNMTNMevbf27OK1masUQMxA= X-Received: by 2002:a17:90b:3c0d:b0:2ea:356f:51b4 with SMTP id 98e67ed59e1d1-2fc40f10ac6mr19672866a91.13.1739852329244; Mon, 17 Feb 2025 20:18:49 -0800 (PST) MIME-Version: 1.0 References: <20250217075819.5d9af8df@hermes.local> In-Reply-To: <20250217075819.5d9af8df@hermes.local> From: Lokesh Chakka Date: Tue, 18 Feb 2025 09:48:37 +0530 X-Gm-Features: AWEUYZnNAPTKx6oFjEv9yzvFo5IdDnKhjP3SbO3SzLUo12RvzqYmd0F1lcQ2XdY Message-ID: Subject: Re: rte_eth_dev_stop crashing consistently To: Stephen Hemminger Cc: users Content-Type: multipart/alternative; boundary="0000000000000be1c1062e62f06a" 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 --0000000000000be1c1062e62f06a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, I've done the build with "meson setup build --buildtype=3Ddebug". I'm seeing a lot function names if I do "file build/lib/librte_eal.so" version I'm working on is dpdk-stable-24.11.1 Inside, the code I've set rte_log_set_global_level(RTE_LOG_DEBUG); while compiling the code, I've included "-lrte_eal -lrte_log -lrte_mbuf -lrte_ethdev -lrte_me mpool -mssse3" libraries. Still I'm seeing only generic EAL Logs. while executing, I'am using the command "sudo pmd_tx_rx -l 0-3 -n 4 --log-level=3D8" still I'am always seeing only the following lines : =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=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D EAL: Detected CPU lcores: 16 EAL: Detected NUMA nodes: 1 EAL: Detected shared linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized EAL: Using IOMMU type 1 (Type 1) ICE_INIT: ice_load_pkg_type(): Active package is: 1.3.39.1, ICE OS Default Package (single VLAN mode) ICE_INIT: ice_load_pkg_type(): Active package is: 1.3.39.1, ICE OS Default Package (single VLAN mode) tx_all_threads_function 188 pkt size: 1500 ICE_DRIVER: ice_set_rx_function(): Using AVX2 Vector Rx (port 0). =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=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D could you please let me know if any more debug flags to be provided.... Thanks & Regards -- Lokesh Chakka. On Mon, Feb 17, 2025 at 9:28=E2=80=AFPM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Mon, 17 Feb 2025 18:36:07 +0530 > Lokesh Chakka wrote: > > > Hello, > > > > I've written a few pieces of code for sending and receiving packets. > > Here is the link for the same. > > > > If I try running only pmd_tx.c or only pmd_rx.c, I'm not seeing any > crashes. > > But if the same code is copied into dpdk_tx_rx.c, I'm seeing a consiste= nt > > crash. > > > > Can someone help me understand what I'm doing wrong? > > > > > > Thanks & Regards > > -- > > Lokesh Chakka. > > This is all your own code, so it is up to you to debug it. > Did you try running in debugger (gdb) and/or enabling some of the debug > flags in the DPDK build. The debug flags will cause more of the code path= s > to validate arguments. > --0000000000000be1c1062e62f06a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hi,

I've done the build = with "meson setup build --buildtype=3Ddebug".
I= 9;m seeing a lot function names if I do "file build/lib/librte_eal.so&= quot;
version I'm working on is dpdk-stable-24.11.1

Inside, the code I've set rte_log_set_global_level(RTE_= LOG_DEBUG);
while compiling the code, I've included "-lr= te_eal -lrte_log -lrte_mbuf -lrte_ethdev -lrte_me =C2=A0 =C2=A0mpool -mssse= 3" libraries.
Still I'm seeing only generic EAL Logs.

while executing, I'am using the command &qu= ot;sudo pmd_tx_rx -l 0-3 -n 4 --log-level=3D8"

still I'am always seeing only the following lines :

=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=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
EAL: Detected CPU lcores: 16EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EA= L: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA m= ode 'VA'
EAL: VFIO support initialized
EAL: Using IOMMU type = 1 (Type 1)
ICE_INIT: ice_load_pkg_type(): Active package is: 1.3.39.1, I= CE OS Default Package (single VLAN mode)
ICE_INIT: ice_load_pkg_type(): = Active package is: 1.3.39.1, ICE OS Default Package (single VLAN mode)
t= x_all_threads_function 188 pkt size: 1500
ICE_DRIVER: ice_set_rx_functio= n(): Using AVX2 Vector Rx (port 0).
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

could you please let me know if any more debug flags= to be provided....


Than= ks & Regards
--
Lokesh Chakka.


On Mon, Feb 17, 20= 25 at 9:28=E2=80=AFPM Stephen Hemminger <stephen@networkplumber.org> wrote:
On Mon, 17 Feb 2025 18:36:07 +0530=
Lokesh Chakka <lvenkatakumarchakka@gmail.com> wrote:

> Hello,
>
> I've written a few pieces of code for sending and receiving packet= s.
> Here is the link for the same.
>
> If I try running only pmd_tx.c or only pmd_rx.c, I'm not seeing an= y crashes.
> But if the same code is copied into dpdk_tx_rx.c, I'm seeing a con= sistent
> crash.
>
> Can someone help me understand what I'm doing wrong?
>
>
> Thanks & Regards
> --
> Lokesh Chakka.

This is all your own code, so it is up to you to debug it.
Did you try running in debugger (gdb) and/or enabling some of the debug
flags in the DPDK build. The debug flags will cause more of the code paths<= br> to validate arguments.
--0000000000000be1c1062e62f06a--