From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200403250205.i2P25CkY017784@ms.usish.com> From: "Jack Liu" To: Sylvain Munaut Cc: "linuxppc-embedded@lists.linuxppc.org" Subject: Re: linux booting problem: init start up very slowly and print kernelinfor character by character Mime-Version: 1.0 Content-Type: text/plain Date: Thu, 25 Mar 2004 10:04:21 +0800 Sender: owner-linuxppc-embedded@lists.linuxppc.org List-Id: Sylvain Munaut hi,all Thanks a lot. I checked my porting code and the answer is yes. After assigned a right interrupt number, everything is ok. Best regards ======= 2004-03-24 18:01:00 Origianl message======= >> 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 ... ) = = = = = = = = = = = = = = = = = = = = Best regards Jack Liu R&D Dept. USI(Shanghai) Inc. Tel: +86-21-58966996x115 Fax: +86-21-58967931 Email: Jack_liu@usish.com http://www.usi.com.tw ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/