From: Brent Cook <bcook@bpointsys.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: root file system mounted via NFS - retry?
Date: Wed, 12 Apr 2006 07:50:31 -0500 [thread overview]
Message-ID: <200604120750.31421.bcook@bpointsys.com> (raw)
In-Reply-To: <443CF3F8.408@imagemap.com>
On Wednesday 12 April 2006 07:35, Randy Smith wrote:
> Hello,
>
> I have a general question regarding having a root file system mounted
> via NFS. Our system consists of a linux PC that acts as the NFS server
> and two embedded ppc boards running linux that mount their file systems
> via NFS. The problem is that the embedded boards boot much faster than
> the PC, and when they attempt to mount the root file system, the NFS
> server is not up yet. The embedded boards hang and it takes quite a
> long time before the watchdog timer reboots them. The next time round,
> they come up just fine.
> What I would like for them to do is keep trying until the NFS server
> appears and then continue to boot.
>
Sorry to try the obvious, but could you make the firmware's auto-boot timeout
longer? I know that u-boot and several others support this.
Also, you could try, instead of mounting root NFS directly from the kernel, an
initrd or embedding an initramfs that does the mount using a script. They you
could retry as much as you wanted without having to teach the kernel
anything.
Or, just hook up some GPIOs from your PC to the reset lines on those PPC's.
Then reset them once your PC is up.
Or rather than running the PPC kernel from flash, tftp it to RAM from your
PC - that way your PPCs can't even load the kernel until the PC is up
(assuming your firmware knows how to do this and handles faults gracefully.)
- Brent
next prev parent reply other threads:[~2006-04-12 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 12:35 root file system mounted via NFS - retry? Randy Smith
2006-04-12 12:40 ` Jarno Manninen
2006-04-12 12:50 ` Brent Cook [this message]
2006-04-12 14:01 ` Randy Smith
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=200604120750.31421.bcook@bpointsys.com \
--to=bcook@bpointsys.com \
--cc=linuxppc-embedded@ozlabs.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).