Re: [gem5-users] Panic: initiateAcc not defined! error with ruby_fs.py on x86

Hi all, I realized that I could run ruby_fs with only --cpu-type=timing and -cpu-type=detailed. However I encounter errors as following for both cases. 1. build/X86/gem5.opt configs/example/ruby_fs.py --disk-image=/home/sanem/full_system_images/disks/linux-x86.img

Re: [gem5-users] Panic: initiateAcc not defined! error with ruby_fs.py on x86

So, The first thing you need to do is identify which x86 instruction is causing this (mnemonic and binary encoding). This looks to be an issue in the ISA decoder for gem5 either not properly detecting the instruction you are executing or not fully supporting it. Basically, you are executing

[gem5-users] Panic: initiateAcc not defined! error with ruby_fs.py on x86

Hi all, I encounter the error as following when I simulate ruby_fs.py on x86. 1. scons build/X86/gem5.opt PROTOCOL=MESI_CMP_directory RUBY=True 2. build/X86/gem5.opt configs/example/ruby_fs.py --disk-image=/home/sanem/full_system_images/disks/linux-x86.img