From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Mohammad Sadegh Sadri" <mamsadegh@hotmail.com>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: ML403 2.6 kernel, root file system on NFS, stops after freeing unused kernel memory
Date: Wed, 23 May 2007 10:58:28 -0600 [thread overview]
Message-ID: <fa686aa40705230958u7c37dbe8m5ee149082fdb52d2@mail.gmail.com> (raw)
In-Reply-To: <BAY115-W12CE664522EEB409218C3FB2350@phx.gbl>
On 5/23/07, Mohammad Sadegh Sadri <mamsadegh@hotmail.com> wrote:
>
> Hi all
>
> I have studied the disscussion here mainly by Mirek32 (I think this was the name) but unfortunately the disscussion is finished without any suitable answer and solution.
>
> the 2.6 kernel comes up on ml403 with no problem, it gets an IP address from my DHCP and mounts the root file system from my NFS server , all of these are ok.
>
> Unfortunately , after "freeing unused kernel memory ", init , console stops working however the board is alive because it answers all of my pings correctly. I tried to make a telnet connection to the board with no success. ( I'm using ELDK 4.0)
>
> any suggestions what is happening here?
Is there a /dev/console node?
try booting with init=/bin/sh to see if you get a console.
Your /etc/inittab might not be starting a getty on the console device.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-05-23 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 16:06 ML403 2.6 kernel, root file system on NFS, stops after freeing unused kernel memory Mohammad Sadegh Sadri
2007-05-23 16:58 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-26 10:05 Mohammad Sadegh Sadri
2007-05-26 13:46 Mohammad Sadegh Sadri
2007-05-27 17:34 ` Clemens Koller
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=fa686aa40705230958u7c37dbe8m5ee149082fdb52d2@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mamsadegh@hotmail.com \
/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).