Hi Gautam, I believe this is caused by a failing dice rolling on line memtest.cc:223. Replace:
> bool uncacheable = random_mt.random(0, 100) < percentUncacheable; with > bool uncacheable = random_mt.random(1, 100) <= percentUncacheable; I forgot to push that patch, my mistake. Explanation: DMAs should be emulated by MemTest by sending 100% *uncachable* accesses. The offending line causes the DMA MemTest to send a coherent access \~1% of the time although configured with percent_uncacheable == 100. These 1% accesses then target the same memory region as the coherent CPU (cache) accesses but it is handled as a DMA (non-coherent) access by Ruby. And there you get that error that merely tells you that an unexpected value was read by MemTest. Best, Gabriel
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
