[gem5-users] Re: An error occurred in i8237 DMA controller when running CPU SPEC 2017 benchmarks

Hi Jinpeng, The error seems to cause by 'sysinfo', which is called by SPEC 2017 before it starts running a workload. SPEC 2017 documents how to turn it off here: https://www.spec.org/cpu2017/Docs/utility.html#sysinfo. Basically, the fix is to add this line: sysinfo_program = to the SPEC config

[gem5-users] Re: An error occurred in i8237 DMA controller when running CPU SPEC 2017 benchmarks

For the disk image, I think I did not follow the instruction exactly. Instead I created a disk image with ubuntu-18.04.2 and then I manually compiled and built CPU SPEC 2017. But I think there would not be any difference in the disk image. Thanks. Jinpeng > On Jul 17, 2020, at 12:25 PM, Jason

[gem5-users] Re: An error occurred in i8237 DMA controller when running CPU SPEC 2017 benchmarks

Hi Jason, Thanks for your prompt help. I exactly follow this instruction(https://gem5art.readthedocs.io/en/latest/tutorials/spec2017-tutorial.html ) to build kernel 4.19.83 and disk image ubuntu-18.04.2 and I am using

[gem5-users] Re: An error occurred in i8237 DMA controller when running CPU SPEC 2017 benchmarks

Hi Jinpeng, Thanks for pointing this out! I haven't personally seen this error before. We've been trying to test SPEC 2017 with gem5-20. Could you give more guest details (e.g., kernel, OS, benchmark, inputs) and simulator details (e.g., ISA, CPU model, memory system, cores, etc.) so we can try

[gem5-users] An error occurred in i8237 DMA controller when running CPU SPEC 2017 benchmarks

Hello all, I am trying to build and run CPU SPEC 2017 benchmarks in the FS mode, but the process terminated unexpectedly with an error happening in i8237 DMA controller. I did not change the source code. I do not quite understand what causes this bug and how to fix it. Any help would be really

[gem5-users] Adding new MessageSizeType in Coherence Protocol

Hi All, I am adding new MessageSizeType to src/mem/ruby/protocol/Ruby_Exports.sm file in MessageSizeType enumeration. During the execution of the gem5 binary, a panic error with message "Invalid range for type MessageSizeType " occurs at the start of execution. Kindly point out the correct way