Dear gem5 users, I’m doing SPEC CPU 2017 benchmarks within gem5 at the moment. I’m using the fs.py system configuration using a NonCachingSimpleCPU (and did also runs using the AtomicSimpleCPU) and DDR4 memory together with a disk image created using the gem5-resources for the SPEC CPU 2017 benchmarks (see https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/ <https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/> ) on X86 architecture. I did change the SPEC CPU 2017 version used from 1.1.0 to 1.1.8. I’m aware of a gem5art tutorial page about those benchmarks, which also lists a table of results in the end (see https://gem5art.readthedocs.io/en/v1.2.0/tutorials/spec2017-tutorial.html <https://gem5art.readthedocs.io/en/v1.2.0/tutorials/spec2017-tutorial.html> ). I’m aware the tutorial page does not relate to the gem5 release v22.1.0.0, but I got several benchmarks with different errors, either during the benchmark setup (input generator for 625.x264_s, hash mismatch on 657.xz_s), or during the benchmark running (killed process without any output on 600.perlbench_s). I did runs on those benchmarks using the AtomicSimpleCPU and caches configured, but they ended the same. All the benchmarks were using the "test” workload, eg. ./build/X86/gem5.opt --outdir=m5out_x264_dram_test ./configs/example/fs.py --cpu-clock 3GHz --kernel /path/to/x86-linux-kernel-4.19.83 --disk-image /path/to/spec-2017-image --script script_x264_dram_test.rcS --mem-size 4GB --cpu-type NonCachingSimpleCPU --mem-type DDR4_2400_8x8 Or ./build/X86/gem5.opt --outdir=m5out_x264_dram_test ./configs/example/fs.py --cpu-clock 3GHz --kernel /path/to/x86-linux-kernel-4.19.83 --disk-image /path/to/spec-2017-image --script script_x264_dram_test.rcS --mem-size 4GB --cpu-type AtomicSimpleCPU --caches --l1d_size=32kB --l1i_size=32kB --l2_size=256kB --mem-type DDR4_2400_8x8 with script_x264_dram_test.rcS containing: 625.x264_s test . Is there a current status of working SPEC CPU 2017 benchmarks, or is there some change needed to apply since the release of the gem5 resource? Thanks a lot! BR, Markus