From: "Vijay Sampath" <vsampath@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problem porting linux 2.6 on IBM405EP based boards
Date: Wed, 13 Dec 2006 19:03:58 -0800 [thread overview]
Message-ID: <758a2bbf0612131903w63a11c60t6f13e68fd3d7e3df@mail.gmail.com> (raw)
In-Reply-To: <458047D3.8060401@freescale.com>
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 <scottwood@freescale.com> 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
>
prev parent reply other threads:[~2006-12-14 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 17:26 Problem porting linux 2.6 on IBM405EP based boards Vijay Sampath
2006-12-13 18:34 ` Scott Wood
2006-12-14 3:03 ` Vijay Sampath [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=758a2bbf0612131903w63a11c60t6f13e68fd3d7e3df@mail.gmail.com \
--to=vsampath@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).