All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/testpmd Bug 1651] Linux kernel 4.10.0 iommu attribute read error
Date: Mon, 03 Feb 2025 04:26:00 +0000	[thread overview]
Message-ID: <bug-1651-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1651
           Summary: Linux kernel 4.10.0 iommu attribute read error
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

When VT-d is enabled (iommu=pt intel_iommu=on), reading IOMMU attributes from
/sys/devices/virtual/iommu/dmarXXX/intel-iommu/cap on Linux kernel 4.10.0
error. This bug is fixed in Linux commit a7fdb6e648fb, This bug is introduced
in Linux commit 39ab9555c241,

Implication:
When binding devices to VFIO and attempting to run testpmd application, testpmd
(and other DPDK applications) will not initialize.

Resolution/Workaround:
Use other linux kernel version. It only happens in linux kernel 4.10.0.

Affected Environment/Platform:
ALL OS of linux kernel 4.10.0.

Driver/Module:
vfio-pci module.

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

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

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  4:26 bugzilla [this message]
2025-02-07 11:21 ` [DPDK/testpmd Bug 1651] Linux kernel 4.10.0 iommu attribute read error 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-1651-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.