From: Thomas Dodd <ted@cypress.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Re: NFS in 2.4.8/9ac
Date: Wed, 19 Sep 2001 16:12:55 -0500 [thread overview]
Message-ID: <3BA90A57.6090803@cypress.com> (raw)
In-Reply-To: <3B8EA974.9060201@cypress.com>
Thomas Dodd wrote:
> I've suddenly started getting host not responding messages
> on NFS mounts. The mounts are from Solaris8 and HPUX-10.20.
> Other Solaris8 machines don't have this problem,
> and the machines serving the mounts are unloaded, and responsive.
> Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
> tulip0: MII transceiver #1 config 1000 status 782d advertising 01e1.
> eth0: Lite-On 82c168 PNIC rev 33 at 0xe400, 00:A0:CC:50:35:C2, IRQ 10
> (Tulip FA310TX card)
> NETDEV WATCHDOG: eth0: transmit timed out
> nfs: server nd not responding, still trying
Just a note: This is still a problem.
eventually I'll get a message about task slots.
It's still there through 2.4.9-ac10.
On a new Athlon 1.4 box, with a LNE100TX NIC
it's there with the default kernel from Red Hat Linux 7.1
(2.4.2-2.i686.rpm), and on a P4-1.8GHz with the same NIC.
The servers are Solaris8 and Solaris-2.6, Sparc machines, and the config
hasn't changed in over a year on the 2.6 boxes.
Anorthe system with RHL-6.2 (2.2.14-5 kernel and eepro100 NIC)
has no trouble talking to the servers.
What/how do I set debugging code on the 2.4 kernels to trak
down this problem? It makes NFS mounted home dirs unusable.
-Thomas
next prev parent reply other threads:[~2001-09-19 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 21:00 NFS in 2.4.8/9ac Thomas Dodd
2001-08-30 21:08 ` Alan Cox
2001-08-30 21:19 ` Thomas Dodd
2001-09-19 21:12 ` Thomas Dodd [this message]
2001-09-19 22:06 ` Alan Cox
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=3BA90A57.6090803@cypress.com \
--to=ted@cypress.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.