linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: jim <jduey@ccc-dcs.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Delay on starting init
Date: Wed, 11 Sep 2002 12:34:54 +0000	[thread overview]
Message-ID: <20020911175118.04A9E38E9D@server.weathercom.com> (raw)


I pulled the lastest 2.4 devel tree from Monte Vista's mirror a couple of
days ago and the behaviour of the boot process changed.  Now, the process
pauses for a long time after the message; "Freeing unused kernel memory".  To
make sure this was a kernel issue, I reverted to the previous kernel and it
booted with no delay.  Also, the delay is apparent on both Hard Hat Linux 2.0
and ELDK from Denx.

Is anyone aware of what changed?

Thanks,
Jim

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

             reply	other threads:[~2002-09-11 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 12:34 jim [this message]
2002-09-12  1:24 ` Delay on starting init David Gibson
2002-09-12  1:32   ` Jin Cheng
2002-09-12 10:27   ` jim
2002-09-25  5:33     ` Scott Anderson

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=20020911175118.04A9E38E9D@server.weathercom.com \
    --to=jduey@ccc-dcs.com \
    --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).