Unfortunately this error message is pretty generic and can happen for a number of different reasons. Is this a clean copy of the simulator or do you have outstanding changes to the code?
Pretty much the only way to debug these things is to look at the logfile dump to try to see if you can piece together what happened. Usually it's something like a memory request never being returned to the pipeline (and so everything stalls waiting on the request) and hits the timeout interval. On Sun, Nov 25, 2012 at 4:36 PM, Ankita Garg <[email protected]> wrote: > Hi, > > I created some checkpoints for the SPEC benchmarks with 2 out-of-order > core configuration (machine - shared_l2). I used taskset two create two > instances of the spec benchmark. However, when I try to load the > checkpoint, the simulation aborts with the following error message: > > # qemu/qemu-system-x86_64 -m 4096M -drive cache=unsafe,file=natty.qcow2 > -snapshot -simconfig sim.cfg -loadvm mcf > > Completed 741000 cycles, 0 commits: 1748021 Hz, > 0 insns/sec: rip 0000000000400b2f ffffffff81013092[vcpu 0] thread 0: > WARNING: At cycle 1048577, 0 user commits: no instructions have committed > for 1048577 cycles; the pipeline could be deadlocked > qemu-system-x86_64: ptlsim/build/core/ooo-core/ooo.cpp:899: bool > ooo::OooCore::runcycle(void*): Assertion `0' failed. > Aborted > > The sim.cfg is just- > -machine shared_l2 > -stats stats.txt > -logfile test.log > -kill-after-run > > Any thoughts on what might be going wrong here ? Thanks for your help! > > -- > Regards, > Ankita > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
