Jason Lunz writes:
> On Wed, Sep 18, 2002 at 9:53PM -0600, Richard Gooch wrote:
> > - the driver is reporting 10 Mbps rather than 100 Mbps. I've actually
> > measured eth0 and eth2 and these are delivering 100 Mbps
> i've noticed this too, and it's probably from all the mucking about
> I did trying to combine becker's method of forcing duplex/speed with
> the one in 2.4.19. That stuff is unrelated to the other,
> more-important merges I did that actually affect how well the card
> works. Jeff rightly pointed out that I should separate out chunks of
> the patch for submission, but I haven't had time.
Speaking of forcing speeds, is the following in /etc/modules.conf
supposed to work? Did I get the syntax right?
options sundance media="autosense","100mbps_fd","autosense"
> This card is still nowhere near working well, even with my patch. It
> silently drops many frames when simultaneously sending and receiving
> at high packet rates. It also locks up under load, and is reset in
> tx_timeout. This happens less frequently with my patch, but is not
> entirely gone.
Ah, that might explain why I've seen variations in TCP throughput from
eth0 <-> eth2 ranging from <8 MB/s to >11 MB/s.
About these lockups: are they fully recoverable by the driver, or does
the machine need attention to fix this? If the former, how long before
the driver recovers?