Recently I have asked a question about "invalid microop". Still the
problem exist. I have some other questions that may help fixing that
error.
1- I built X86_FS/m5.opt and used x86_64-vmlinux-2.6.22.9. I have to
say that I manually added
self.kernel = binary('x86_64-vmlinux-2.6.22.9')
to makeLinuxX86System function. In the downloaded package from
repository kernel, that line was not present.
2- There is no bigswap2.img for x86 disk image (I downloaded the disk
image from gem5 site). I manually copied linux-bigswap2.img from ALPHA
disk image to x86 disk image.
3- I created 401.bzip2.rcS which contain
#!/bin/sh
cd /401.bzip2
/sbin/m5 resetstats
./bzip2_base.amd64-m64-gcc44-nn liberty.jpg 30
/sbin/m5 exit
4- I ran this command:
/build/X86_FS/m5.opt ./configs/example/fs.py
--script=configs/boot/401.bzip2.rcS
However I get this
info: Entering event queue @ 0. Starting simulation...
panic: Invalid microop!
@ cycle 1000
[invoke:build/X86_FS/arch/generic/debugfaults.hh, line 93]
Memory Usage: 225576 KBytes
Program aborted at cycle 1000
I want to know if the "invalid microop" is related to my binary file
or the provided x86 kernel. It seems that the kernel has not been
booted yet so I think there is no problem with my binary file.
Any comment is welcomed.
--
// Naderan *Mahmood;
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
