All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Alex Shnitman <alexsh@hectic.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kgdb/Sandpoint -- patch & help needed
Date: Tue, 19 Sep 2000 10:40:03 -0700	[thread overview]
Message-ID: <39C7A4F3.133DF04D@mvista.com> (raw)
In-Reply-To: 20000919193930.C1406@hectic.net


Alex Shnitman wrote:

> 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?

printk's are logged to a buffer until the kernel has initialized the console
and then dumps it all out.  At this point, the console isn't initialized.  The
initialization is done with the call to console_init() (in
init/main.c:start_kernel) which eventually calls register_console() which will
dump out the logged msgs.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-09-19 17:40 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
2000-09-19 17:00       ` Dan Malek
2000-09-20 12:34         ` Alex Shnitman
2000-09-19 17:40       ` Mark A. Greer [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=39C7A4F3.133DF04D@mvista.com \
    --to=mgreer@mvista.com \
    --cc=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 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.