04-15-2026, 06:48 PM
The SError I also get on helios64 at times, with the same JMicron SATA to PCIe and rk3399. https://lkml.org/lkml/2023/5/15/1179 but
https://github.com/ARM-software/arm-trus...fb93654cb3 marvell/a3700: Prevent SError accessing PCIe link while it is down
https://github.com/ARM-software/arm-trus...419e9a1ec9 fix(plat/marvell/a3k): disable HANDLE_EA_EL3_FIRST by default "
It was enabled in commit 3c7dcda ("marvell/a3700: Prevent SError
accessing PCIe link while it is down") with a workaround for a bug found
in U-Boot and Linux kernel driver pci-aardvark.c (PCIe controller driver
for Armada 37xx SoC) which results in SError interrupt caused by AXI
SLVERR on external access (syndrome 0xbf000002) and immediate kernel
panic.
Now when proper patches are in both U-Boot and Linux kernel projects,
this workaround in TF-A should not have to be enabled by default
anymore as it has unwanted side effects like propagating all external
aborts, including non-fatal/correctable into EL3 and making them as
fatal which cause immediate abort.
Add documentation for HANDLE_EA_EL3_FIRST build option into Marvell
Armada build section.
Signed-off-by: Pali Rohár <pali@kernel.org>
Change-Id: Ic92b65bf9923505ab682830afb66c2f6cec70491
"
So it is supposed to be fixable without TF-A hacking, at least for Marvell A3700.
I also had random corruption, but it seems with voltage up for the big cpus things improve https://forum.armbian.com/topic/30074-he...ent-226166 (but I thought it was a helios64 board design issue).
https://github.com/ARM-software/arm-trus...fb93654cb3 marvell/a3700: Prevent SError accessing PCIe link while it is down
https://github.com/ARM-software/arm-trus...419e9a1ec9 fix(plat/marvell/a3k): disable HANDLE_EA_EL3_FIRST by default "
It was enabled in commit 3c7dcda ("marvell/a3700: Prevent SError
accessing PCIe link while it is down") with a workaround for a bug found
in U-Boot and Linux kernel driver pci-aardvark.c (PCIe controller driver
for Armada 37xx SoC) which results in SError interrupt caused by AXI
SLVERR on external access (syndrome 0xbf000002) and immediate kernel
panic.
Now when proper patches are in both U-Boot and Linux kernel projects,
this workaround in TF-A should not have to be enabled by default
anymore as it has unwanted side effects like propagating all external
aborts, including non-fatal/correctable into EL3 and making them as
fatal which cause immediate abort.
Add documentation for HANDLE_EA_EL3_FIRST build option into Marvell
Armada build section.
Signed-off-by: Pali Rohár <pali@kernel.org>
Change-Id: Ic92b65bf9923505ab682830afb66c2f6cec70491
"
So it is supposed to be fixable without TF-A hacking, at least for Marvell A3700.
I also had random corruption, but it seems with voltage up for the big cpus things improve https://forum.armbian.com/topic/30074-he...ent-226166 (but I thought it was a helios64 board design issue).

