From: Christoph Hellwig <hch@lst.de>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Christoph Hellwig <hch@lst.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
iommu@lists.linux.dev, baolu.lu@linux.intel.com
Subject: Re: [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235
Date: Tue, 28 Mar 2023 03:22:31 +0200 [thread overview]
Message-ID: <20230328012231.GB21977@lst.de> (raw)
In-Reply-To: <a79ea7f5-6a41-a6c9-cfec-ba01aa2a3cfa@leemhuis.info>
I finally found some real time to look into this:
On Tue, Mar 21, 2023 at 02:52:00PM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> > The man errors I am getting are
> >
> > dmar_fault 8 callbacks suppressed
> > DMAR : DRHD: handling fault status req 2
> > DMAR : [DMA Write NO_PASID] Request device [07.00.1] fault addr
> > 0xfffe0000 [fault reason 0x82] Present bit in contect entry is clear
This clearly indicates that my original idea about the AMD gart was
completely bonkers, as we're obviously on an Intel platform.
And this indicates that the device is trying to do a DMA write to
something that isn't IOMMU mapped. Getting this from an initialization
change (commit 78013eaadf6 (x86: remove the IOMMU table infrastructure")
feels very strange to me.
Can you maybe post the full dmesg? I wonder if there is interesting
initialization error in here.
next prev parent reply other threads:[~2023-03-28 1:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 13:52 [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235 Linux regression tracking (Thorsten Leemhuis)
2023-03-22 9:46 ` Jason Adriaanse
2023-03-22 13:54 ` Christoph Hellwig
2023-03-28 1:22 ` Christoph Hellwig [this message]
2023-03-30 12:18 ` Robin Murphy
2023-03-31 2:20 ` Jason Adriaanse
2023-04-16 6:55 ` Christoph Hellwig
2023-04-22 6:25 ` Jason Adriaanse
2023-04-24 13:20 ` Robin Murphy
2023-04-24 13:44 ` Jason Adriaanse
2023-04-24 14:07 ` Robin Murphy
2023-04-25 4:17 ` Jason Adriaanse
2023-04-25 11:37 ` Robin Murphy
2023-04-25 13:58 ` Jason Adriaanse
2023-05-22 10:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:01 ` Robin Murphy
2023-05-22 11:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-02 13:07 ` Thorsten Leemhuis
2023-06-06 9:24 ` Christoph Hellwig
2023-06-06 10:26 ` Jason Adriaanse
2023-04-16 6:41 ` Christoph Hellwig
2023-04-17 11:21 ` Robin Murphy
2023-06-20 13:30 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20230328012231.GB21977@lst.de \
--to=hch@lst.de \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).