Hi, I have the same problem. I have taken a checkpoint using SE mode with classic memory and timing CPU.
build/X86_MOESI_hammer/gem5.fast ../configs/example/ruby_se.py -c ./bin/astar -o "BigLakes2048.cfg" --cpu-type=timing --mem-size=4096MB -r 1 Then, i tried to restore execution using RUBY: build/X86_MOESI_hammer/gem5.fast ../configs/example/se.py -c ./bin/astar -o "BigLakes2048.cfg" --restore-with-cpu=timing --cpu-type=timing --mem- size=4096MB -r 1 --ruby gdb reports: rogram terminated with signal 11, Segmentation fault. #0 0x0000000000fb4454 in PhysicalMemory::unserializeStore (this=0x419c5d0, cp=0x46e06e0, section=...) at build/X86_MOESI_hammer/mem/physical.cc:399 399 uint8_t* pmem = backingStore[store_id].second; #0 0x0000000000fb4454 in PhysicalMemory::unserializeStore (this=0x419c5d0, cp=0x46e06e0, section=...) at build/X86_MOESI_hammer/mem/physical.cc:399 #1 0x0000000000fb3601 in PhysicalMemory::unserialize (this=0x419c5d0, cp=0x46e06e0, section=...) at build/X86_MOESI_hammer/mem/physical.cc:371 #2 0x0000000001337a5a in System::unserialize (this=0x419c4c0, cp=0x46e06e0, section=...) at build/X86_MOESI_hammer/sim/system.cc:376 #3 0x00000000013222ff in SimObject::loadState (this=0x419c4c0, cp=0x46e06e0) at build/X86_MOESI_hammer/sim/sim_object.cc:82 #4 0x00000000018625fd in _wrap_SimObject_loadState (args=0x3f985f0) at build/X86_MOESI_hammer/python/m5/internal/param_SimObject_wrap.cc:3012 #5 0x00007f3ed7f6203b in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #6 0x00007f3ed7f6372c in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #7 0x00007f3ed7f625ff in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #8 0x00007f3ed7f6372c in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #9 0x00007f3ed7f625ff in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #10 0x00007f3ed7f62703 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #11 0x00007f3ed7f6372c in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #12 0x00007f3ed7f63882 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0 #13 0x00007f3ed7f61725 in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #14 0x00007f3ed7f6372c in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #15 0x00007f3ed7f625ff in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #16 0x00007f3ed7f6372c in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #17 0x00007f3ed7f63882 in PyEval_EvalCode () from /usr/lib/libpython2.6.so.1.0 #18 0x00007f3ed7f8497d in PyRun_StringFlags () from /usr/lib/libpython2.6.so.1.0 #19 0x00000000012dfc1c in m5Main (argc=11, argv=0x7fff3345df38) at build/X86_MOESI_hammer/sim/init.cc:280 #20 0x000000000040b18b in main (argc=11, argv=0x7fff3345df38) at build/X86_MOESI_hammer/sim/main.cc:57 Is it possible to restore execution using RUBY from a checkpoint created using classic memory model when using SE mode? Thank you in advance. Adrian _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
