From: Matej Kupljen <matej.kupljen@ultra.si>
To: Edward Jubenville <edjubenville@adelphia.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Slow boot with NFS, server not responding
Date: Wed, 26 Jul 2006 11:03:19 +0200 [thread overview]
Message-ID: <1153904599.7133.21.camel@localhost.localdomain> (raw)
In-Reply-To: <GPECLCIGPLHEOMGPMCPAOEIIDNAA.edjubenville@adelphia.net>
Hi
> I am having trouble booting the kernel with a root file system over NFS.
> Once the kernel has mounted the file system, it cycles through this pair of
> messages, endlessly:
>
> nfs: server 192.168.0.39 not responding, still trying
> nfs: server 192.168.0.39 OK
We had the same problems on a DBAU1200 board, because that board uses
smc91c111 chip, which has small RX buffers, and a lot of RX overruns
happened.
We solved this by specifying additional kernel command line parameter:
nfsroot=,tcp
which specifies that for the NFS TCP should be used instead of UDP.
I hope this helps.
BR,
Matej
next prev parent reply other threads:[~2006-07-26 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:27 Slow boot with NFS, server not responding Edward Jubenville
2006-07-25 17:10 ` Andrei Konovalov
2006-07-26 19:55 ` Edward Jubenville
2006-07-26 9:03 ` Matej Kupljen [this message]
2006-07-26 9:52 ` Kalle Pokki
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=1153904599.7133.21.camel@localhost.localdomain \
--to=matej.kupljen@ultra.si \
--cc=edjubenville@adelphia.net \
--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).