Re: [Gems-users] Fatal Error: Simics get unstalled without ruby

[Dan Gibson <degibson@xxxxxxxx>]

That error will arise if Ruby stalls a processor and never delivers a 
hit callback:
To stall a processor "indefinately," Ruby stalls it for a large number 
of cycles (I think 2,000,000, but it could be 2,000,000,000). 
Eventually, if Ruby fails to unstall a processor, the 2e6 cycles elapses 
and Simics resumes execution-- ergo "Simics get(s) unstalled without 
Ruby asking".
I have no idea how this might arise in the LogTM code...

Regards,
Dan

Mark Gebhart wrote:

> Hi,
>
> Sorry for a duplicate question but I originally asked in an unrelated thread
> and thought it would be better to break this out into a separate thread and
> I added some other thoughts.
>
> I am seeing the following error on a program with long running transactions:
>
> Fatal Error: in fn MemoryTransactionResult
> SimicsProcessor::makeRequest(memory_transaction_t*) in
> simics/SimicsProcessor.C:365: Error: Simics get unstalled without ruby
> asking?
>
> Has anyone seen this before / have any advice to avoid it?  This error
> message is thrown inside of SimicsProcessor::makeRequest, would it be safe
> to just throw a warning instead of an error?  Or is there some timeout value
> that I need to increase to prevent Simics from getting unstalled since I am
> dealing with long running transactions?
>
> Here are all of the messages I see:
>
> Warning: in fn void RegisterState::enableInterrupts(int) in
> log_tm/RegisterStateWindowed.C:336: "WARNING: in enable interrupts" is
> WARNING: in enable interrupts
> Warning: in fn void RegisterState::enableInterrupts(int) in
> log_tm/RegisterStateWindowed.C:336: "WARNING: in enable interrupts" is
> WARNING: in enable interrupts
> Warning: in fn void RegisterState::enableInterrupts(int) in
> log_tm/RegisterStateWindowed.C:337: pil is 0
> Warning: in fn void RegisterState::enableInterrupts(int) in
> log_tm/RegisterStateWindowed.C:337: pil is 0
> Fatal Error: in fn MemoryTransactionResult
> SimicsProcessor::makeRequest(memory_transaction_t*) in
> simics/SimicsProcessor.C:365: Error: Simics get unstalled without ruby
> asking?
> Fatal Error: in fn MemoryTransactionResult
> SimicsProcessor::makeRequest(memory_transaction_t*) in
> simics/SimicsProcessor.C:365: Error: Simics get unstalled without ruby
> asking?
>
>
> Thanks for any help anyone can provide,
>
> Mark
>
>
> _______________________________________________
> 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.
>
>
>