All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1241] DPDK 18.11.5: i40e PMD fails to start X710 port when set mtu.
Date: Mon, 29 May 2023 10:47:39 +0000	[thread overview]
Message-ID: <bug-1241-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1241
           Summary: DPDK 18.11.5: i40e PMD fails to start X710 port when
                    set mtu.
           Product: DPDK
           Version: 18.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: 18309220061@163.com
  Target Milestone: ---

When i use the i40e PMD to set the mtu, as follows:
1.  rte_eth_dev_ stop
2.  rte_eth_dev_set_mtu
3.  rte_eth_dev_start
The 1 and 2 steps are normal, but step 3 fails.
Log as follows:

i40e_alloc_rx queue mbufs(): Failed to allocate mbuf for RX
i40e alloc_rx queue mbufs(): Failed to allocate mbuf for RX
i40e dev rx queue start(): Failed to allocate RX queue mbuf
i40e dev switch queues(): Failed to switch rx queues
i40e dev start): Failed to enable VsI
i40e dev rx queue start(): Failed to allocate Rx queue mbuf
i40e dev switch queues(): Failed to switch rx queues
i40e dev start(): Failed to enable VSI

I don't know why?Sometimes it's normal and sometimes it's not.Only X710 nics
has the issue.

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

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

                 reply	other threads:[~2023-05-29 10:47 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-1241-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.