Hi Mitch,
I agree with you. The original command didn't use either checkpoint or
fastforward. Therefore, no cpu switching is expected by gem5. However,
the PARSEC script (i assume it is generated automatically) forces the
cpu switching. This should be the reason of assertion failure.
Bahar, you can either remove the "/sbin/m5 switchcpu" or generate a
checkpoint first to let gem5 do the cpu switching. Also, you can take a
look at the setCPUClass() and run() in configs/common/Simulation.py to
see how gem5 will expect a cpu switching.
-Tao
On 02/01/2013 01:04 PM, Mitch Hayenga wrote:
Hi,
I'm currently traveling and don't run full system that much myself
these days. So maybe someone else would be a better choice to help you.
That said, I searched the list for your error and it looks like its
the same problem as discussed in this thread?
http://comments.gmane.org/gmane.comp.emulators.m5.users/9504
Basically, remove the call to switchcpu from the rcs file?
On Wed, Jan 30, 2013 at 12:04 AM, Bahar Asgari <bahar.asg...@gmail.com
<mailto:bahar.asg...@gmail.com>> wrote:
Hi!
Dear Mitch, Thanks for your kindly helps.
I'm tried to find the start of benchmark execution, so I've ran
the program
in the bigger ticks, such as, from 4999000000000 to 5000000000000.
But as you can see in continue, I've encountered an error, which
causes the simulation to abort in a cycle.
command line: ./build/ALPHA/gem5.debug --debug-flags=Exec
--trace-start=4999000000000 --trace-file=/media/6288-B09B/test1.out
configs/example/fs.py --cpu-type=detailed --caches --l2cache --script
/media/6288-B09B/parsec/blackscholes_4c_simmedium.rcS -m 5000000000000
-n 4
Global frequency set at 1000000000000 ticks per second
info: kernel located at:
/media/6288-B09B/m5_system_2.0b3/binaries/vmlinux
Listening for system connection on port 3456
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...
info: Launching CPU 1 @ 112938000
info: Launching CPU 2 @ 114570000
info: Launching CPU 3 @ 116228000
warn: Prefetch instructions in Alpha do not do anything
warn: Prefetch instructions in Alpha do not do anything
hack: be nice to actually delete the event here
Exiting @ tick 2362947327500 because switchcpu
gem5.debug: build/ALPHA/sim/eventq.cc:63: virtual Event::~Event():
Assertion `!scheduled()' failed.
Program aborted at cycle 2362947327500
Aborted
Note that in the time before 2362947327500, the cycle's traces are
same for different benchmarks, and It seems that the benchmark
didn't execute yet.
Is it possible to estimate the start time of a benchmark execution
in such a large trace file?
And what is the reasons of above error and warnings?
Best Regards
--
Bahar Asgari
Department of Computer Engineering
Iran University of Science and Technology
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org <mailto: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
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
