From: Robin Murphy <robin.murphy@arm.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
iommu@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Re: iommu: flood of ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070]
Date: Mon, 3 Feb 2025 13:01:45 +0000 [thread overview]
Message-ID: <42a8ca6f-a881-4b4c-9ddb-bf3f2bc6f539@arm.com> (raw)
In-Reply-To: <Z6CGzUSV7llweytQ@Red>
On 2025-02-03 9:05 am, Corentin Labbe wrote:
> Hello
>
> I have a supermicro server which is flooded of kernel message:
> ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070]
>
> The server works perfectly anyway.
> It happens with official ubuntu kernel vmlinuz-6.8.0-51-generic.
> I tried also a custom 6.12.6, same problem.
>
> I tried to update bios, no change.
> I tried iommu=soft, no change.
>
> I dont know what to do next.
>
> Regards
>
> IOMMU group 83 e6:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] (rev 11)
Wow, a Marvell SATA controller doing something other than the usual
phantom function quirk, that's a nice change :D
I'd guess that firmware has left it running for something like legacy
IDE emulation (if that's still a thing?) or its own soft-RAID driver,
but neglected to declare an IVMD entry to described the reserved memory
region(s) it's using for that. A smoking gun would be if 0xa14a4000
matches some firmware-reserved PA in the system memory map. In that
case, if you're lucky you might have some firmware/BIOS option to
disable fancy behaviour and leave it in plain AHCI mode. Otherwise,
booting with "iommu.passthrough=1" (or the even bigger hammer of
"amd_iommu=off") should at least allow you to ignore the issue.
Thanks,
Robin.
next prev parent reply other threads:[~2025-02-03 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 9:05 Corentin Labbe
2025-02-03 13:01 ` Robin Murphy [this message]
2025-02-05 13:36 ` Corentin Labbe
2025-02-05 18:53 ` Robin Murphy
2025-02-05 12:03 ` Vasant Hegde
2025-02-05 13:41 ` Corentin Labbe
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=42a8ca6f-a881-4b4c-9ddb-bf3f2bc6f539@arm.com \
--to=robin.murphy@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®