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 what looks like a non-memory instruction as a memory operation. The panic in o3 for "Unknown Type" is because the instruction is not marked as a load or store, but is being handled by the memory dependency unit. The later fault for the timing cpu model (initiateAcc()) is likely on the same instruction, it was just able to get farther and try to actually execute the non-memory instruction as a memory instruction. Since the initiateAcc() function is only implemented for memory operations, this is why you got a panic. Either it's a bad encoding or gem5's decoder doesn't properly handle the instruction you are trying to execute. First step to fixing this is figuring out what the instruction was. On Tue, Jan 7, 2014 at 6:22 AM, Sanem Arslan <sanem.ars...@boun.edu.tr>wrote: > 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 > --kernel=/home/sanem/full_system_images/binaries/x86_64- > vmlinux-2.6.22.9.smp > --cpu-type=detailed > > > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > panic: Unknown type! (most likely a barrier). > @ cycle 872471049555235488 > [insert:build/X86/cpu/o3/mem_dep_unit_impl.hh, line 252] > Memory Usage: 872471049555235488 KBytes > Program aborted at cycle 173000 > Aborted (core dumped) > > > 2. build/X86/gem5.opt configs/example/ruby_fs.py > --disk-image=/home/sanem/full_system_images/disks/linux-x86.img > --kernel=/home/sanem/full_system_images/binaries/x86_64- > vmlinux-2.6.22.9.smp > --cpu-type=timing > > > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > panic: initiateAcc not defined! > @ cycle 847301579128001184 > [initiateAcc:build/X86/cpu/static_inst_exec_sigs.hh, line 30] > Memory Usage: 847301579128001184 KBytes > > Program aborted at cycle 165000 > > Do you have any idea about these errors? > > > Thank you in advance for your time and help. > Best Regards, > Sanem > > Sanem Arslan <sanem.ars...@boun.edu.tr> > > > 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 >> --kernel=/home/sanem/full_system_images/binaries/x86_64- >> vmlinux-2.6.22.9.smp >> >> Global frequency set at 1000000000000 ticks per second >> info: kernel located at: /home/sanem/full_system_images/binaries/x86_64- >> vmlinux-2.6.22.9.smp >> 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012 >> Listening for com_1 connection on port 3458 >> warn: Reading current count from inactive timer. >> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7002 >> **** REAL SIMULATION **** >> info: Entering event queue @ 0. Starting simulation... >> panic: initiateAcc not defined! >> @ cycle 853353291127280288 >> [initiateAcc:build/X86/cpu/static_inst_exec_sigs.hh, line 30] >> Memory Usage: 853353291127280288 KBytes >> Program aborted at cycle 165000 >> Aborted (core dumped) >> >> However, when I simulate fs.py on x86, there is no such error. >> >> build/X86/gem5.opt configs/example/fs.py --disk-image=/home/sanem/full_ >> system_images/disks/linux-x86.img --kernel=/home/sanem/full_ >> system_images/binaries/x86_64-vmlinux-2.6.22.9.smp >> >> gem5 Simulator System. http://gem5.org >> gem5 is copyrighted software; use the --copyright option for details. >> >> gem5 compiled Dec 24 2013 15:46:08 >> gem5 started Dec 24 2013 16:01:47 >> gem5 executing on localhost.localdomain >> command line: build/X86/gem5.opt configs/example/fs.py >> --disk-image=/home/sanem/full_system_images/disks/linux-x86.img >> --kernel=/home/sanem/full_system_images/binaries/x86_64- >> vmlinux-2.6.22.9.smp >> Global frequency set at 1000000000000 ticks per second >> info: kernel located at: /home/sanem/full_system_images/binaries/x86_64- >> vmlinux-2.6.22.9.smp >> 0: rtc: Real-time clock set to Sun Jan 1 00:00:00 2012 >> Listening for com_1 connection on port 3458 >> warn: Reading current count from inactive timer. >> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7002 >> **** REAL SIMULATION **** >> info: Entering event queue @ 0. Starting simulation... >> warn: Don't know what interrupt to clear for console. >> >> Why can this error occur? Have I missed any important point? I have >> searched on the web but I could not find any solution. >> >> Thank you in advance for your time and help. >> >> Best Regards, >> Sanem. >> _______________________________________________ >> 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 >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
