Sounds like another bisect needed to get a starting hold on this. Trying to further simplify the case ...
Turns out the test file and efi isn't needed which makes this simpler to test! It is already in the initialization of the system that breaks. To wrap it into something scriptable I utilize that it hangs in the good case with these arguments. # Good case $ timeout --preserve-status 15 qemu-system-riscv64 -no-user-config -nodefaults -m 256 -display 'none' -serial 'stdio' -machine 'virt' ... qemu-system-riscv64: terminating on signal 15 from pid 40953 (timeout) ubuntu@paelzer-qemu-break-edk2-test:~/edk2-2025.02$ echo $? 0 # Bad Case $ qemu-system-riscv64 -no-user-config -nodefaults -m 256 -display 'none' -serial 'stdio' -machine 'virt' ... ERROR:target/riscv/pmu.c:216:riscv_pmu_icount_update_priv: assertion failed: (newpriv <= PRV_S) Bail out! ERROR:target/riscv/pmu.c:216:riscv_pmu_icount_update_priv: assertion failed: (newpriv <= PRV_S) Aborted ubuntu@paelzer-qemu-break-edk2-test:~/edk2-2025.02$ echo $? 134 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2120835 Title: EDK2 tests for riscv emulation fail against qemu 10.1 (but only on ppc64 and armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2120835/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
