You shouldn't really need any special .config options, although use
more adventurous settings at your own risk. Where is it hanging? Is
there any output at all? What I usually did when this happened was to
wait until I thought it was hung, kill it so that it printed what tick
it stopped at, and then run it again with tracing turned on at that
tick. Be careful, once it hits that tick you can fill up your
harddrive pretty quickly if you've wandered away. Hopefully you'll be
able to tell what function it's in, what it's waiting on, if it's
still executing instructions, if it ran off into junk memory, etc.
Also some parts of boot just take a long time, but since you've
already booted something I'm guessing you know what to expect. When I
have a chance and if I can find it, I'll send out the .config I used
to make one of my kernels.
Gabe
Quoting Joel Hestness <hestn...@cs.utexas.edu>:
Hi,
This might be a question for Gabe:
Steve Reinhardt pointed me to a Linux binary that I have been able to boot
with X86_FS. I have built a couple different binaries from the Linux
source, including the M5 specific patches, but it appears that M5 hangs when
trying to boot them. I am wondering if there are any critical options that
I need to look for in the .config file, or if anyone has a .config
specifically for building X86_FS kernel binaries.
Also, any tips for debugging M5 Linux boot?
Thank you,
Joel
--
Joel Hestness
PhD Student, Computer Architecture
Dept. of Computer Science, University of Texas - Austin
http://www.cs.utexas.edu/~hestness
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
