tulip/nfs problem

Thomas E. Dodd /CSDC (ted@cypress.com)
Wed, 01 Dec 1999 15:10:45 -0600


I was running an upgraded RH6.1 system
with a RedHat 2.2.12-20 kernel
and a Realtek PCI-NE2k NIC.

Everything worked well, but the NIC
was terible.

So I go a NetGear card, and configured
the tulip driver from RedHAt.

I started getting nfs errors.
from the log:

Dec 1 14:39:59 tedpc kernel: nfs: server pr not responding, still
trying
Dec 1 14:40:02 tedpc kernel: nfs: task 1868 can't get a request slot
Dec 1 14:40:12 tedpc kernel: nfs: server pr OK
nfs: server pr not responding, still trying
Dec 1 14:40:13 tedpc kernel: nfs: server pr OK
Dec 1 14:40:23 tedpc kernel: nfs: server pr not responding, still
trying
nfs: server pr OK
Dec 1 14:40:23 tedpc kernel: nfs: server pr OK
nfs: server pr not responding, still trying
Dec 1 14:40:43 tedpc kernel: nfs: server pr not responding, still
trying
nfs: server pr OK
Dec 1 14:40:44 tedpc kernel: nfs: server pr OK
Dec 1 14:40:44 tedpc PAM_pwdb[909]: (login) session closed for user
ted
nfs: server pr not responding, still trying
Dec 1 14:40:55 tedpc kernel: nfs: server pr not responding, still
trying
Dec 1 14:41:06 tedpc kernel: nfs: task 1885 can't get a request slot
nfs: task 1886 can't get a request slot
Dec 1 14:41:16 tedpc kernel: nfs: task 1886 can't get a request slot
nfs: server pr OK
nfs: server pr OK
Dec 1 14:41:43 tedpc kernel: nfs: server pr OK
nfs: server pr OK
Dec 1 14:41:43 tedpc last message repeated 2 times

I have nfs mounted home directories. It makes using X horrid.
The system freezes untill nfs get OK for the errors.
The reason for the new NIC was to get *BETTER* nfs performance
not worse.

tedpc is my Athlon running linux
pr is a Sparc20 running Solaris 2.6

I never had these problems with the old NIC.

I've also tried the 2.2.13-0.4 kernel from Rawhide
with the same results.

-Thomas

please CC: ted@cypress.com
I've been out of town and have ~5000
messages in from the kernel list to
go through :(

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/