Hi, A fix for this issue has just been posted on the gem5 reviewboard : https://gem5-review.googlesource.com/c/public/gem5/+/18910. The fix simply removes the assertion. Please give it a try!
Cheers, - Gabor From: gem5-users <[email protected]> on behalf of Majid Jalili <[email protected]> Reply-To: Gem5 Users Mailing List <[email protected]> Date: Friday, 24 May 2019 at 00:21 To: Gem5 Users Mailing List <[email protected]> Subject: Re: [gem5-users] Error while running the latest version of gem5 fs mode/atomic cpu By reverting the commit "cpu,mem: Add support for partial loads/stores and wide mem. accesses" I solved the issue. But still not clear to me how it helped. On Monday, May 20, 2019, 1:28:31 PM CDT, Majid Jalili <[email protected]> wrote: Hi, I just cloned the latest version of gem5 and tried to run it in FS mode. However, if I set the cpu type to atomic I get the following error: gem5.opt: build/X86/cpu/simple/atomic.cc:544: virtual Fault AtomicSimpleCPU::writeMem(uint8_t*, unsigned int, Addr, Request::Flags, uint64_t*, const std::vector<bool>&): Assertion `locked && curr_frag_id == 0' failed. I do not see this error if I use other type of cpu. I think it is coming from one of the latest commit, because I did not have this problem 3 weeks ago. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
