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


Date: Sun, 23 Apr 2006 19:45:31 -0500
From: Jake Adriaens <jtadriaens@xxxxxxxx>
Subject: [Gems-users] LogTM: failed assertion 'isReady(request)'
Hi,

I've been attempting to run a small transactional program, however when
I run it I often get the following error:
failed assertion 'isReady(request)' at fn void
Sequencer::makeRequest(const CacheMsg&) in system/Sequencer.C:487

It doesn't happen everytime the program is run, and the same program
works under the same setup using locks instead of begin and end
transaction. I am using simics 2.2.19 and start start it as follows:
gems/simics/home/MOESI_SMP_LogTM_directory/simics -stall

I run the following commands in simics:
read-configuration /home/ece757/checkpoints/sol9-2p.checkpoint
set-memory-limit 768
magic-break-enable
source /home/ece757/examples/hw5/scripts/simulate.py
c
instruction-fetch-mode instruction-fetch-trace
istc-disable
dstc-disable
load-module ruby
ruby0.setparam g_NUM_PROCESSORS 2
ruby0.setparam_str REMOVE_SINGLE_CYCLE_DCACHE_FAST_PATH true
ruby0.setparam_str PROFILE_XACT true
ruby0.setparam RETRY_LATENCY 100
ruby0.setparam g_MEMORY_SIZE_BYTES 8589934592
ruby0.setparam g_DEADLOCK_THRESHOLD 400000
ruby0.init
c
c
ruby0.dump-stats /home/ece757/examples/hw5/out/trans_array.2
exit

Here is a more detailed dump of the error starting with loading ruby:
Ruby Timing Mode
Warning: optimizations not enabled.
Creating event queue...
Creating event queue done
Creating system...
  Processors: 2
Creating system done
Ruby initialization complete
[/home/ece757/examples/hw5/scripts/simulate.simics:17] c
[cpu1] v:0x0000000000010e44 p:0x00000000df078e44  magic (sethi 0x40000, %g0)
[/home/ece757/examples/hw5/scripts/simulate.simics:18] c
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
PID: 22916

Thanks for the help,
Jake

[← Prev in Thread] Current Thread [Next in Thread→]