DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1249] [dpdk-23.07] ixgbe port stop failed after launch testpmd
Date: Mon, 12 Jun 2023 07:29:30 +0000	[thread overview]
Message-ID: <bug-1249-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1249

            Bug ID: 1249
           Summary: [dpdk-23.07] ixgbe port stop failed after launch
                    testpmd
           Product: DPDK
           Version: 23.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: linglix.chen@intel.com
  Target Milestone: ---

Environment
OS: Ubuntu 22.04.2 LTS/5.15.0-71-generic
DPDK version: 8a2de735318b38ba93a041cb2f209889bde02689
Compiler: gcc version 11.3.0
NIC hardware: 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
NIC driver: ixgbe-5.18.11
NIC firmware: 0x000161bf

Test Setup

1. bind 1 port to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:b1:00.0

2. launch testpmd
 x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-2 -n 4 -- -i

3.testpmd>port stop 0
testpmd> show port info all

Show the output from the previous commands
testpmd>port stop 0
Stopping ports...
Checking link statuses...
ixgbe_dev_link_update_share(): Other link thread is running now!
Done
testpmd> show port info all
ixgbe_dev_wait_setup_link_complete(): IXGBE link thread not complete too long
time!
need kill to quit testpmd.

Expected Result
port stop normal.

Regression
Is this issue a regression: (Y/N)Y

Version the regression was introduced: Specify git id if known.
commit e90baf6b82f66c880c7e7f8f77fc534980165808
Author: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date:   Tue Jun 6 14:45:45 2023 -0700

    net/ixgbe: replace legacy atomics with GCC builtin atomics

    Replace the use of rte_atomic.h types and functions, instead use GCC
    supplied C++11 memory model builtins.

    Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
    Acked-by: Morten Brørup <mb@smartsharesystems.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 4072 bytes --]

             reply	other threads:[~2023-06-12  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  7:29 bugzilla [this message]
2023-06-12  7:43 ` David Marchand
2023-06-12 16:32   ` Tyler Retzlaff
2023-06-13  9:50     ` David Marchand
2023-06-14  6:57       ` Yang, Qiming
2023-06-14  7:13         ` David Marchand
2023-06-14  7:18           ` Morten Brørup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1249-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).