From: Matt Porter <porter@cox.net>
To: Stefano Bodini <s.bodini@comcast.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Frozen ! any idea ?
Date: Thu, 5 Dec 2002 12:17:33 -0700 [thread overview]
Message-ID: <20021205121733.A14807@home.com> (raw)
In-Reply-To: <5.1.0.14.0.20021205132823.00a3aac0@pop3.norton.antivirus>; from s.bodini@comcast.net on Thu, Dec 05, 2002 at 01:28:31PM -0500
On Thu, Dec 05, 2002 at 01:28:31PM -0500, Stefano Bodini wrote:
> In order to try to debug something I enabled the KDGB in the kernel
> (following the instructions on the MontaVista documentation).
>
> I recompiled the kernel, no errors .. but when I try to load and start it :
>
> [Go 00400000]
> loaded at: 00410000 004A81F4
> relocated to: 00400000 004981F4
> board data at: 00495128 00495144
> relocated to: 004052C4 004052E0
> zimage at: 00405960 004945AA
> avail ram: 00499000 01000000
>
> Linux/PPC load: root=/dev/nfs rw ip=auto
> Uncompressing Linux...done.
> Now booting the kernel
>
> That's it.
> Stops. No warning, no errors .. just stops.
> I'm sure this is not a minicom problem this time ... any ideas ?
There is an early default breakpoint set when you enable KGDB on
PPC. You've hit it and need to be communicating with the in-kernel
stub to continue.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-05 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 18:28 Frozen ! any idea ? Stefano Bodini
2002-12-05 18:44 ` Dave Wilhardt
2002-12-05 19:17 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 14:00 Steven Blakeslee
2002-12-02 14:15 ` Stefano Bodini
2002-11-25 19:44 Stefano Bodini
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=20021205121733.A14807@home.com \
--to=porter@cox.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=s.bodini@comcast.net \
/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).