It may be the upward compatibility problem. If there is a syscall invented in newer version kernel than the virtual machine kernel, the older one cannot process the syscall request.
It will be helpful to check the compatibility issues between your x86_FS images and the machine you build your cpu2006. 2012. 5. 18. 오전 1:33에 "Diana Guttman" <[email protected]>님이 작성: > Hello, > > Does anyone know what could be causing this error? I am trying to run > Spec2006 benchmarks to test my gem5 setup for X86_FS. The kernel boots > fine and mounts the file system. The binaries are already compiled and > they work on the system where I compiled them, also x86-64. I get this > error in the terminal: > > (none) CPU2006 # ./458.sjeng/run/build_base_amd64-m64-gcc47-nn.0000/sjeng > FATAL: kernel too old > sjeng[810]: segfault at 00002b12e1694de0 rip 0000000000453377 rsp > 00007fff3c251140 error 4 > Segmentation fault > (none) CPU2006 # > > It doesn't crash the simulation or the virtual OS. I made the disk image > using the gem5img.py tool to make a blank image, and then copied all the > files from the provided x86root.img into the new image. > > Thanks, > Diana > > > _______________________________________________ > 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
