From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org,
Todd Brandt <todd.e.brandt@linux.intel.com>
Subject: Re: [Bug 209321] DMAR: [DMA Read] Request device [03:00.0] PASID ffffffff fault addr fffd3000 [fault reason 06] PTE Read access is not set
Date: Thu, 8 Oct 2020 10:22:49 +0200 [thread overview]
Message-ID: <20201008082249.GA3107@8bytes.org> (raw)
In-Reply-To: <20201007154314.GA3245607@bjorn-Precision-5520>
Hi Bjorn,
On Wed, Oct 07, 2020 at 10:43:14AM -0500, Bjorn Helgaas wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=209321
>
> Not much detail in the bugzilla yet, but apparently this started in
> v5.8.0-rc1:
>
> DMAR: [DMA Read] Request device [03:00.0] PASID ffffffff fault addr fffd3000 [fault reason 06] PTE Read access is not set
>
> Currently assigned to Driver/PCI, but not clear to me yet whether PCI
> is the culprit or the victim.
Thanks for the heads-up, looks like Intel is already on it.
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org,
Todd Brandt <todd.e.brandt@linux.intel.com>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Bug 209321] DMAR: [DMA Read] Request device [03:00.0] PASID ffffffff fault addr fffd3000 [fault reason 06] PTE Read access is not set
Date: Thu, 8 Oct 2020 10:22:49 +0200 [thread overview]
Message-ID: <20201008082249.GA3107@8bytes.org> (raw)
In-Reply-To: <20201007154314.GA3245607@bjorn-Precision-5520>
Hi Bjorn,
On Wed, Oct 07, 2020 at 10:43:14AM -0500, Bjorn Helgaas wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=209321
>
> Not much detail in the bugzilla yet, but apparently this started in
> v5.8.0-rc1:
>
> DMAR: [DMA Read] Request device [03:00.0] PASID ffffffff fault addr fffd3000 [fault reason 06] PTE Read access is not set
>
> Currently assigned to Driver/PCI, but not clear to me yet whether PCI
> is the culprit or the victim.
Thanks for the heads-up, looks like Intel is already on it.
Regards,
Joerg
next prev parent reply other threads:[~2020-10-08 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 15:43 [Bug 209321] DMAR: [DMA Read] Request device [03:00.0] PASID ffffffff fault addr fffd3000 [fault reason 06] PTE Read access is not set Bjorn Helgaas
2020-10-07 15:43 ` Bjorn Helgaas
2020-10-08 8:22 ` Joerg Roedel [this message]
2020-10-08 8:22 ` Joerg Roedel
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=20201008082249.GA3107@8bytes.org \
--to=joro@8bytes.org \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=todd.e.brandt@linux.intel.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 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.