From: "Navin Boppuri" <nboppuri@trinetcommunication.com>
To: "Daris A Nevil" <dnevil@snmc.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: NFS problem- neighbout table overlow
Date: Wed, 27 Sep 2000 11:29:15 -0500 [thread overview]
Message-ID: <020e01bfc890$30ded920$4a1f76d8@washington> (raw)
In-Reply-To: 39D11274.A2AF2410@snmc.com
Hello everyone,
Thank you for all the help. All I needed to do was to change the setting of
SICR_ENET_CLKRT defined in commproc.h . The SCC2 was not configured
correctly. jonb@marel.is pointed this out to me. The ethernet now works
just fine.
Navin.
----- Original Message -----
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>
Sent: Tuesday, September 26, 2000 10:17 PM
Subject: Re: NFS problem- neighbout table overlow
>
> 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/
prev parent reply other threads:[~2000-09-27 16:29 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
2000-09-27 16:29 ` Navin Boppuri [this message]
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='020e01bfc890$30ded920$4a1f76d8@washington' \
--to=nboppuri@trinetcommunication.com \
--cc=dnevil@snmc.com \
--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 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).