Both KVM and DerivO3CPU without restore were broken for me without checkpoints when I last tried them:
- https://github.com/gem5/gem5/issues/16 - https://www.mail-archive.com/gem5-users@gem5.org/msg15048.html On Thu, Apr 5, 2018 at 4:12 AM, Da Zhang <d...@vt.edu> wrote: > Hey guys, > > My gem5 real simulation crashed with > " > > gem5.opt: build_alter/build/X86/cpu/timebuf.hh:54: void > TimeBuffer<T>::valid(int) const [with T = DefaultIEWDefaultCommit<O3CPUImpl>]: > Assertion `idx >= -past && idx <= future' failed. > " > I am using DerivO3CPU and 32MB l2 cache 32GB mem and ramulator memory. > Restore a checkpoint who was token using KVM CPU. The workload was running > 8 instances of the same application with 2 threads each. > More backtrace > " > > 172928 --- BEGIN LIBC BACKTRACE --- > > 172929 build_alter/build/X86/gem5.opt(_Z15print_backtracev+0x15) > [0x1558a15] > > 172930 build_alter/build/X86/gem5.opt(_Z12abortHandleri+0x39)[0x156b039] > > 172931 /lib64/libpthread.so.0(+0xf100)[0x7f538bf88100] > > 172932 /lib64/libc.so.6(gsignal+0x37)[0x7f538a5405f7] > > 172933 /lib64/libc.so.6(abort+0x148)[0x7f538a541ce8] > > 172934 /lib64/libc.so.6(+0x2e566)[0x7f538a539566] > > 172935 /lib64/libc.so.6(+0x2e612)[0x7f538a539612] > > 172936 build_alter/build/X86/gem5.opt[0x906252] > > 172937 build_alter/build/X86/gem5.opt(_ZN10DefaultIEWI9O3CPUImplE12in > stToCommitER14RefCountingPtrI13BaseO3DynInstIS0_EE+0x1dd)[0x150c09d] > > 172938 build_alter/build/X86/gem5.opt(_ZN10DefaultIEWI9O3CPUImplE12ex > ecuteInstsEv+0x560)[0x150ef40] > > 172939 build_alter/build/X86/gem5.opt(_ZN10DefaultIEWI9O3CPUImplE4tic > kEv+0x11e)[0x1513a9e] > > 172940 build_alter/build/X86/gem5.opt(_ZN9FullO3CPUI9O3CPUImplE4tickE > v+0x12b)[0x14e5a8b] > > 172941 build_alter/build/X86/gem5.opt(_ZN10EventQueue10serviceOneEv+ > 0xc5)[0x155f265] > > 172942 build_alter/build/X86/gem5.opt(_Z9doSimLoopP10EventQueue+ > 0x40)[0x1576580] > > 172943 build_alter/build/X86/gem5.opt(_Z8simulatem+0xd4d)[0x157768d] > > 172944 build_alter/build/X86/gem5.opt[0xe9a07a] > > 172945 build_alter/build/X86/gem5.opt[0xb84bc7] > > 172946 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x50c2)[ > 0x7f538b88d5d2] > > 172947 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172948 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x425f)[ > 0x7f538b88c76f] > > 172949 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172950 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x425f)[ > 0x7f538b88c76f] > > 172951 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172952 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x425f)[ > 0x7f538b88c76f] > > 172953 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172954 /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f538b88e1c2] > > 172955 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x4f00)[ > 0x7f538b88d410] > > 172956 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172957 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x425f)[ > 0x7f538b88c76f] > > 172958 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x7f538b88e0bd] > > 172959 /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x7f538b88e1c2] > > 172960 /lib64/libpython2.7.so.1.0(+0xfb5ff)[0x7f538b8a75ff] > > 172961 --- END LIBC BACKTRACE --- > " > any idea? this only happen during real simulation, and sometimes we can > avoid it by running longer warmup in atomic mode. > > best, > Da Zhang > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > 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
