diff options
Diffstat (limited to 'results/classifier/zero-shot/118/kernel/2794')
| -rw-r--r-- | results/classifier/zero-shot/118/kernel/2794 | 79 |
1 files changed, 79 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/2794 b/results/classifier/zero-shot/118/kernel/2794 new file mode 100644 index 000000000..b2e7cf12f --- /dev/null +++ b/results/classifier/zero-shot/118/kernel/2794 @@ -0,0 +1,79 @@ +kernel: 0.943 +device: 0.881 +architecture: 0.837 +graphic: 0.825 +boot: 0.797 +ppc: 0.707 +PID: 0.654 +performance: 0.596 +permissions: 0.567 +debug: 0.540 +register: 0.448 +vnc: 0.430 +user-level: 0.416 +semantic: 0.399 +VMM: 0.379 +virtual: 0.354 +risc-v: 0.349 +x86: 0.335 +network: 0.280 +files: 0.243 +peripherals: 0.242 +assembly: 0.228 +mistranslation: 0.219 +socket: 0.202 +TCG: 0.195 +arm: 0.143 +i386: 0.116 +hypervisor: 0.100 +KVM: 0.067 + +qemu-system-m68k virt machine doesn't boot Linux kernels using 68020, 68030 and 68060 CPUs +Description of problem: +QEMU doesn't seem to be able to start Linux kernels using a CPU other than a 68040 (which does work fine) + +To rule out host issues, the issue is reproductible on Debian Unstable amd64 (with version QEMU emulator version 9.2.0)(Debian 1:9.2.0+ds-5)) + +To rule out cross-compilation issues, the kernel has been rebuild inside a virt machine (using a 68040 CPU), running Debian Unstable + +Each CPU model below gets stuck early before kernel boot during the ABCGHIJK thing. The Kernel doesn't seem to boot and QEMU process eat 100% of a CPU physical core + +**68020** +``` +qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux +ABCGH +``` + +**68030** +``` +qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux +ABC +``` + +**68060** +``` +qemu-system-m68k -M virt -cpu m68060 -m 1G -nographic -kernel /home/demik/tmp/vmlinux +ABC +``` +Steps to reproduce: +1. build a kernel with 68020/030/060 support (using virt_defconfig as base) +2. start QEMU with the command line above +Additional information: +68020 is understandable as it may need some sort of 68851 emulation. + +Relevant Kernel config Processor configuration: +``` +# +# Processor Type +# +CONFIG_M68KCLASSIC=y +# CONFIG_COLDFIRE is not set +CONFIG_M68020=y +CONFIG_M68030=y +CONFIG_M68040=y +CONFIG_M68060=y +``` + +This may be related to the following issues (but I don't have the skillset to confirm that) +- https://gitlab.com/qemu-project/qemu/-/issues/2091 +- https://gitlab.com/qemu-project/qemu/-/issues/2500 |