From: "Burján Gábor" <buga+dated+1013031263.c89449@elte.hu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17 NFS hangup
Date: Sun, 3 Feb 2002 22:34:22 +0100 [thread overview]
Message-ID: <20020203213422.GA703@csoma.elte.hu> (raw)
In-Reply-To: <20020203202251.GA22797@csoma.elte.hu> <shsbsf61di3.fsf@charged.uio.no>
In-Reply-To: <shsbsf61di3.fsf@charged.uio.no>
Hello,
On Sun, Feb 03, Trond Myklebust wrote:
> Nothing abnormal there or in your file. However, when you start
> getting 'server not responding' messages, and no tcpdump output it's
> usually a sign that the networking layer has given up on you. Any
> strange output from 'netstat -s'?
Output is here: http://www.csoma.elte.hu/~burjang/netstat-s-20020203.out
I think `1710 reassemblies required' may be strange after boot...
How can I figure out what causes this?
> It would be useful to know what networking card/driver combination you
> are using? Any firewalls/netfilter setups? Any special mount options?
eth0: PCnet/PCI II 79C970A at 0x1020, 08 00 5a f8 82 e7
pcnet32: pcnet32_private lp=c0591000 lp_dma_addr=0x80591000 assigned IRQ 15.
pcnet32.c:v1.25kf 17.11.2001 tsbogend@alpha.franken.de
(this card is an integrated AMD pcnet32 in a 43P-140)
There are no firewalls or packet filters. I didn't specify any
special mount options for nfs:
partvis:~$ cat /proc/mounts
/dev/root / nfs rw,v2,rsize=4096,wsize=4096,hard,udp,nolock,addr=157.181.150.31 0 0
proc /proc proc rw 0 0
partvis:~$
buga
next prev parent reply other threads:[~2002-02-03 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 20:22 2.4.17 NFS hangup Burjan Gabor
2002-02-03 21:06 ` Trond Myklebust
2002-02-03 21:34 ` Burján Gábor [this message]
2002-02-03 21:58 ` Alan Cox
2002-02-03 22:44 ` Trond Myklebust
2002-02-03 23:00 ` Burján Gábor
2002-02-04 13:21 ` Athanasius
2002-02-04 14:47 ` Athanasius
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=20020203213422.GA703@csoma.elte.hu \
--to=buga+dated+1013031263.c89449@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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