I am not sure whether it's related to the cache cohenrence protocol so i just give some hint. From your command, you didn't specify any cache coherence protocol. In other words, you use the default protoocl (MI_example). This protocol only allow one cache level (L1 cache only)... Tao 2011/9/20 lyh <168liuyuh...@163.com>
> Hi all, > *When I use 4x4 mesh network, the simulation detects a deadlock and cannot > continue.* > *Here is the record.* > > command line: ./build/ALPHA_FS/gem5.opt configs/example/ruby_fs.py -n 16 > --l1i_size=8kB --l1d_size=8kB --l2_size=128kB --num-l2caches=16 > --topology=Mesh --timing --num-dirs=16 -b fft --mesh-rows=4 > Global frequency set at 1000000000000 ticks per second > info: kernel located at: > /root/gem5/m5_system_2.0b3/binaries/vmlinux_2.6.27-gcc_4.3.4 > Listening for system connection on port 3457 > 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 7016 > 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7017 > 0: system.remote_gdb.listener: listening for remote gdb #2 on port 7018 > 0: system.remote_gdb.listener: listening for remote gdb #3 on port 7019 > 0: system.remote_gdb.listener: listening for remote gdb #4 on port 7020 > 0: system.remote_gdb.listener: listenin g for remote gdb #5 on port 7021 > 0: system.remote_gdb.listener: listening for remote gdb #6 on port 7022 > 0: system.remote_gdb.listener: listening for remote gdb #7 on port 7023 > 0: system.remote_gdb.listener: listening for remote gdb #8 on port 7024 > 0: system.remote_gdb.listener: listening for remote gdb #9 on port 7025 > 0: system.remote_gdb.listener: listening for remote gdb #10 on port 7026 > 0: system.remote_gdb.listener: listening for remote gdb #11 on port 7027 > 0: system.remote_gdb.listener: listening for remote gdb #12 on port 7028 > 0: system.remote_gdb.listener: listening for remote gdb #13 on port 7029 > 0: system.remote_gdb.listener: listening for remote gdb #14 on port 7030 > 0: system.remote_gdb.listener: listening for remote gdb #15 on port 7031 > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > info: Launching CPU 1 @ 1341472000 > info: Launching CPU 2 @ 1352183000 > info: Launching CPU 3 @ 1362 795000 > info: Launching CPU 4 @ 1373531500 > info: Launching CPU 5 @ 1397074500 > info: Launching CPU 6 @ 1433310000 > info: Launching CPU 7 @ 1443924000 > info: Launching CPU 8 @ 1454538000 > info: Launching CPU 9 @ 1465152000 > info: Launching CPU 10 @ 1476231000 > info: Launching CPU 11 @ 1487308000 > info: Launching CPU 12 @ 1498385000 > info: Launching CPU 13 @ 1509462000 > info: Launching CPU 14 @ 1520541000 > info: Launching CPU 15 @ 1531620000 > panic: Possible Deadlock detected. Aborting! > version: 0 request.paddr: 0x[0x15e60, line 0x15e40] m_writeRequestTable: 1 > current time: 4002001 issue_time: 3223640 difference: 778361 > @ cycle 2001000500 > [wakeup:build/ALPHA_FS/mem/ruby/system/Sequencer.cc, line 124] > Memory Usage: 644928 KBytes > Program aborted at cycle 2001000500 > Aborted > > > > _______________________________________________ > 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
