diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-16 16:59:00 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-16 16:59:33 +0000 |
| commit | 9aba81d8eb048db908c94a3c40c25a5fde0caee6 (patch) | |
| tree | b765e7fb5e9a3c2143c68b0414e0055adb70e785 /results/classifier/118/graphic/2807 | |
| parent | b89a938452613061c0f1f23e710281cf5c83cb29 (diff) | |
| download | qemu-analysis-9aba81d8eb048db908c94a3c40c25a5fde0caee6.tar.gz qemu-analysis-9aba81d8eb048db908c94a3c40c25a5fde0caee6.zip | |
add 18th iteration of classifier
Diffstat (limited to 'results/classifier/118/graphic/2807')
| -rw-r--r-- | results/classifier/118/graphic/2807 | 61 |
1 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/2807 b/results/classifier/118/graphic/2807 new file mode 100644 index 000000000..4e5057550 --- /dev/null +++ b/results/classifier/118/graphic/2807 @@ -0,0 +1,61 @@ +graphic: 0.895 +boot: 0.891 +ppc: 0.880 +device: 0.869 +performance: 0.851 +peripherals: 0.824 +vnc: 0.759 +architecture: 0.741 +user-level: 0.738 +debug: 0.662 +hypervisor: 0.630 +x86: 0.591 +semantic: 0.532 +i386: 0.477 +register: 0.470 +network: 0.467 +permissions: 0.465 +kernel: 0.464 +virtual: 0.456 +socket: 0.436 +assembly: 0.369 +PID: 0.342 +risc-v: 0.308 +TCG: 0.300 +arm: 0.296 +VMM: 0.249 +files: 0.239 +mistranslation: 0.221 +KVM: 0.150 + +DOUBLE MMU FAULT when running -M virt in qemu-system-m68k +Description of problem: +When running qemu-system-m68k with the -M virt machine type, a DOUBLE MMU FAULT occurs immediately upon startup, even without any BIOS, disk image, or additional configuration. +Steps to reproduce: +1. qemu-system-m68k -M virt -m 4M -serial stdio + +QEMU crashes immediately with the following output: +``` +qemu: fatal: DOUBLE MMU FAULT +D0 = 00000000 A0 = 00000000 F0 = 7fff ffffffffffffffff ( nan) +D1 = 00000000 A1 = 00000000 F1 = 7fff ffffffffffffffff ( nan) +D2 = 00000000 A2 = 00000000 F2 = 7fff ffffffffffffffff ( nan) +D3 = 00000000 A3 = 00000000 F3 = 7fff ffffffffffffffff ( nan) +D4 = 00000000 A4 = 00000000 F4 = 7fff ffffffffffffffff ( nan) +D5 = 00000000 A5 = 00000000 F5 = 7fff ffffffffffffffff ( nan) +D6 = 00000000 A6 = 00000000 F6 = 7fff ffffffffffffffff ( nan) +D7 = 00000000 A7 = 00000000 F7 = 7fff ffffffffffffffff ( nan) +PC = 00400000 SR = 2704 T:0 I:7 SI --Z-- +FPSR = 00000000 ---- + FPCR = 0000 X RN + A7(MSP) = 00000000 A7(USP) = 00000000 ->A7(ISP) = 00000000 +VBR = 0x00000000 +SFC = 0 DFC 0 +SSW 00000105 TCR 00000000 URP 00000000 SRP 00000000 +DTTR0/1: 00000000/00000000 ITTR0/1: 00000000/00000000 +MMUSR 00000000, fault at fffffffc +``` +Additional information: +The issue seems to be related to incorrect memory initialization, causing a fault at address fffffffc. +The PC = 00400000 suggests that QEMU is jumping to an invalid address early in the boot process. +The fact that the fault is consistent across different configurations (q800, next-cube, etc) points to a possible regression or incomplete memory initialization in the virt machine. |