From: Marcus Blomenkamp <Marcus.Blomenkamp@epost.de>
To: linux-kernel@vger.kernel.org
Subject: r8169 GigE driver problem, locks up 2.4.23 NFS subsystem
Date: Sat, 13 Dec 2003 13:00:05 +0100 [thread overview]
Message-ID: <200312131300.05847.Marcus.Blomenkamp@epost.de> (raw)
Hi all.
Since ugrading from a realtek-8139 based nic to a realtek-6139 gigabit one i
am experiencing strange network problems. Particularly it locks up the NFS
subsystem on writing to remote files.
I tried to narrow it down using several TCP/UDP traffic tools such as
'netpipe' and 'netcat' and different kernel r8169 driver versions.
I restricted the network to a single 100mbit crossover cable between a machine
with said gig-nic and a file server which has not been modified yet.
File server: 'kartoffel', RTL-8139, linux-2.4.20
Client machine: 'zwiebel', RTL-8169S, linux-2.4.23-pre9, linux-2.6.0-test11
I tried 2.4.23-pre9 and 2.6.0-test11 vanilla drivers and a special realtek
supplied version for linux-2.4. With respect to basic TCP and UDP transfer
their behaviour was identical. However 2.6 NFS subsystem was able to recover
from the network stalls, while 2.4 NFS did not release processes from 'D'
state.
My suspicion is that something related to UDP datagram to IP-over-ethernet
frame fragmentation is broken. TCP transfers in both directions work fine
while UDP transmissions over a specific datagram size stall after sending a
few k.
These objections manifest into NFS running fine over TCP and running fine over
UDP with wsize<=4096, while standard NFS mount option wsize=8192 fails.
If anyone is interested, i have dmesg output and ethereal log files handy.
Best regards, Marcus
next reply other threads:[~2003-12-13 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 12:00 Marcus Blomenkamp [this message]
2003-12-14 2:02 ` Jeff Garzik
2003-12-13 13:01 Francois Romieu
2003-12-13 13:54 ` Marcus Blomenkamp
[not found] ` <20031214144055.A4664@electric-eye.fr.zoreil.com>
2003-12-15 10:24 ` Marcus Blomenkamp
2003-12-15 18:58 ` Francois Romieu
2003-12-18 0:45 ` Francois Romieu
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=200312131300.05847.Marcus.Blomenkamp@epost.de \
--to=marcus.blomenkamp@epost.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome