From: Lu Baolu <baolu.lu@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org
Subject: Re: dmar pte read access not set error messages on hp dl388 gen8 systems
Date: Thu, 5 Dec 2019 09:39:13 +0800 [thread overview]
Message-ID: <2d4e0c05-f0ee-d4b1-d2ed-24197811b097@linux.intel.com> (raw)
In-Reply-To: <20191204205300.4jiexjqfpnqlcagu@cantor>
Hi,
On 12/5/19 4:53 AM, Jerry Snitselaar wrote:
> Attaching console output (can't get to a point to actually log in) and
> config that is used to build that kernel.
[...]
[ 21.969477] pci 0000:00:00.0: Adding to iommu group 0
[ 21.971390] pci 0000:00:01.0: Adding to iommu group 1
[ 21.973173] pci 0000:00:01.1: Adding to iommu group 2
[ 21.974930] pci 0000:00:02.0: Adding to iommu group 3
[ 21.976672] pci 0000:00:02.1: Adding to iommu group 4
[ 21.978446] pci 0000:00:02.2: Adding to iommu group 5
[ 21.980224] pci 0000:00:02.3: Adding to iommu group 6
[ 21.982096] pci 0000:00:03.0: Adding to iommu group 7
[ 21.983868] pci 0000:00:03.1: Adding to iommu group 8
[ 21.985644] pci 0000:00:03.2: Adding to iommu group 9
[ 21.987484] pci 0000:00:03.3: Adding to iommu group 10
[ 21.989830] pci 0000:00:04.0: Adding to iommu group 11
[ 21.991738] pci 0000:00:04.1: Adding to iommu group 11
[ 21.993557] pci 0000:00:04.2: Adding to iommu group 11
[ 21.995360] pci 0000:00:04.3: Adding to iommu group 11
[ 21.997145] pci 0000:00:04.4: Adding to iommu group 11
[ 21.998915] pci 0000:00:04.5: Adding to iommu group 11
[ 22.000694] pci 0000:00:04.6: Adding to iommu group 11
[ 22.002569] pci 0000:00:04.7: Adding to iommu group 11
[ 22.004556] pci 0000:00:05.0: Adding to iommu group 12
[ 22.006388] pci 0000:00:05.2: Adding to iommu group 12
[ 22.008186] pci 0000:00:05.4: Adding to iommu group 12
[ 22.009968] pci 0000:00:11.0: Adding to iommu group 13
[ 22.011815] pci 0000:00:1a.0: Adding to iommu group 14
[ 22.013605] pci 0000:00:1c.0: Adding to iommu group 15
[ 22.015408] pci 0000:00:1c.7: Adding to iommu group 16
[ 22.017216] pci 0000:00:1d.0: Adding to iommu group 17
[ 22.018991] pci 0000:00:1e.0: Adding to iommu group 18
[ 22.021826] pci 0000:00:1e.0: Using iommu dma mapping
[ 22.023783] pci 0000:00:1f.0: Adding to iommu group 19
[ 22.025667] pci 0000:00:1f.2: Adding to iommu group 19
[ 22.346001] pci 0000:03:00.0: Adding to iommu group 20
[ 22.348727] pci 0000:03:00.0: Using iommu dma mapping
[ 22.350644] pci 0000:03:00.1: Adding to iommu group 20
[ 22.352833] pci 0000:03:00.2: Adding to iommu group 20
[...]
It seems that iommu pci bus probe didn't enumerate device [01:00.2] and
[02:00.0], the corresponding context entries were not setup. Hence dma
fault generated when devices access the memory.
Do these two devices show in "lspci" output? How do these devices get
enumerated by the system?
Best regards,
baolu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-12-05 1:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 6:34 dmar pte read access not set error messages on hp dl388 gen8 systems Jerry Snitselaar
2019-12-02 6:41 ` Lu Baolu
2019-12-02 7:14 ` Jerry Snitselaar
2019-12-02 16:13 ` Jerry Snitselaar
2019-12-03 1:59 ` Lu Baolu
2019-12-03 9:56 ` Jerry Snitselaar
2019-12-04 0:17 ` Lu Baolu
2019-12-04 20:53 ` Jerry Snitselaar
2019-12-05 1:39 ` Lu Baolu [this message]
2019-12-05 2:25 ` Jerry Snitselaar
2019-12-05 2:44 ` Lu Baolu
2019-12-05 2:53 ` Jerry Snitselaar
2019-12-06 1:52 ` Lu Baolu
2019-12-06 7:24 ` Jerry Snitselaar
2019-12-07 1:53 ` Lu Baolu
2019-12-07 2:29 ` Jerry Snitselaar
2019-12-07 2:41 ` Jerry Snitselaar
2019-12-08 6:26 ` Lu Baolu
2019-12-10 0:52 ` Jerry Snitselaar
2019-12-10 1:29 ` Lu Baolu
2019-12-10 3:47 ` Jerry Snitselaar
2019-12-10 5:03 ` Lu Baolu
2019-12-10 5:18 ` Jerry Snitselaar
2019-12-10 5:43 ` Lu Baolu
2019-12-10 22:12 ` Jerry Snitselaar
2019-12-10 5:43 ` Jerry Snitselaar
2019-12-10 6:16 ` Jerry Snitselaar
2019-12-10 6:26 ` Lu Baolu
2019-12-10 7:44 ` Jerry Snitselaar
2019-12-08 6:04 ` Lu Baolu
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=2d4e0c05-f0ee-d4b1-d2ed-24197811b097@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jsnitsel@redhat.com \
/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).