linux-kernel - Re: iommu: flood of ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <42a8ca6f-a881-4b4c-9ddb-bf3f2bc6f539@arm.com>
Date: Mon, 3 Feb 2025 13:01:45 +0000
From: Robin Murphy <robin.murphy@....com>
To: Corentin Labbe <clabbe.montjoie@...il.com>, joro@...tes.org,
 suravee.suthikulpanit@....com, will@...nel.org, iommu@...ts.linux.dev
Cc: linux-kernel@...r.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]

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.