I'm not aware of anybody else having this problem. Does it hang,
return an error from gem5, return an error from the kernel on the
terminal, or? Did you try building from scratch by deleting the entire
build directory? Sometimes stray files can survive longer than they're
supposed to and mess up incremental builds. A lot will have changed in
your update, so there's a non-zero chance of that happening.
Gabe
Quoting "Ankita (Garg) Goel" <[email protected]>:
Hi,
I have been using X86_FS for a while now. Just upgraded to the new version
that has combined FS and SE mode. However, now I am unable to boot into
Linux. The command I used is:
# build/X86/gem5.opt configs/example/fs.py --cpu-type=[detailed|timing]
--kernel=x86_64-vmlinux-2.6.28.4-smp --caches
The kernel does boot up if the cpu-type is the default, ie, atomic. Is this
a known issue ?
--
Regards,
Ankita
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
