Hi Tang, This is likely happening because the custom kernel you built has flags for certain devices enabled, devices which are most likely not supported in gem5. I encountered this problem myself when building custom x86 kernels. I used the parsec x86 kernel flags as a starting point, and disabled many of the remaining flags that the build process prompted me for when building it. You can reference the system.terminal output to see which device is probably causing the error.
Malek On Fri, Aug 8, 2014 at 5:44 PM, Dongjie Tang via gem5-users < gem5-users@gem5.org> wrote: > I made a kernel by myself, but when I run ' > /mnt/nokrb/tangdj/gem5/build/X86/gem5.opt -d > /mnt/nokrb/tangdj/gem5/Output/m5_augreal_1h configs/example/fs.py > --script=/mnt/nokrb/tangdj/gem5/MEV/rcs_augreal/test_augreal_1h.rcS > --cpu-type=detailed --caches --l2cache > --kernel=/mnt/nokrb/tangdj/full-system_images/binaries/vmlinux > --l2_size=512kB > --disk-image=/mnt/nokrb/tangdj/full-system_images/disks/opencv.img -F > 1000000000 -I 100000000 '; it gives me such a problem: > fatal: Unable to find destination for addr 0x80000000000000ed on bus > system.iobus > Could someone know what happened and how to solve that problem? > > Thank you very much > > Tang > > _______________________________________________ > 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
