Gem5+Ramulator Error when running SPEC2006 benchmarks about ramulator

[Kozlowlw]

Having the same error with PARSEC benchmarking.
Clang 3.6.2
GCC 5.2.1
Swig 2.0.12
Running on Ubuntu 15.10

[Mappouras]

Sorry I did not give an earlier update. It seems that other memory modules (DramSim) have similar problems. You can go to the indicated file and change line 567 as follow:

if (privateFlags.isSet(VALID_CONTEXT_ID))
return _contextId;
else
return 0;

Of course that does not fix the problem, but it temporarily ignores the error.

[i7mist]

Hi all, sorry for the delay. I have figured the reason and a patch to fix this with be pushed soon.

[astromonk2013]

Hi i7mist, is there any update regarding the fix for this issue. Please let us know if there is a patch for this or what the fix is.Thanks

[astromonk2013]

i believe the contextid in gem5 is performed just for the statistics. The ramulator is using the contextId for the source of the request or the coreid.Somehow the coreid or the context id is getting corrupted.I think its set to garbage value when the source of the request does not originate in the cpu but the cache. This might happen during a writeback. What confuses me is any access to the ramulator is a write back and it should fail immediately on a WR but it does not.

[i7mist]

Hi astromonk2013, sorry for replying late. You are right about the source of corruption, it is happening during a writeback. I can fix this issue but I found there are still some other issues that make it corrupt when running some SPEC benchmarks. I didn't have time to fix that problem so I haven't pushed it to github. I'll try to get it done this week. Please stay tuned.

[astromonk2013]

Thanks, just an update I am trying to use the threadId to pass the cpuid/coreId to the ramulator.lets see if that works.I'll look forward to your updates.

[kvprathap]

Hello i7mist, I am at the latest commit(6ada583) and still get this error. I created a checkpoint with atomic cpu and restoring with '--mem-type=ramulator --ramulator-config=configs/LPDDR3-config.cfg --cpu-type=arm_detailed -r 1'.

gem5.opt: build/ARM/mem/request.hh:567: int Request::contextId() const: Assertion `privateFlags.isSet(VALID_CONTEXT_ID)' failed.

[afairouz84]

Hi all,

Anyone fixed this issue?

I'm having the same error:

gem5.opt: build/X86/mem/request.hh:567: int Request::contextId() const: Assertion `privateFlags.isSet(VALID_CONTEXT_ID)' failed.