All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: linuxppc-embedded: /bin/sh wont run from nfsroot.
Date: Wed, 15 Dec 1999 16:22:44 +1100	[thread overview]
Message-ID: <385725A3.A1C110DF@ctam.com.au> (raw)
In-Reply-To: 19991215055541.23843.qmail@web301.mail.yahoo.com



I have made progress now that the caches are disabled.  I will leave
them disabled for now until I have a full working system via NFS (unless
someone advises me otherwise).

My system was getting stuck at the following piece of code.  I don't
know was SASH is but it is defined at the top of the file.  I commented
it out to see what would happen.  I also noticed that Magnus Damm's ADS
modifications also has the "#define SASH 1" commented out.  What is the
purpose of SASH and the implication of undefining it ?

#ifdef SASH
    {
        int i, pid;

        pid = kernel_thread(do_linux_sash, "sash", SIGCHLD);
        if (pid > 0)
            while (pid != wait(&i));
    }
#else
    ....
#endif


After undefining it, the kernel got further.  It gets to the point where
it tries to run /bin/sh and then just sits there.  Here is the last part
of the console ouput.  Any ideas where to go from here.

Brendan.

eth0: CPM ENET Version 0.2, 00:d0:1f:11:22:33
IP-Config: Guessing netmask 255.255.255.0
Looking up port of RPC 100003/2 on 203.21.127.160
Looking up port of RPC 100005/1 on 203.21.127.160
VFS: Mounted root (NFS filesystem) readonly.
BJS: INITRD: 1
Freeing unused kernel memory: 32k init
BJS: opening console
BJS: console opended
BJS: trying /sbin/init
BJS: trying /etc/init
BJS: trying /bin/init
BJS: trying /bin/sh


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

  reply	other threads:[~1999-12-15  5:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15  5:55 linuxppc embedded boot problems Brian Kuschak
1999-12-15  5:22 ` Brendan Simon [this message]
1999-12-15 11:00   ` linuxppc-embedded: /bin/sh wont run from nfsroot Jim Chapman
1999-12-15 18:56     ` Alan Mimms
1999-12-15 20:09       ` Dan Malek
1999-12-15 21:27         ` Richard Hendricks
1999-12-15 21:37           ` Alan Mimms
1999-12-15 22:13             ` Dan Malek
1999-12-16 14:52             ` Richard Hendricks
1999-12-15 19:24     ` Dan Malek
1999-12-15 23:10       ` linuxppc-embedded: memory map question Brendan Simon
1999-12-16  9:37       ` linuxppc-embedded: programs wont run from nfsroot Brendan Simon
1999-12-15 22:40     ` linuxppc-embedded: /bin/sh " Brendan Simon
1999-12-16  0:24     ` Brendan Simon
1999-12-16  2:17       ` Brendan Simon
1999-12-15 19:11   ` Dan Malek
     [not found]   ` <ot66y035bv.fsf@thinktwice.zoftcorp.dk>
1999-12-15 22:29     ` Brendan Simon
1999-12-15 19:06 ` linuxppc embedded boot problems Dan Malek
1999-12-15 22:56   ` Brendan Simon
1999-12-16  5:03     ` Dan Malek

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=385725A3.A1C110DF@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.