Re: [Gems-users] LogTM: failed assertion 'isReady(request)'

[郭锐 <timmyguo@xxxxxxxxxxxxxxxx>]

This is a known issue. But the fix has not been released yet.
It's quit easy to fix it on your own. I have succeeded running radix kernel
on Ruby. Good luck!

Reason:
   a bug in SimicsProcessor.makeRequest that cause assertion failure
   when a transaction store hits but the corresponding log store misses.
   In such a situation, the processor will not stall, and flushes the
   active request for the log store. When the log store hits later, an
   assertion failure would arise.

> -----Original Message-----
> From: gems-users-bounces@xxxxxxxxxxx
[mailto:gems-users-bounces@xxxxxxxxxxx]
> On Behalf Of yoo@xxxxxxxxxxxxxx
> Sent: Tuesday, January 23, 2007 3:32 AM
> To: gems-users@xxxxxxxxxxx
> Subject: [Gems-users] LogTM: failed assertion 'isReady(request)'
> 
> Hi,
> 
> I've been trying to run SPLASH-2 benchmark suite on LogTM by changing
> coarse-grained locks into transactions.
> However, for most of the applications I get the following error:
> 
> failed assertion 'isReady(request)' at fn void
> Sequencer::makeRequest(const CacheMsg&) in system/Sequencer.C:487
> failed assertion 'isReady(request)' at fn void
> Sequencer::makeRequest(const CacheMsg&) in system/Sequencer.C:487
> At this point you might want to attach a debug to the running and get to
the
> crash site; otherwise press enter to continue
> 
> I know this issue has been discussed before, but was the fixed released?
> I'm using GEMS release 1.3.1. The above error occurred with both SIMICS
> 2.2.19 and 3.0.22.
> 
> Please let me know
> 
> 
> -Richard
> 
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding
> "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.