linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: kd@flaga.is
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel 2.2.13 network problems
Date: Fri, 03 Dec 1999 11:16:19 +0100	[thread overview]
Message-ID: <199912031016.LAA29598@denx.local.net> (raw)
In-Reply-To: Your message of "Fri, 03 Dec 1999 10:04:06 GMT." <OF09A0544A.557A1BF7-ON0025683C.00368333@flaga.is>


In message <OF09A0544A.557A1BF7-ON0025683C.00368333@flaga.is> you write:
> 
> I just recently compiled the 2.2.13 kernel for our custom mpc823 board.
> Everything seem to work except that the network is really slow and
> frequently there are nfs timeouts, e.g.
> 
> nfs server x.x.x.x not responding
> nfs server x.x.x.x o.k.
> 
> Has anyone had similar experience and/or solution?

I *bet* your NFS server is on a PowerPC system running LinuxPPC.

I have the very same problem here with all kinds of embedded 8xx
systems (823, 850, 860) and all different kernel versions.

Move the NFS server to another  system,  for  instance  an  Intel  PC
running Linux, and you'll be perfectly fine.

I have no idea *why* this is happening...

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Bus error -- please leave by the rear door.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-03 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-03 10:04 Kernel 2.2.13 network problems kd
1999-12-03 10:16 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-03 10:31 kd
1999-12-03 16:48 ` Dan Malek
1999-12-03 17:25 kd
1999-12-03 17:42 ` Dan Malek

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=199912031016.LAA29598@denx.local.net \
    --to=wd@denx.de \
    --cc=kd@flaga.is \
    --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).