Hello,
When I run parsec in FS mode with garnet-network = fixed, simulation always
get aborted ... Such problem does not happen if I run with garnet-network =
flexible. However, it seems the network power model in gem5 does not
support flexible pipeline, and so I have to go with fixed router pipeline.
command line: ./build/ALPHA_FS/gem5.opt -d
./m5out/blackscholes_16_16_1GHz_4_timing ./configs/example/ruby_fs.py
--checkpoint-restore=1 --restore-with-cpu timing --cpu-type=timing --caches
--l2cache --num-cpus=16 --num-dirs=16 --num-l2caches=16 --clock=1GHz
--l1d_size=64kB --l1i_size=64kB --l1d_assoc=2 --l1i_assoc=2 --l2_size=4MB
--l2_assoc=8 --cacheline_size=64 --ruby --garnet-network=fixed
--topology=Mesh --mesh-rows=4
Global frequency set at 1000000000000 ticks per second
info: kernel located at: /home/mdl/juz145/benchmark/parsec/binaries/vmlinux
Listening for system connection on port 3456
0: system.tsunami.io.rtc: Real-time clock set to Thu Jan 1 00:00:00
2009
0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000
0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001
0: system.remote_gdb.listener: listening for remote gdb #2 on port 7002
0: system.remote_gdb.listener: listening for remote gdb #3 on port 7003
0: system.remote_gdb.listener: listening for remote gdb #4 on port 7004
0: system.remote_gdb.listener: listening for remote gdb #5 on port 7005
0: system.remote_gdb.listener: listening for remote gdb #6 on port 7006
0: system.remote_gdb.listener: listening for remote gdb #7 on port 7007
0: system.remote_gdb.listener: listening for remote gdb #8 on port 7008
0: system.remote_gdb.listener: listening for remote gdb #9 on port 7009
0: system.remote_gdb.listener: listening for remote gdb #10 on port 7010
0: system.remote_gdb.listener: listening for remote gdb #11 on port 7011
0: system.remote_gdb.listener: listening for remote gdb #12 on port 7012
0: system.remote_gdb.listener: listening for remote gdb #13 on port 7013
0: system.remote_gdb.listener: listening for remote gdb #14 on port 7014
0: system.remote_gdb.listener: listening for remote gdb #15 on port 7015
**** REAL SIMULATION ****
info: Entering event queue @ 2293633599000. Starting simulation...
panic: Possible Deadlock detected. Aborting!
version: 0 request.paddr: 0x[0x3247c8, line 0x3247c0] m_readRequestTable: 1
current time: 2294133600000 issue_time: 2293633600000 difference: 500000000
@ cycle 2294133600000
[wakeup:build/ALPHA_FS/mem/ruby/system/Sequencer.cc, line 107]
Memory Usage: 906204 KBytes
Program aborted at cycle 2294133600000
Abort (core dumped)
Anyone knows how to fix such problem
Best,
Jia
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
