DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1653] PHY link up fails when rebinding i40e NICs to kernel driver
Date: Mon, 03 Feb 2025 04:29:20 +0000	[thread overview]
Message-ID: <bug-1653-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1653
           Summary: PHY link up fails when rebinding i40e NICs to kernel
                    driver
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

Some kernel drivers are not able to handle the link status correctly after DPDK
application sets the PHY to link down.

Implication:
The link status can’t be set to “up” after the NIC is rebound to the kernel
driver. Before a DPDK application quits it will invoke the function
i40e_dev_stop() which will sets the PHY to link down. Some kernel drivers may
not be able to handle the link status correctly after it retakes control of the
device. This is a known PHY link configuration issue in the i40e kernel driver.
The fix has been addressed in the 2.7.4 rc version. So if the i40e kernel
driver is < 2.7.4 and doesn’t have the fix backported it will encounter this
issue.

Resolution/Workaround:
First try to remove and reinsert the i40e kernel driver. If that fails reboot
the system.

Affected Environment/Platform:
All.

Driver/Module:
Poll Mode Driver (PMD).

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

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

                 reply	other threads:[~2025-02-03  4:29 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-1653-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).