From d0c85e36e4de67af628d54e9ab577cc3fad7796a Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 07:27:52 +0000 Subject: add deepseek and gemma results --- results/classifier/gemma3:12b/kernel/1157 | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 results/classifier/gemma3:12b/kernel/1157 (limited to 'results/classifier/gemma3:12b/kernel/1157') diff --git a/results/classifier/gemma3:12b/kernel/1157 b/results/classifier/gemma3:12b/kernel/1157 new file mode 100644 index 00000000..b68d7d20 --- /dev/null +++ b/results/classifier/gemma3:12b/kernel/1157 @@ -0,0 +1,14 @@ + +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) -- cgit v1.2.3