On 2025/12/12 9:53, Jiaqi Yan wrote:
On Thu, Dec 11, 2025 at 5:02 AM Zenghui Yu yuzenghui@huawei.com wrote:
I can also hit this ASSERT with:
Random seed: 0x6b8b4567 # Mapped 0x40000 pages: gva=0x80000000 to gpa=0xff80000000 # Before EINJect: data=0xbaadcafe # EINJ_GVA=0x81234bad, einj_gpa=0xff81234bad, einj_hva=0xffff41234bad, einj_hpa=0x2841234bad # echo 0x10 > /sys/kernel/debug/apei/einj/error_type - done # echo 0x2 > /sys/kernel/debug/apei/einj/flags - done # echo 0x2841234bad > /sys/kernel/debug/apei/einj/param1 - done # echo 0xffffffffffffffff > /sys/kernel/debug/apei/einj/param2 - done # echo 0x1 > /sys/kernel/debug/apei/einj/notrigger - done # echo 0x1 > /sys/kernel/debug/apei/einj/error_inject - done # Memory UER EINJected # Dump kvm_run info about KVM_EXIT_MMIO # kvm_run.arm_sea: esr=0xffff90ba0040, flags=0x691000 # kvm_run.arm_sea: gva=0x100000008, gpa=0 ==== Test Assertion Failure ==== arm64/sea_to_user.c:207: exit_reason == (41) pid=38023 tid=38023 errno=4 - Interrupted system call 1 0x0000000000402d1b: run_vm at sea_to_user.c:207 2 0x0000000000402467: main at sea_to_user.c:330 3 0x0000ffff9122b03f: ?? ??:0 4 0x0000ffff9122b117: ?? ??:0 5 0x00000000004026ef: _start at ??:? Wanted KVM exit reason: 41 (ARM_SEA), got: 6 (MMIO)
Not sure what's wrong it..
Does your test machine have SDEI or SCI enabled for host APEI? Do you see any kernel log from "Memory failure:" saying hugetlb page recovered, and recovered significant earlier than the KVM exit here. It maybe the kernel has already unmapped hugepage in response to SDEI or SCI before this test actually consumes memory error, so no SEA is actually triggered.
No kernel log was printed when I saw this failure.
Thanks, Zenghui