Re: [PATCH v2 2/2] Revert "ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585"

[Bjorn Helgaas]

On Sat, Sep 26, 2026 at 05:02:03PM +0200, Niklas Cassel wrote:
> On Fri, Sep 25, 2026 at 03:01:39PM -0500, Mario Limonciello wrote:
> > On 9/25/26 14:42, Bjorn Helgaas wrote:
> > > 
> > > What if I just merge patch [1/2] ("x86/PCI: Disable enhanced atomics
> > > on AMD NBIO 7.7 and 7.11") for v7.3?  Would that leave anything
> > > broken?
> > > 
> > > [1] https://lore.kernel.org/all/20260403050225.50186-1-artmoty@xxxxxxxxx/t/#u)
> > > [2] https://forum.radxa.com/t/repeated-ext4-metadata-corruption-on-raspberry-pi-5-with-penta-sata-hat-jmb585-despite-healthy-ssds-and-raid1/31393/10
> > > [3] https://forums.raspberrypi.com/viewtopic.php?p=2386959#p2386959
> > > 
> > > > Cc: Arthur Husband <artmoty@xxxxxxxxx>
> > > > Signed-off-by: Mario Limonciello <mario.limonciello@xxxxxxx>
> > 
> > I think we should let Niklas speak up here because there was confirmation on
> > this thread it's an AMD only issue.
> > 
> > https://lore.kernel.org/all/ap6RyP28fxXNjRWS@ryzen/
> 
> 1) The original reporter mentioned that he had never seen any issues on
>    Raspberry Pi, the commit message was AI generated.
> 
> 2) The problem "repeated-ext4-metadata-corruption" appears to be a problem
>    with NCQ on a specific drive. I asked that person for more tests, but
>    he did not to once turning off NCQ solved his problem.
> 
> 3) The quirk actually introduced a bunch of problems on Raspberry Pi,
>    because libata did not clear upper 64 bit addresses. This has since
>    been fixed in commit 82e47533221d ("ata: libahci: clear PxCLBU and
>    PxFBU for AHCI_HFLAG_32BIT_ONLY")
> 
> 4) People had been using this AHCI controller for years (including on
>    Raspberry Pi) without seeing any issues (until the quirk was
>    introduced).
> 
> 5) The people who were complaining about data corruption could be
>    identified to all use AMD systems.
> 
> 6) These people complained that it broke directly for any address > 32 bit.
>    For the JMicron (instead of ASMedia), it breaks for any address > 43 bit.
>    I have a hard time believing that the controller is so broken that the
>    set the 64-bit DMA addresses supported bit in the AHCI CAP register,
>    but does not support a single bit more than 32 bit.
> 
> 7) For all AHCI controllers with these quirks (except for an old ATI
>    one), we have gotten an errata from the manufacturer.
>    We have never seen any errata for this controller.
> 
> 
> All in all, I am 100% confident to revert the patch.
> But, I don't care if it goes into 7.3 or 7.4.
> 
> Just say the word and I can pick it up for 7.4 instead.

That all sounds good.  How about if I ask Linus to pull Mario's AMD
SMN fix for v7.3, since that seems to be PCI-related, and then you can
decide how/when to take the quirk revert, since that seems to be
ATA-related?

I'll ask Linus to pull the AMD SMN fix today, so you could still
revert the quirk for v7.3 also if you wanted.  It sounds like there
might be more details that could be included in the quirk revert,
e.g., the fact that the quirk caused issues on Raspberry Pi and the
fact that the problem the quirk address was fixed by commit X.