From: Wolfgang Denk <wd@denx.de>
To: Don Holmgren <djholm@fnal.gov>
Cc: "Stephan Ruettiger (r0337c)" <r0337c@email.sps.mot.com>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: root nfs boot problems
Date: Tue, 21 Mar 2000 20:28:53 +0100 [thread overview]
Message-ID: <200003211928.UAA20238@denx.local.net> (raw)
In-Reply-To: Your message of "Tue, 21 Mar 2000 11:28:31 CST." <Pine.SGI.3.95.1000321111628.2421C-100000@hppc.fnal.gov>
In message <Pine.SGI.3.95.1000321111628.2421C-100000@hppc.fnal.gov> you wrote:
>
> I don't believe the "neighbour table overflow" errors are the problem. I
> get them frequently but otherwise have success.
I have never seen such errors when the ethernet inrface is working
correclty.
> It looks like a problem on your nfs server. The "unable to get nfsd port
> number from server" and "unable to get mountd port number from server"
> messages indicate that at minimum, the portmapper is not running on your
> server. Perhaps mountd and/or nfsd are also not running.
Well, IMHO it's more likely that no packets were ever sent to the
ethernet at all. This type of problemppens for instance when the
Transmit Enable signal is not asserted.
It might be useful to check with a sniffer if the box is transmitting
at all...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Don't put off for tomorrow what you can do today, because if you
enjoy it today you can do it again tomorrow.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-21 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 15:05 root nfs boot problems Stephan Ruettiger (r0337c)
2000-03-21 17:28 ` Don Holmgren
2000-03-21 19:28 ` Wolfgang Denk [this message]
2000-03-21 21:55 ` Don Holmgren
2000-03-22 8:09 ` Stephan Ruettiger (r0337c)
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=200003211928.UAA20238@denx.local.net \
--to=wd@denx.de \
--cc=djholm@fnal.gov \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=r0337c@email.sps.mot.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).