All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1940] [net/ice] E810 PF Passthrough: Intermittent Link Bring‑Up Failure After Reboot (DPDK 24.11.1)
Date: Wed, 29 Apr 2026 19:02:07 +0000	[thread overview]
Message-ID: <bug-1940-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1940

            Bug ID: 1940
           Summary: [net/ice] E810 PF Passthrough: Intermittent Link
                    Bring‑Up Failure After Reboot (DPDK 24.11.1)
           Product: DPDK
           Version: 24.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: gownivalla.susmitha@wipro.com
  Target Milestone: ---

Hello DPDK Community,

We are facing an intermittent physical link bring‑up failure with Intel E810 PF
passthrough to a VM using DPDK 24.11.1. The failure occurs after reboot.

NIC: Intel E810 (Dell OEM, dual‑port)
NVM: 4.20
Host ICE driver: 1.11.14
Guest ICE driver (base): 1.6.4
DPDK: 24.11.1
Mode: PF passthrough
Environment: Openstack

After a VM reboot, port availability is inconsistent; occasionally both ports
come up, but often only one or neither initializes.

We would appreciate input on:

1. Any known ICE PMD issues with E810 in PF passthrough scenarios.
3. Known firmware dependencies or minimum NVM levels required for stable PFPT
operation.
4. Any potential software-level workarounds to mitigate compatibility issues
without changing the underlying firmware/driver?
5. Any upstream discussions or patches related to E810 reset/timing issues?

Thanks in advance.

Regards,
Susmitha

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

                 reply	other threads:[~2026-04-29 19:02 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-1940-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.