public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Furlong <douglas.furlong@firebox.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Fri, 28 Nov 2003 09:37:09 +0000	[thread overview]
Message-ID: <1070012227.3615.7.camel@wibbit.firebox.com> (raw)
In-Reply-To: <200311280946.06755.jojo@automatix.de>

On Fri, 2003-11-28 at 08:46, Juergen Sauer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Am Donnerstag, 27. November 2003 13:00 schrieb Douglas Furlong:
> > Good day all.
> >=20
> > I am running in to excessive amounts of NFS errors as below.
> >=20
> > kernel: nfs: server neon not responding, still trying
> > kernel: nfs: server neon OK
> >=20
> > I was hoping that some of you may be able to provide me with some
> > assistance.
>=20
> Hight Doug, Hi Trond,
>=20
> Is there any NVIDIA Stuff in the client/server ?
> The Nvidia drivers vor the graphics and the nvidia netdrivers
> are broken for 2.4.[20|21|22] !
> The nv.o module for Xfree86 breaks IMHO the NFS.
>=20
> I sent a bug report to the Nvidia maintainers.
>=20
> Refer to the NFS Server not responding threads in the last month.

Morning J=FCrgen

I do indeed have an nvidia card in the machine which is a nVidia
Corporation NV11 [GeForce2 MX/MX 400] (rev b2).

However on an lsmod the nv.o driver is not being loaded (the machine
goes to run level 3 not 5.

Am I right in saying this should mean the problem does not exist?

I will go and have a look at those archives (only been on the list for a
week).

Doug



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-11-28  9:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07   ` Douglas Furlong
2003-11-27 20:02     ` Trond Myklebust
2003-11-28  8:46 ` Juergen Sauer
2003-11-28  9:37   ` Douglas Furlong [this message]
2003-11-28 10:11     ` Juergen Sauer
2003-11-28 10:48       ` Douglas Furlong
2003-11-28 12:28         ` Bogdan Costescu
2003-11-28 16:56           ` Trond Myklebust
2003-11-28 18:43             ` Bogdan Costescu
2003-12-02 14:37             ` Douglas Furlong
2003-12-02 15:37               ` Trond Myklebust
2003-12-04 17:17                 ` Steve Dickson
2003-12-04 17:37             ` Steve Dickson
2003-12-04 18:39               ` Trond Myklebust
2003-12-04 19:11                 ` Steve Dickson
2003-12-04 20:55                   ` seth vidal
2003-12-04 21:24                     ` Steve Dickson
2003-12-05  2:53                       ` Kyle Rose
2003-12-09 19:47                         ` Steve Dickson
2003-12-09 20:09                           ` Kyle Rose
2003-12-05 15:50                 ` Bogdan Costescu
2003-11-30 20:01           ` seth vidal
2003-12-01 10:58             ` Bogdan Costescu
2003-11-28 12:36       ` Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2009-05-16  0:57 nfs: " Jerome Walters

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=1070012227.3615.7.camel@wibbit.firebox.com \
    --to=douglas.furlong@firebox.com \
    --cc=nfs@lists.sourceforge.net \
    /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