summary refs log tree commit diff stats
path: root/gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:07 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:17 +0200
commit9260319e7411ff8281700a532caa436f40120ec4 (patch)
tree2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml
parent225caa38269323af1bfc2daadff5ec8bd930747f (diff)
downloadqemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz
qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml')
-rw-r--r--gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml39
1 files changed, 0 insertions, 39 deletions
diff --git a/gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml b/gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml
deleted file mode 100644
index 39cca3987..000000000
--- a/gitlab/issues/target_m68k/host_missing/accel_missing/2807.toml
+++ /dev/null
@@ -1,39 +0,0 @@
-id = 2807
-title = "DOUBLE MMU FAULT when running -M virt in qemu-system-m68k"
-state = "closed"
-created_at = "2025-02-10T17:10:09.117Z"
-closed_at = "2025-02-10T18:34:05.422Z"
-labels = ["target: m68k", "workflow::Needs Info"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/2807"
-host-os = "Windows 11"
-host-arch = "x86_64"
-qemu-version = "QEMU emulator version 9.2.0 (v9.2.0-12071-g3dd0aeb44b)"
-guest-os = "None, I'm writing one."
-guest-arch = "m68k"
-description = """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."""
-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 = """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."""