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 A31F6429AF for ; Fri, 21 Apr 2023 23:06:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1C58D410FB; Fri, 21 Apr 2023 23:06:14 +0200 (CEST) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by mails.dpdk.org (Postfix) with ESMTP id BB30A406B3 for ; Fri, 21 Apr 2023 23:06:12 +0200 (CEST) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-63b70ca0a84so3347094b3a.2 for ; Fri, 21 Apr 2023 14:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1682111172; x=1684703172; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=EkLOGCwLdAhXX3Y2l8Lw9cVDiQf/ctMQ+SgTdT8aoMw=; b=2i2a4wGt/DZBIy0pFYQuRjtL6g/KNwXxotXlscGdxwf82S2LkTIjULfv1yePgA8fjl 7xpp1oaODi5nZY5ed8/grM0Fcy4buY8CrokLvTa5Gp5huSyd/rSvEl1yDiH5s2nxAVhK kdNFSoSDq1faO14ltyeigcvJSJzG5QHbk521B4AAUQInzmrEOYUrAG3Nbku2hJ5Ty1hk d/JKPO0HYLY82x2hKMZFi/WQHCtPsonta7ranhksInD0gpL7IljFhGF/f2e6P/b97J5N LlfTopx7whEtnFjSnyKTH1cEFyWU3hazwxSRHnwYa/QtQunVwUex8ZkVZLAk6qOpxbCt jmrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682111172; x=1684703172; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=EkLOGCwLdAhXX3Y2l8Lw9cVDiQf/ctMQ+SgTdT8aoMw=; b=QziGJM+lHIABPQ8XH6NpurZvWiwXKdcpJ5l2TqzlAyas5ycMl4FoHE0yrzrZndv+4z fXN41qiedJyWkXYHq6yeJ2cfaBysgoE6i0l8yzCFc4hiqawFAE9cBbArfMegC7W7DVbr HHEa4rBgoWOxtX4rGA54BmB/1wtzmY2QdJmbancV776b/Pkc12+HXQ6bu/4BRoAK/Ni2 jSr9vI7Pwv6XWWx6PGgEYyeyytZIm/KScTLmI7FsqByXdHhBmR03rpZ9A3BFdsk47Go8 3ofgAokdr13tah1jddLvVx3ueEa7+/lfu6ljhwjOuyIViTdv+ECYsiTgNRuGj7Ul78UA T7Yw== X-Gm-Message-State: AAQBX9fE8gN+InGG2HY7qsuQKM4XKxk2BdGPi/CbilOTKFAWGq+FRSMn hfuvq6lP++UuEHuvdGHeCOkMEw== X-Google-Smtp-Source: AKy350bx+6+Z/JTyD1Rz8VRfH4cW4TkDPkCLkcgymojfC5A0UiGPJps0W/DqvYNad0d3JuRKkWuiQA== X-Received: by 2002:a05:6a20:4418:b0:f2:b6d6:e3fa with SMTP id ce24-20020a056a20441800b000f2b6d6e3famr2814515pzb.38.1682111171683; Fri, 21 Apr 2023 14:06:11 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id o9-20020a629a09000000b0062d90f36d16sm3373828pfe.88.2023.04.21.14.06.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 21 Apr 2023 14:06:11 -0700 (PDT) Date: Fri, 21 Apr 2023 14:06:08 -0700 From: Stephen Hemminger To: Igor de Paula Cc: users@dpdk.org Subject: Re: Issue with rte_eth_dev_start Message-ID: <20230421140608.35327af3@hermes.local> In-Reply-To: References: MIME-Version: 1.0 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 Fri, 21 Apr 2023 13:39:18 +0100 Igor de Paula wrote: > From what I can tell, dpdk calles the function vfio_disable_msix in the > stop and start function. The reason it does not happen in start up is that > I don't call stop before. > Calling stop and then start calls the function twice. Which maybe shouldn= 't > happen... Is it a bug? >=20 > On Thu, Apr 20, 2023 at 12:33=E2=80=AFPM Igor de Paula wrote: >=20 > > Hi, > > I am having trouble with restarting a HW port allocated to DPDK. > > I am running the DPDK version: 21.08.0 and Ubuntu 20.04.3 LTS. > > The driver is : net_e100igb > > After I start the port with no issues I try to call rte_eth_dev_stop to > > stop it. > > When I am ready I call rte_eth_dev_start to start it again an I get the > > following message: > > EAL: Error disabling MSI-X interrupts for fd 46. > > I am not sure what this error is coming from and what it causes. > > I found little information online. If someone could explain, I would > > really appreciate it. > > This is a copy print on setup with no issues: > > 2023-04-20 11:09:51.703542: Driver: net_e1000_igb > > 2023-04-20 11:09:51.703546: Bus Id: 0000:01:00.0 > > 2023-04-20 11:09:51.703551: rx offload cap: 280e (92e0f) > > 2023-04-20 11:09:51.703555: tx offload cap: 8002 (803f) > > 2023-04-20 11:09:51.703559: NUMA Socket: 0 > > 2023-04-20 11:09:51.703563: MAC Address: b4:96:91:63:62:40 > > 2023-04-20 11:09:51.703568: Max Rx Queue: 8 > > 2023-04-20 11:09:51.703572: Max Tx Queue: 8 > > 2023-04-20 11:09:51.703577: Max Rx Descriptors: 4096 > > 2023-04-20 11:09:51.703581: Max Tx Descriptors: 4096 > > 2023-04-20 11:09:51.703585: Max Rx Packet Length: 16383 > > 2023-04-20 11:09:51.703589: Available Link Speeds: 10Mb/s 100Mb/s 1= Gb/s > > 2023-04-20 11:09:51.703608: Fixed Link Speed: Auto > > 2023-04-20 11:09:51.703616: Fixed Duplex: Auto > > 2023-04-20 11:09:51.703623: MTU Set to: 16383 > > 2023-04-20 11:09:51.703632: Actual Rx Descriptors: 4096 > > 2023-04-20 11:09:51.703636: Actual Tx Descriptors: 4096 > > 2023-04-20 11:09:51.703695: Set up 1 send queues > > 2023-04-20 11:09:51.703700: Actual MTU: 16383 > > 2023-04-20 11:09:51.703704: Actual Linkspeed: 0 > > 2023-04-20 11:09:51.703708: Actual duplex: 0 > > 2023-04-20 11:09:51.703713: Successfully set port interrupt event > > 2023-04-20 11:09:51.818085: Flow control turned off for Port 0 > > 2023-04-20 11:09:51.844179: Port 0 up and running > > 2023-04-20 11:09:51.844303: Event type: LSC interrupt > > 2023-04-20 11:09:51.844382: Port 0 Link Down > > > > And after I stop and start: > > 2023-04-20 11:11:00.492428: Driver: net_e1000_igb > > 2023-04-20 11:11:00.492476: Bus Id: 0000:01:00.0 > > 2023-04-20 11:11:00.492526: rx offload cap: 280e (92e0f) > > 2023-04-20 11:11:00.492576: tx offload cap: 8002 (803f) > > 2023-04-20 11:11:00.492624: NUMA Socket: 0 > > 2023-04-20 11:11:00.492672: MAC Address: b4:96:91:63:62:40 > > 2023-04-20 11:11:00.492721: Max Rx Queue: 8 > > 2023-04-20 11:11:00.492770: Max Tx Queue: 8 > > 2023-04-20 11:11:00.492813: Max Rx Descriptors: 4096 > > 2023-04-20 11:11:00.492851: Max Tx Descriptors: 4096 > > 2023-04-20 11:11:00.492889: Max Rx Packet Length: 16383 > > 2023-04-20 11:11:00.492958: Available Link Speeds: 10Mb/s 100Mb/s 1= Gb/s > > 2023-04-20 11:11:00.493207: Fixed Link Speed: Auto > > 2023-04-20 11:11:00.493301: Fixed Duplex: Full > > 2023-04-20 11:11:00.493822: MTU Set to: 16383 > > 2023-04-20 11:11:00.493889: Actual Rx Descriptors: 4096 > > 2023-04-20 11:11:00.493936: Actual Tx Descriptors: 4096 > > 2023-04-20 11:11:00.494190: Actual MTU: 16383 > > 2023-04-20 11:11:00.494229: Actual Linkspeed: 0 > > 2023-04-20 11:11:00.494266: Actual duplex: 1 > > 2023-04-20 11:11:00.494305: Successfully set port interrupt event > > *EAL: Error disabling MSI-X interrupts for fd 46* > > 2023-04-20 11:11:00.603181: Flow control turned off for Port 0 > > 2023-04-20 11:11:00.629151: Port 0 up and running > > 2023-04-20 11:11:00.629222: Event type: LSC interrupt > > 2023-04-20 11:11:00.629273: Port 0 Link Down > > > > > > Thanks, > > Igor Are you using Link State (LSC) or receive interrupts? Did you start/stop the tx and rx queues. Could be a device bug where it assumes all queues were stopped. Also check kernel dmesg output; VFIO might print an error message there.