Hi, I am testing new protocols using splash2 benchmark under SE mode.. I am geeing following error.
*command line: ./build/X86_NEW/gem5.debug ./configs/example/se.py --ruby -n4 --cpu-type=timing --l1d_size=16kB --l1i_size=16kB --l1d_assoc=1 --l1i_assoc=1 --mem-size=4194304kB --topology=Crossbar --cpu-clock=2GHz --ruby-clock=2GHz --mem-type=SimpleMemory -c /home/midhun/git_repos/splash2/codes/kernels/fft/fft -o '-m 10 -p 4 -t'* *block_size_bits 6* *NUM_CPU I: 0* *NUM_CPU I: 1* *NUM_CPU I: 2* *NUM_CPU I: 3* *Global frequency set at 1000000000000 ticks per second* *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* ***** REAL SIMULATION ***** *info: Entering event queue @ 0. Starting simulation...* *panic: Possible Deadlock detected. Aborting!* *version: 0 request.paddr: 0x[0x17c8, line 0x17c0] m_readRequestTable: 1 current time: 250000000 issue_time: 0 difference: 250000000* * @ tick 250000000* *[wakeup:build/X86_NEW/mem/ruby/system/Sequencer.cc, line 114]* *Memory Usage: 4857412 KBytes* *Program aborted at cycle 250000000* *Aborted (core dumped)* How to know the actual error or debug log to identify the exact issue? Regards, Midhun P mail to : [email protected] Mobile : +91-9946001223 <[email protected]>
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
