As addendum here is a short ping log: 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4093 ttl=64 time=0.581 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4094 ttl=64 time=18.2 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4095 ttl=64 time=186 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4096 ttl=64 time=0.565 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4097 ttl=64 time=542 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4098 ttl=64 time=0.870 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4099 ttl=64 time=792 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4100 ttl=64 time=1.52 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4101 ttl=64 time=188 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4102 ttl=64 time=1.11 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4103 ttl=64 time=648 ms 64 bytes from piwi.kc.de (192.168.2.28): icmp_seq=4104 ttl=64 time=112 ms
As you can see every second ping (at least every third) has times >> 100ms, in this log up to 648ms but they can even exceed 1000ms. I really need that interface to behave so any help would really be appreciated... Cheers nils Am 09.08.2010 00:25, schrieb Nils Faerber: > Hello! > I am more or less "trying" to use the e1000e driver on a Thinkpad X60. > Up to kernel 2.6.32 it worked quite fine. The next kernel I tried was > 2.6.34.1 and now 2.6.35 and there I find a very nasty issue which is > high packet latencies, varying. If I do e.g. a ping to machine on the > local net ping times are sometimes OK but most of the time > 300ms and > going up to 1000ms - which is inacceptable. > > The very nasty and for me kind of neck breaking side effect is that I > cannot boot my embedded boards over tftp from this e1000e machine > anymore which renders the notebook useless for my work :( The embedded > board's tftp client timeouts on almost every packet and gives up sooner > or later. > > Instead of the in-kernel e1000e driver I also tried the latest release > from your sf.net page e1000e-1.2.10.tar.gz. > > I also already tried different module parameters like disable the power > management, disabling MSI, etc. but no change. The only thing I know is > that the driver from 2.6.32 worked. > > If I can help to diagnose this let me know. > If you have a possible solution, even better ;) > > Thanks! > > PS: I am not subscribed to the e1000 list so in case you reply please > take my address into CC directly - thanks! > > Cheers > nils -- kernel concepts GbR Tel: +49-271-771091-12 Sieghuetter Hauptweg 48 Fax: +49-271-771091-19 D-57072 Siegen Mob: +49-176-21024535 http://www.kernelconcepts.de ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
