From: Alex Shnitman <alexsh@hectic.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kgdb/Sandpoint -- patch & help needed
Date: Tue, 19 Sep 2000 19:39:30 +0300 [thread overview]
Message-ID: <20000919193930.C1406@hectic.net> (raw)
In-Reply-To: <7803.969334757@msa.cmst.csiro.au>; from Murray.Jensen@cmst.csiro.au on Tue, Sep 19, 2000 at 02:39:17PM +1100
Hi, Murray!
On Tue, Sep 19, 2000 at 02:39:17PM +1100, you wrote the following:
> >... 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.
Right, but before calling setup_arch, it prints the linux kernel
banner! Here's the code:
printk(linux_banner);
setup_arch(&command_line, &memory_start, &memory_end);
And I don't see the banner. Did you see it when you encountered this?
--
Alex Shnitman | http://www.debian.org
alexsh@hectic.net, alexsh@linux.org.il +-----------------------
http://alexsh.hectic.net UIN 188956 PGP key on web page
E1 F2 7B 6C A0 31 80 28 63 B8 02 BA 65 C7 8B BA
NTL have a new network routing protocol as invented for amusing
small children. Its called 'now you see it now you dont' with much
of the US vanishing at cardiff for 10 seconds every minute or so.
-- Alan Cox on a diary update
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-19 16: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
2000-09-19 16:39 ` Alex Shnitman [this message]
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=20000919193930.C1406@hectic.net \
--to=alexsh@hectic.net \
--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 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).