Red Hat Bugzilla – Bug 103146
(NET 3C59X) Very slow FTP's
Last modified: 2013-07-02 22:14:52 EDT
Description of problem:
Using taroon-beta2. . .
Tranferring files from another UNIX server (does not matter; tried AIX,
RedhatAS, Redhat9) is really slow. Checked the network setting on both ends
using mii-tool and is reported and set correctly (100BaseTx-FD). Cabling has
Had this problem with Redhat9 [and after some searching found] and added the
following to /etc/rc.d/init.d/autofs which resolved the problem:
Tried the same on taroon-beta2, no luck; I get 100KB/s-180KB/s for any file
greater than 1MB.
Disconnected the machine from the network and connected another machine with the
same connect running Redhat9 with the localoptions set and getting
Removed the HD from taroon-beta2 machine and installed another drive [same
model] running Redhat9 with localoptions set and getting 700KB/s-957KB/s
consistantly; thus eliminating hardware [Dell Optiplex 240] and network as the
700KB/s to >900KB/s
Cisco switch is not reporting any errors which would indicate a negotiation problem.
What network driver?
The driver is 3c59x.
In Bug 102685 I reported such a problem with the NET 3C59X (3c905B, 3c905
cards). My example shows a very slow FTP. But I see with mii-tool a
autonegotiations problem on a 10 MB HUB. Now I have install
kernel-2.4.21-1.1931.2.411.ent from RHN, the problem is the same.
On Tarron-beta2 CDs there are kernel-2.4.21-1.1931.2.399.ent.
This machine is connected to a Cisco switch and we are not seeing any errors on
the port; errors that we'd see if there was a autonegotiation problem.
Both kernel-2.4.21-1.1931.2.399.ent and kernel-2.4.21-1.1931.2.411.ent behave
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.