From: Daris A Nevil <dnevil@snmc.com>
To: "Dan A. Dickey" <ddickey@charter.net>
Cc: Navin Boppuri <nboppuri@trinetcommunication.com>,
linuxppc-embedded@lists.linuxppc.org,
greyham@research.canon.com.au
Subject: Re: NFS problem- neighbout table overlow
Date: Tue, 26 Sep 2000 16:17:41 -0500 [thread overview]
Message-ID: <39D11274.A2AF2410@snmc.com> (raw)
In-Reply-To: 39D10BB4.D6F1897@charter.net
When you see the "neighbour table overflow" message it simply means that
NFS cannot communicate with the server. It could mean anything from a
bad cable, invalid IP setup, bad driver, incorrect driver setup, etc.
It really means that you are not successfully transporting IP packets.
Regards,
Daris Nevil
"Dan A. Dickey" wrote:
>
> Navin Boppuri wrote:
> > Hello Everyone,
> > I have been having problems with my custom board. The NFS mount does
> > not
> > work. The NFS request does not actually go the server. I dont see any
> > packets coming to the server from this board. I did have some ring
> > dump
> > problems. There were some errors in Port A setting which I fixed and
> > that is
> > gone now. By I still see 'neighbour table overflow' messages. What can
> > be
> > the problem?
>
> Navin,
> I can't say that I remember for sure - but I seem to recall
> this as being a problem in the Linux NFS implementation.
> Check through the linux-kernel archives for messages regarding
> the neighbour table overflow. There may be a suggestion
> on how to solve this. I know I remember something about this...
> -Dan
>
--
Daris A Nevil
Simple Network Magic Corporation
401 Kentucky Lane
McKinney, TX 75069
214-793-7757
dnevil@snmc.com
www.snmc.com
quickstack.com
qslinux.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-26 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 20:20 NFS problem- neighbout table overlow Navin Boppuri
2000-09-26 20:48 ` Dan A. Dickey
2000-09-26 21:17 ` Daris A Nevil [this message]
2000-09-27 16:29 ` Navin Boppuri
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=39D11274.A2AF2410@snmc.com \
--to=dnevil@snmc.com \
--cc=ddickey@charter.net \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nboppuri@trinetcommunication.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).