linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Jack Liu <Jack_liu@usish.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linux booting problem: init start up very slowly and print kernel infor character by character
Date: Wed, 24 Mar 2004 18:01:17 +0100	[thread overview]
Message-ID: <4061BEDD.1080304@246tNt.com> (raw)
In-Reply-To: <200403241240.i2OCeakY022508@ms.usish.com>


Hi

>  Booting infomation:
>		.......
>		mice: PS/2 mouse device common for all mice
>		VFS: Mounted root (ext2 filesystem) readonly.
>		Freeing unused kernel memory: 64k init
>		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~before this, everything is OK.
>		INIT: version 2.84 booting
>  			              Welcome....
>        From "INIT", system seems to start very slowly. "INIT" and other kernel infomation were printed out character  by character with some kind of delay between them.It took even five minutes to mount a proc file system.
>        What could be the problem?
>		Is this becuase of disk configuation problem since init is the first program got called from disk?
>
>
>
Well, I suppose that it's on a serial console.

For me it sounds like a serial problem. Everything before the "INIT:
..." is printed via printk and is then handled by the 'console' part of
the serial driver. In all the drivers I've used/seen this is done the
simpliest way, often via busy waiting on the uart, without interrupts,
.... When the init program it's called, it doesn't use the console stuff
( it's unidirectionnal anyway ... ) but it open /dev/ttyS0 ( or the
appropriate device ) and it's not at all the same code running. Here (
again, in the driver I worked with ), interrupts are used to know when
the UART is ready or when chars are incoming, ...

What you could try to see if it comes from the serial stuff, is disable
consoel completely and 'see' the time it takes to boot ( of course you
need to have another visible effect that you system is fully booted like
inserting a ping -c 1 at the end of the init scripts ... )

My 2 cents, ...

    Sylvain

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

      reply	other threads:[~2004-03-24 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 12:39 linux booting problem: init start up very slowly and print kernel infor character by character Jack Liu
2004-03-24 17:01 ` Sylvain Munaut [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=4061BEDD.1080304@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=Jack_liu@usish.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).