linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marco Schramel <Schramel.Linux@go.bartec.de>
To: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Init hangs
Date: Thu, 5 Aug 2004 11:54:54 +0200	[thread overview]
Message-ID: <200408051154.54426.Schramel.Linux@go.bartec.de> (raw)


Hi,

my kernel hangs by initializing the system. My target is mpc8270-based. I use ELDK 3.0 and mount my root-fs over nfs.
Denx-kernel 2.4.25.


I added some printk's in the function "static int init(void * unused)" of  linux/init/main.c to see what happens.

#############################################################

	.
	.
	.
	(void) dup(0);
	(void) dup(0);

	/*
	 * We try each of these until one succeeds.
	 *
	 * The Bourne shell can be used instead of init if we are
	 * trying to recover a really broken machine.
	 */
	if (execute_command)
		run_init_process(execute_command);
	printk("before /sbin/init\n");
	run_init_process("/sbin/init");
	printk("before /etc/init\n");
	run_init_process("/etc/init");
	printk("before  /bin/init\n");
	run_init_process("/bin/init");
	printk("before  /bin/sh\n");
	run_init_process("/bin/sh");

##################################

the last lines of my boot messages
#######################################
IP-Config: Complete:
      device=eth0, addr=192.168.55.3, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.55.3, domain=, nis-domain=(none),
     bootserver=192.168.55.1, rootserver=192.168.55.1, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.55.1
Looking up port of RPC 100005/1 on 192.168.55.1
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 72k init
before /sbin/init

##############################################

It seems like it hangs in "run_init_process("/sbin/init");" or the /sbin/init - file does not work.
Sometimes the message "INIT: version 2.84 booting" is showed. And after printing this message it hangs, too.
But the most times it looks like above.

Any ideas?
Thanks in advance

Marco



---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone:  +49 (0)9929/301332
Fax:      +49 (0)9929/301112

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

             reply	other threads:[~2004-08-05  9:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  9:54 Marco Schramel [this message]
2004-08-05 10:33 ` Init hangs Wolfgang Denk
2004-08-05 15:28   ` Marco Schramel
2004-08-05 17:48     ` Wolfgang Denk
2004-08-06  6:26       ` Marco Schramel
2004-08-06  8:11         ` Wolfgang Denk
2004-08-06 11:22           ` Ralph Siemsen
2004-08-06 12:38             ` Dan Malek
2004-08-06 13:14               ` Robert P. J. Day
2004-08-06 13:49                 ` Dan Malek
2004-08-06 12:46             ` Wolfgang Denk
2004-08-06 13:12               ` Ralph Siemsen
2004-08-06 13:44               ` Dan Malek
2004-08-06 14:36                 ` Wolfgang Denk

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=200408051154.54426.Schramel.Linux@go.bartec.de \
    --to=schramel.linux@go.bartec.de \
    --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).