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 9F81EA034C for ; Thu, 1 Sep 2022 17:22:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6EA4940C35; Thu, 1 Sep 2022 17:22:03 +0200 (CEST) Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) by mails.dpdk.org (Postfix) with ESMTP id 0329E40695 for ; Thu, 1 Sep 2022 17:22:02 +0200 (CEST) Received: by mail-pl1-f175.google.com with SMTP id f24so14635005plr.1 for ; Thu, 01 Sep 2022 08:22:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc; bh=WcIK7dNBBAeoMucLvCEPAJzzzYAKalW7PlVT39pJbUQ=; b=tiL9U5ug5jGoWKRw90dVavhJui8qsJOeDXHeSyDUVG+kZRqDxMNGVDMrw48VjGI/Xc 81646vAutlJ9z/CcBbzfAH9KvYuLFUTewS3sCzavRx8e9qp6gq1P1qoEI5wo5q+gEoRJ kg7t0xA0hCnwfo1men5wbabZODx2XO9W6sDqYv6G1Euv5MBCrURgg2srJ9upkvyyDA0j 5k0pSqfeWGjCQcjMvuXbhKd7IhhOgWmwzSf5l7SKPI19f9rUz8vjv9HkiMmXMOMuUbm0 hS8JbQRpJCpXmT+03RGCLq0mEnydVBPzmBtlFw7k9TQd05vC/UUgC2I4vnehqzfepDKW PPyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=WcIK7dNBBAeoMucLvCEPAJzzzYAKalW7PlVT39pJbUQ=; b=O5oH64a+mSStKADhAjN0w4sBSJRl8TYkKNczJWTNKUurH/DCpCbJpm3TIEr1Ky19El qhwhWtx9WxZy5ZVVeJcTC9N+YSZ+AukvPOGlBc86qVrCH8rOGqdkIU0qwmxZFfJeiorv Kx5zsn574rVI8TNE93K3en9RxLhvRiDU26RY7+rnS+GW81A9PJ2wehGqBM1d9GEU4MJn Ywfd64zIc+5SVJXhIW0ex511R/zonPUWzQZxOqKvARUb8bVJcXbtkKF2xhT0NvrxZjHF hFCPNKNUdnvgFE96rGT8Yz8tyQ8d5wAZ2H9nw0WQ1eROAJiAMRAiFBdsSyo6Sbyge6LD gTcQ== X-Gm-Message-State: ACgBeo2k4y9pxNpfBfGjvboMgE/6uUMFLc2UKMIyqb9UZAmWszThu/hm 45ot8HEmuti+OBq9g8RIG52vtcn5nfUmBg== X-Google-Smtp-Source: AA6agR7H0ZlTdTmzqQOOWdjR35eoS4qW/kZHh39dRENzTYZP8wD1cfd80BRu1qLImf/x5lt7UYgnLQ== X-Received: by 2002:a17:90a:2a8a:b0:1fd:bb56:ec53 with SMTP id j10-20020a17090a2a8a00b001fdbb56ec53mr9286207pjd.78.1662045721116; Thu, 01 Sep 2022 08:22:01 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id e8-20020a17090301c800b001729da53673sm14172178plh.14.2022.09.01.08.22.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Sep 2022 08:22:00 -0700 (PDT) Date: Thu, 1 Sep 2022 08:21:59 -0700 From: Stephen Hemminger To: Anna Tauzzi Cc: users@dpdk.org Subject: Re: Initializing and starting port on primary but transmitting on secondary I get port not ready Message-ID: <20220901082159.31573889@hermes.local> In-Reply-To: References: <20220831182546.228d64a3@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 Thu, 1 Sep 2022 09:33:54 +0200 Anna Tauzzi wrote: > I'm using the Mellanox Connect X5: > > pci@0000:3b:00.0 enp59s0f0np0 network MT27800 Family [ConnectX-5] > pci@0000:3b:00.1 enp59s0f1np1 network MT27800 Family [ConnectX-5] > pci@0000:3b:00.2 enp59s0f0v0 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:00.3 enp59s0f0v1 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:00.4 enp59s0f0v2 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:00.5 enp59s0f0v3 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:04.2 enp59s0f1v0 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:04.3 enp59s0f1v1 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:04.4 enp59s0f1v2 network MT27800 Family [ConnectX-5 > Virtual Function] > pci@0000:3b:04.5 enp59s0f1v3 network MT27800 Family [ConnectX-5 > Virtual Function] > > This is the message: > lcore 6 called tx_pkt_burst for not ready port 0 > 8: [/lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7ffff7c77a00]] > 7: [/lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7ffff7be5b43]] > 6: [/usr/local/lib/librte_eal.so.22(+0x1559a) [0x7ffff7d8e59a]] > 5: [build/simple_eth_tx_mp(+0x1a0c7) [0x55555556e0c7]] > 4: [build/simple_eth_tx_mp(+0x19f89) [0x55555556df89]] > 3: [build/simple_eth_tx_mp(+0x423c) [0x55555555823c]] > 2: [/usr/local/lib/librte_ethdev.so.22(+0x7cbc) [0x7ffff7eb3cbc]] > 1: [/usr/local/lib/librte_eal.so.22(rte_dump_stack+0x32) [0x7ffff7daf152]] > > I'm having all sorts of problems with this Mellanox stuff, Intel cards are > much more user friendly. > > Just to recap: > * configure on primary and transmit on primary ---> GOOD > > * configure on secondary and transmit on secondary ---> SIGSEGV > Thread 4 "lcore-worker-6" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7ffff4346640 (LWP 7208)] > rte_eth_tx_burst (port_id=0, queue_id=0, tx_pkts=0x7ffff4344ac0, nb_pkts=1) > at /usr/local/include/rte_ethdev.h:5650 > 5650 qd = p->txq.data[queue_id]; > (gdb) print p->txq > $2 = {data = 0x0, clbk = 0x7ffff7f21528 } (data is > NULL) > > > * configure on primary and transmit on secondary ---> PORT NOT READY > > Do you know who should be notified of this problem? Should I open a bug on > DPDK bugzilla or file it to NVIDIA? > > Thx. > > > > Il giorno gio 1 set 2022 alle ore 03:25 Stephen Hemminger < > stephen@networkplumber.org> ha scritto: > > > On Wed, 31 Aug 2022 22:59:56 +0200 > > Anna Tauzzi wrote: > > > > > I initialize a port with the following methods on a primary process: > > > > > > rte_dev_probe(vf) > > > > > > rte_eth_dev_configure(port_id, ... ); > > > > > > rte_eth_dev_adjust_nb_rx_tx_desc(port_id, ... ); > > > > > > rte_eth_rx_queue_setup(port_id, .... ); > > > > > > rte_eth_tx_queue_setup(port_id, ... ); > > > > > > rte_eth_dev_start(port_id ... ); > > > > > > > > > > > > Then I use the rte_eth_tx_burst(port_id) in the secondary process but I > > get > > > this message: > > > > > > called tx_pkt_burst for not ready port 0 > > > > > > Is this expected? > > > > No looks like a device driver bug. Which PMD? What version of rdma-core and kernel. There were some bugs in earlier versions around secondary process support. They were fixed, some users are using failsafe and mlx5 on Azure with secondary processes.