The new Gem5 stable version is not supporting fixed pipeline garnet
simulations. The simulation just fails after entering the event queue. I have
tried all the Ruby protocols (MOESI hammer, MESI two level, MESI CMP
directory), still the bug persisted in all protocols. With flexible pipeline
the simulation is working fine. I have attached the command used for executing
Gem5 and the result I got. Kindly let me know how to fix this.
command line: build/X86/gem5.fast configs/example/fs.py --caches --ruby
--cpu-clock=2.5GHz --cpu-type=timing --num-cpus=4 --num-l2cache=4 --num-dirs=4
--l1i_size=32kB --l1d_size=32kB --l2_size=8MB --topology=Mesh --mesh-rows=2
--garnet-network=fixed
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
warn: add_child('cls'): child 'credit_links0 credit_links1' already has parent
Global frequency set at 1000000000000 ticks per second
info: kernel located at:
/net/g/kduraisa/pvt/own_library/gem5/system/binaries/vmlinux
Listening for com_1 connection on port 3456
warn: Reading current count from inactive timer.
0: system.remote_gdb.listener: listening for remote gdb on port 7000
0: system.remote_gdb.listener: listening for remote gdb on port 7001
0: system.remote_gdb.listener: listening for remote gdb on port 7002
0: system.remote_gdb.listener: listening for remote gdb on port 7003
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
panic: Possible Deadlock detected. Aborting!
version: 0 request.paddr: 0x[0x1fdf380, line 0x1fdf380] m_readRequestTable: 1
current time: 3400002000 issue_time: 3160606000 difference: 239396000
threshold:200000000
@ tick 3400002000
[wakeup:build/X86/mem/ruby/system/Sequencer.cc, line 102]
Memory Usage: 993736 KBytes
Program aborted at tick 3400002000
Abort (core dumped)
Karthi Duraisamy
Research Scholar
School of Electrical Engineering and Computer Science
Washington State University
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
