That worked fine for me. You might want to try deleting your build directory and recompiling gem5, but I have no idea if that will actually fix your problem. Since that works for most people and is (more or less) part of nightly tests that we run I'm sure it works, so the problem must have something to do with how your machine is set up. The fact that it dies immediately with an invalid microop is very strange. Maybe you aren't giving your virtual machine enough memory? (I assume you're using virtual box)
Gabe On 07/06/11 12:23, ?? wrote: > Hi, > > I compiled a X86_SE model successfully. "scons build/X86_SE/m5.opt" > However, I got a error when I test this model. "build/X86_SE/m5.opt > configs/example/se.py" > > VirtualBox:~/m5$ build/X86_SE/gem5.opt configs/example/se.py > gem5 Simulator System. http://gem5.org > gem5 is copyrighted software; use the --copyright option for details. > > gem5 compiled Jul 6 2011 15:14:30 > gem5 started Jul 6 2011 15:15:24 > gem5 executing on shu-VirtualBox > command line: build/X86_SE/gem5.opt configs/example/se.py > Global frequency set at 1000000000000 ticks per second > 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > panic: Invalid microop! > @ cycle 500 > [invoke:build/X86_SE/arch/generic/debugfaults.hh, line 93] > Memory Usage: 552440 KBytes > Program aborted at cycle 500 > Aborted > > Dose anyone know how to solve this problem? > > Regards, > Zhen. > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
