DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1675] Shutting down the link on broadcom bnxt BCM57508 100GbE doesn't shutdown link on peer side
Date: Fri, 14 Mar 2025 00:58:36 +0000	[thread overview]
Message-ID: <bug-1675-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1675
           Summary: Shutting down the link on broadcom bnxt BCM57508
                    100GbE doesn't shutdown link on peer side
           Product: DPDK
           Version: 21.08
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: saurin.suthar@trellix.com
  Target Milestone: ---

We are using BCM57508 100GbE 2-port NIC AOC-A100G-B2CM
https://www.supermicro.com/en/products/accessories/addon/AOC-A100G-b2CM.php

Running alma linux 5.15.133 kernel with dpdk v21.08. Both 100G ports are
working normal and able to tx/rx. But when I bring the link down using
"ifconfig ethx down" the link status shows it is down. But on that interface,
packets are still coming, also peer side link is not going down. Is there a
patch available for this? If I bring the link down from peer side, link goes
down on my machine side.

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

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

                 reply	other threads:[~2025-03-14  0:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1675-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).