Hi Manu,
A gdb backtrace. Thanks, Ali On 05.10.2012 10:34, Manu Awasthi wrote: > Ali Saidi <saidi <at> umich.edu> writes: > >> Hi Manu, I don't know why you're seeing that issue,but you'd need to provide a back > > trace to see which event is being scheduled that was already scheduled. FYI, > people normally boot with a simple CPU, take a checkpoint, and then restore from > that checkpoint. THis lest you get to the region of interest in the benchmark > much more quickly than booting the machine with e detailed cpu. > >> Ali > > Hi Ali, > Thanks for the quick reply. Is there a commandline argument that I can use to > capture the list of events being scheduled - or just a regular gdb backtrace? > > Thanks, > Manu > &nbs > >> and NPB) with >> >> the ARM ISA and am receiving assertion failures > px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"> my commandline ./build/ARM/m5.opt configs/example/fs.py --kernel=vmlinux-3.3- > > ar> ecjvm2008.rcS --cpu-type=detailed --caches -- l1d_size=32kB --l1d_assoc=2 --l1i_size=32kB --l1 > 2cache -- l2_size=4MB --l2_assoc=8 --clock=2.5GHz --maxinsts=2000000000 Assertion Failure :: m5.opt: build/ARM/sim/eventq.hh:485: void > > EventQueue::schedule(Event*, Tick): Assertion `!event->scheduled()' failed. Links: ------ [1] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
