Bugreport/Question

[Michael]

I have a Realtek 8139 (rev 16) card and have encountered some
strange problems with it I think are driver related.
I run linux (slackware with the 2.0.38 kernel) and as the uptime
goes up, the performance goes weird.. (cut from a ping seq follows)

PING bert.campus.luth.se (130.240.197.172): 56 data bytes
64 bytes from 130.240.197.172: icmp_seq=2 ttl=255 time=0.8 ms
64 bytes from 130.240.197.172: icmp_seq=0 ttl=255 time=2010.3 ms
64 bytes from 130.240.197.172: icmp_seq=1 ttl=255 time=1013.3 ms
64 bytes from 130.240.197.172: icmp_seq=3 ttl=255 time=600.5 ms
64 bytes from 130.240.197.172: icmp_seq=4 ttl=255 time=2840.2 ms
64 bytes from 130.240.197.172: icmp_seq=5 ttl=255 time=1840.3 ms
64 bytes from 130.240.197.172: icmp_seq=6 ttl=255 time=840.4 ms
64 bytes from 130.240.197.172: icmp_seq=8 ttl=255 time=16.8 ms
64 bytes from 130.240.197.172: icmp_seq=7 ttl=255 time=1021.7 ms
64 bytes from 130.240.197.172: icmp_seq=9 ttl=255 time=843.8 ms
64 bytes from 130.240.197.172: icmp_seq=11 ttl=255 time=0.8 ms
64 bytes from 130.240.197.172: icmp_seq=10 ttl=255 time=1012.1 ms
64 bytes from 130.240.197.172: icmp_seq=12 ttl=255 time=843.1 ms
64 bytes from 130.240.197.172: icmp_seq=14 ttl=255 time=0.8 ms
64 bytes from 130.240.197.172: icmp_seq=13 ttl=255 time=1001.0 ms
64 bytes from 130.240.197.172: icmp_seq=15 ttl=255 time=863.6 ms
64 bytes from 130.240.197.172: icmp_seq=17 ttl=255 time=0.7 ms
64 bytes from 130.240.197.172: icmp_seq=16 ttl=255 time=1002.2 ms

--- bert.campus.luth.se ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 0.7/875.1/2840.2 ms

The ping from this machine SHOULD be 0.7 all the time .. 
As the uptime goes up, ping goes up.. this was the ping after
something like 15 hours uptime.

Now.. think this is driver related, the card that's broken .. 
or what? If you want to know anything more about the config
of my system, just ask and I'll be happy to supply the details 
if I can .. 

I'm using the latest release driver found on your homepage, it's
the second one I tried.. I didn't really want to try to the test
driver since I didn't know what was unstable about nor if it would
solve my problem.

-- Michael Ahlner, hoping for some solution to this..

 

 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
 |  body of the mail, include only the text:
 |   unsubscribe this-list-name youraddress@wherever.org
 | You will be unsubscribed as speedily as possible.