All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1649] igb_uio legacy mode can not be used in X710/XL710/XXV710
Date: Mon, 03 Feb 2025 04:06:39 +0000	[thread overview]
Message-ID: <bug-1649-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1649
           Summary: igb_uio legacy mode can not be used in
                    X710/XL710/XXV710
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

X710/XL710/XXV710 NICs lack support for indicating INTx is asserted via the
interrupt bit in the PCI status register. Linux deleted them from INTx support
table. The related commit.

Implication:
When insmod igb_uio with intr_mode=legacy and test link status interrupt. Since
INTx interrupt is not supported by X710/XL710/XXV710, it will cause
Input/Output error when reading file descriptor.

Resolution/Workaround:
Do not bind igb_uio with legacy mode in X710/XL710/XXV710 NICs, or do not use
kernel version >4.7 when you bind igb_uio with legacy mode.

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: 3099 bytes --]

             reply	other threads:[~2025-02-03  4:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  4:06 bugzilla [this message]
2025-02-12 18:43 ` [DPDK/other Bug 1649] igb_uio legacy mode can not be used in X710/XL710/XXV710 bugzilla

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-1649-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.