Discussion:
How to fix the error of simulation with se.py and HMC.py
(too old to reply)
김창현
2018-11-01 02:52:24 UTC
Permalink
Hello, I am writing to you because I have questions about an error related to se.py simulation. Currently, I try to run SPEC2006 Benchmark by connecting the HMC memory to se.py but an error occurred during execution. The simple hello file ran well, but when I run the SPEC 2006 file, this situation occurred. Can you tell me where it went wrong?
gem5 Simulator System. http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 compiled Aug 14 2018 23:05:34
gem5 started Oct 27 2018 00:44:59
gem5 executing on user, pid 20102
command line: ./build/ARM/gem5.opt -d m5out/BaselineSingle/429.mcf configs/example/se.py --maxinst=1000000000 --fast-forward=2000000000 --cpu-type=ex5_LITTLE --cpu-clock=4GHz --mem-type=HMC_2500_1x32 --mem-size=4GB --caches --l1i_size=32kB --l1d_size=32kB --l2cache --l2_size=256kB --l3_size=8MB -c /home/undergra1/gem5/code/429.mcf/mcf --options=/home/undergra1/gem5/code/429.mcf/inp.in

info: Standard input is not a terminal, disabling listeners.
Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: DRAM device capacity (1024 Mbytes) does not match the address range assigned (256 Mbytes)
warn: Sockets disabled, not accepting gdb connections
Switch at instruction count:2000000000
info: Entering event queue @ 0. Starting simulation...
info: Increasing stack size by one page.
warn: readlink() called on '/proc/self/exe' may yield unexpected results in various settings.
Returning '/home/undergra1/gem5/code/429.mcf/mcf'
Switched CPUS @ tick 526109642000
switching cpus
warn: ClockedObject: Already in the requested power state, request ignored
warn: User mode does not have SPSR
warn: User mode does not have SPSR
**** REAL SIMULATION ****
info: Entering event queue @ 526109642000. Starting simulation...
panic: panic condition !(pkt->isRead() || pkt->isWrite()) occurred: Should only see read and writes at memory controller
Memory Usage: 4369184 KBytes
Program aborted at tick 526109764800
--- BEGIN LIBC BACKTRACE ---
./build/ARM/gem5.opt(_Z15print_backtracev+0x29)[0x55c3618e3f69]
./build/ARM/gem5.opt(_Z12abortHandleri+0x4a)[0x55c3618f7b6a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11630)[0x7fe268312630]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x9f)[0x7fe266bde7ef]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fe266be03ea]
./build/ARM/gem5.opt(+0x73bc7f)[0x55c3617ddc7f]
./build/ARM/gem5.opt(_ZN8DRAMCtrl13recvTimingReqEP6Packet+0x15a)[0x55c361a46c4a]
./build/ARM/gem5.opt(_ZN15NoncoherentXBar13recvTimingReqEP6Packets+0x48e)[0x55c361a5593e]
./build/ARM/gem5.opt(+0x9dbb74)[0x55c361a7db74]
./build/ARM/gem5.opt(_ZN10EventQueue10serviceOneEv+0xd9)[0x55c3618eb259]
./build/ARM/gem5.opt(_Z9doSimLoopP10EventQueue+0x58)[0x55c361904e68]
./build/ARM/gem5.opt(_Z8simulatem+0xc1a)[0x55c361905e5a]
./build/ARM/gem5.opt(+0xdfe8b7)[0x55c361ea08b7]
./build/ARM/gem5.opt(+0x8abd53)[0x55c36194dd53]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x87ff)[0x7fe2685a87cf]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7c34)[0x7fe2685a7c04]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7c34)[0x7fe2685a7c04]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7c34)[0x7fe2685a7c04]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7fe26859fe49]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8868)[0x7fe2685a8838]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7c34)[0x7fe2685a7c04]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x86c)[0x7fe26870099c]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19)[0x7fe26859fe49]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[0x7fe26860d366]
./build/ARM/gem5.opt(_Z6m5MainiPPc+0x8f)[0x55c3618f644f]
./build/ARM/gem5.opt(main+0x33)[0x55c3617807e3]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fe266bc93f1]
--- END LIBC BACKTRACE ---

Loading...