diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1157')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1157 | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1157 b/results/classifier/zero-shot/108/other/1157 new file mode 100644 index 00000000..4e31a1c5 --- /dev/null +++ b/results/classifier/zero-shot/108/other/1157 @@ -0,0 +1,28 @@ +graphic: 0.879 +device: 0.812 +debug: 0.800 +semantic: 0.725 +permissions: 0.549 +performance: 0.518 +files: 0.493 +vnc: 0.492 +network: 0.465 +PID: 0.453 +socket: 0.434 +boot: 0.432 +KVM: 0.133 +other: 0.103 + +aarch64: enabling MMU causes instruction abort +Description of problem: +The title describes the problem pretty accurately, we get an instruction abort when enabling the MMU with a pretty simple set of page tables. This has been regressed from qemu 6.x. +Steps to reproduce: +1. Run the provided Kernel binary with the command line specified above. +2. Notice the hang after 'Initialize MMU'. I traced it down to being an instructions abort after the write to the SCTLR_EL1 register. +3. Try to run with qemu 6.x, and notice that it works. +Additional information: +This does work on actual hardware, so it has to be a qemu bug. + +A binary of the Serenity Kernel has been attached to the issue. The source of that binary can be found at commit ca0e32e59fcf67a662e5d3a994d44cd7c941624a of [SerenityOS](https://github.com/SerenityOS/serenity). + +[Kernel](/uploads/f731edbf81d8e575035e9693b0a51dbf/Kernel) |