LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: trying to debug my failure to start "init"
Date: Wed, 9 Jun 2004 19:17:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406091911340.3310@localhost.localdomain> (raw)


  just before i pack it in for the day, i'm still grappling with why i
can't get the linuxppc-2.5 kernel to start the init/minit program on my
8xx board.  very curious, since it used to be able to, even if it hung
immediately afterwards.

  for more feedback, i added a printk() call to the run_init_process()
function in init/main.c to see what it thought it was doing.  the tail end
of my boot sequence was:

...
Kernel command line: console=ttyS0,9600 rw root=/dev/ram0 init=/sbin/minit
... snip ...
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).             <-- good
Mounted devfs on /dev                            <-- also good
Freeing unused kernel memory: 52k init
Trying run_init_process with /sbin/minit         <-- hmm, that should work
Trying run_init_process with /sbin/init
Trying run_init_process with /etc/init
Trying run_init_process with /bin/init
Trying run_init_process with /bin/sh
Kernel panic: No init found.  Try passing init= option to kernel.


  at this point, i'm out of ideas, and in need of a beer.  thanks to
everyone who's provided advice so far.

rday

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

             reply	other threads:[~2004-06-09 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 23:17 Robert P. J. Day [this message]
2004-06-10 12:25 ` trying to debug my failure to start "init" Mark Chambers
2004-06-10 13:00   ` Robert P. J. Day
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10  4:57 MuthuGanesh M

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=Pine.LNX.4.58.0406091911340.3310@localhost.localdomain \
    --to=rpjday@mindspring.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