DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1574] bnxt dropping all packets when memory is low
Date: Wed, 06 Nov 2024 09:19:58 +0000	[thread overview]
Message-ID: <bug-1574-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1574
           Summary: bnxt dropping all packets when memory is low
           Product: DPDK
           Version: 23.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: fgiordano@riverbed.com
  Target Milestone: ---

Hello,

my DPDK application uses a BCM57412 NetXtreme-E 10Gb RDMA ethernet controller
(bnxt driver). When memory is low (and I reproduce it with a custom binary that
simply allocates memory and uses it) I get a bunch of errors like these in
/var/log/messages:

bnxt_rx_pkt(): mbuf alloc failed with prod=0x10aa

That's probably expected but what happens sometimes is that the NIC starts
dropping **all** incoming packets. Even if I then stop the memory-eating tool,
the application will drop 100% of incoming packets. The only thing to do at
that point is to restart the application.

I tested it with version 21.11.1, 23.11.1 and 23.11.2 and I could reproduce it
on all of them. Is this a known issue? Thanks.

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

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

                 reply	other threads:[~2024-11-06  9:20 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-1574-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).