From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kgdb/Sandpoint -- patch & help needed
Date: Tue, 19 Sep 2000 14:39:17 +1100 [thread overview]
Message-ID: <7803.969334757@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Alex Shnitman <alexsh@hectic.net> of "Mon, 18 Sep 2000 17:16:27 +0300." <20000918171627.B4328@hectic.net>
On Mon, 18 Sep 2000 17:16:27 +0300, Alex Shnitman <alexsh@hectic.net> writes:
>... However, with this patch the kernel
>hangs right after saying "Now booting the kernel". I don't even see
>how these changes could affect the boot process so early.
Aha! I was caught by this. When you enable CONFIG_KGDB, a breakpoint is
executed in setup_arch() which is just about the first thing the kernel
does.
The sequence is (very!) roughly (and for the 8xx embedded platform):
_start()
identify_machine()
MMU_init()
start_kernel()
lock_kernel()
setup_arch()
set_debug_traps() | ifdef CONFIG_KGDB
breakpoint() |
...
parse_options()
trap_init()
init_IRQ()
...
Solution? Simply start gdb on your host machine and do the following:
set remotebaud BBBBBB (if required)
target remote /dev/... (serial port on host connected to
target kgdb serial port)
continue
and your kernel will fire up again (I kicked myself when I realised what
was going on). Cheers!
Murray...
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-19 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alexsh@hectic.net>
2000-09-18 14:16 ` kgdb/Sandpoint -- patch & help needed Alex Shnitman
2000-09-19 3:39 ` Murray Jensen [this message]
2000-09-19 16:39 ` Alex Shnitman
2000-09-19 17:00 ` Dan Malek
2000-09-20 12:34 ` Alex Shnitman
2000-09-19 17:40 ` Mark A. Greer
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=7803.969334757@msa.cmst.csiro.au \
--to=murray.jensen@cmst.csiro.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.