Oh. KGDB. Makes perfect sense. Cool will try to setup a serial debugger or try and enable printks or try and debug with emulator with no kgdb. Currently printks don't work (although ppc specific prints ppc_md.progress() appear on the console). What does it take to get printk to work early on? Regardless I have enough to proceed now.
Vijay On 12/13/06, Scott Wood <[EMAIL PROTECTED]> wrote: > Vijay Sampath wrote: > > After this, the code started executing start_kernel, but stopped > > shortly thereafter (snippet B). After this every time I press a key, > > the following line gets printed: > > > > $T0740:30300a00;01:c0621fb0;#45 > > > > Its possible that I have something configured wrong, but > > any guidance on what that message could possibly mean would be > > appreciated. > > That looks like output from a GDB stub. You may want to try turning off > GDB support in your kernel in order to (probably) get an oops message > instead (you may need to do something special to hook printk up to the > early debug console). Alternately, you could try attaching to it with GDB. > > -Scott > _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
