Red Hat Bugzilla – Bug 210274
forcedeth driver faulty when on 1Gbps
Last modified: 2007-11-16 20:14:46 EST
Description of problem:
Linux workstations running on a fast network (1Gb) whilst using Landmark
SeisWorks or Shell 123DI have sluggish performance when interpreting a horizon
(interp take time to register and does not keep up with cursor clicks)
SeisWorks takes long time to scroll to a new line
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Seisworks project
2. Load horizons
3. Start interpreting
Interpreting is slow (up to 5-10 seconds to finish interpreting)
Intpreting should take well under a second to complete.
I disabled the on board NVidia NIC and installed an Intel EPro 1000 and
repeated the above tests and found no performance problems. When using a stock
xw9300 (i.e. using the forcedeth driver) on a 100Mbps port does not show any of
the above symptoms.
The hardware is HP xw9300 Workstation and a sysreport from a couple of days ago
Created attachment 138223 [details]
sysreport of an effected workstation
Created attachment 138290 [details]
Sysreport of the Stuttgart Workstation which does not have the problems
Attached is a sysreport from an engineering sample Sun Stuttgart workstation
which is similar in spec to the xw9300 including having onboard NVidia NICs.
Is this still a problem?
Yes this is still a problem on stock RHEL3 kernels. The problems only seem
apparent when doing *lots* of very small updates to a file on an NFS server
(Solaris in this case) when the card is operating in 1G mode. 100M is fine.
Applying the NVidia patches to take the driver to v0.60+ fixes the problem.
We are now rolling our own kernels to get around these problems.
I know EL5 uses 0.56 of the driver but I can't test this as the apps we run
don't work properly outside EL3.
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.
Nice, especially considering it was logged before EL3 went into maintenance