From: Oliver Amft <oam@oamx.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: initial shell respawning too fast
Date: Wed, 20 Mar 2002 19:02:50 +0100 [thread overview]
Message-ID: <3C98CECA.E7187E8C@gmx.net> (raw)
I am trying to boot Linux (linuxppc_2_4_devel 2.4.19-pre1) from a
Walnut,
405GP Rev D board - All works fine till INIT starts (see screen
printout below). The root fs (nfs boot) is an older version of the
HardHat filesystem. bash crashes somehow, but unforunatly it prints no
report. An old HHL 2.4.0-test2 kernel still works with this root fs.
INIT: version 2.77 booting
INIT: Entering runlevel: 3
INIT: Id "sh" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
INIT: Id "sh" respawning too fast: disabled for 5 minutes
INIT: Id "sh" respawning too fast: disabled for 5 minutes
INIT: Id "sh" respawning too fast: disabled for 5 minutes
INIT: Id "sh" respawning too fast: disabled for 5 minutes
Probably I am missing some trivial thing - any ideas welcome!
Oliver
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-03-20 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 18:02 Oliver Amft [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-22 8:53 initial shell respawning too fast Frank Haverkamp
2002-03-22 13:04 Oliver Amft
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=3C98CECA.E7187E8C@gmx.net \
--to=oam@oamx.net \
--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).