Hello guys!
I've a very strange problem with my e1000: Sometimes it's very laggy,
sometimes it runs perfectly.
Sometimes I thought this could be a problem of the switch I'm connected
to, but this happens on every hardware tested after some time.
What happens very often is that I've very high changing ping times: from
10ms to 500ms.
I have the
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
in an IBM thinkpad t60
Kernel is Linux denkbrett 2.6.23.9 #2 SMP PREEMPT Tue Nov 27 17:22:15 CET 2007 i686 GNU/Linux
Konfiguration is
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
To give you some impressions:
[15:07] denkbrett:~% ping 81.14.211.141
PING 81.14.211.141 (81.14.211.141) 56(84) bytes of data.
64 bytes from 81.14.211.141: icmp_seq=1 ttl=245 time=50.4 ms
64 bytes from 81.14.211.141: icmp_seq=2 ttl=245 time=180 ms
64 bytes from 81.14.211.141: icmp_seq=3 ttl=245 time=276 ms
64 bytes from 81.14.211.141: icmp_seq=4 ttl=245 time=506 ms
64 bytes from 81.14.211.141: icmp_seq=5 ttl=245 time=280 ms
64 bytes from 81.14.211.141: icmp_seq=6 ttl=245 time=26.6 ms
64 bytes from 81.14.211.141: icmp_seq=7 ttl=245 time=27.2 ms
64 bytes from 81.14.211.141: icmp_seq=8 ttl=245 time=64.6 ms
64 bytes from 81.14.211.141: icmp_seq=9 ttl=245 time=90.1 ms
==> which should be always 27ms, another host next to me does
27ms continiously
64 bytes from 192.168.0.130: icmp_seq=85 ttl=64 time=0.534 ms
64 bytes from 192.168.0.130: icmp_seq=86 ttl=64 time=1.01 ms
64 bytes from 192.168.0.130: icmp_seq=87 ttl=64 time=0.519 ms
64 bytes from 192.168.0.130: icmp_seq=88 ttl=64 time=0.998 ms
64 bytes from 192.168.0.130: icmp_seq=89 ttl=64 time=0.483 ms
64 bytes from 192.168.0.130: icmp_seq=90 ttl=64 time=0.982 ms
64 bytes from 192.168.0.130: icmp_seq=91 ttl=64 time=0.448 ms
64 bytes from 192.168.0.130: icmp_seq=92 ttl=64 time=0.956 ms
64 bytes from 192.168.0.130: icmp_seq=93 ttl=64 time=0.424 ms
64 bytes from 192.168.0.130: icmp_seq=94 ttl=64 time=0.906 ms
=> which looks pretty good.
I'm not sure, what is the cause and I'm not 100% able to reproduce
this. Though I remember I think I remember that started with a kernel
around 2.6.16 or similar. Though iirc, after first I saw that problem,
downgraded and also saw that behaviour on the old kernel.
Any ideas on what could be wrong?
Sincerly
Nico
P.S.: Please CC me, not subscribed.
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
Attachment:
signature.asc
Description: Digital signature
