[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47AB4B2E.1030801@intel.com>
Date: Thu, 07 Feb 2008 10:17:18 -0800
From: "Kok, Auke" <auke-jan.h.kok@...el.com>
To: Pavel Machek <pavel@....cz>
CC: kernel list <linux-kernel@...r.kernel.org>,
e1000-devel@...ts.sourceforge.net, john.ronciak@...el.com,
jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com,
Jeff Garzik <jgarzik@...ox.com>
Subject: Re: [E1000-devel] e1000 1sec latency problem
Pavel Machek wrote:
> Hi!
>
> I have the famous e1000 latency problems:
>
> 64 bytes from 195.113.31.123: icmp_seq=68 ttl=56 time=351.9 ms
> 64 bytes from 195.113.31.123: icmp_seq=69 ttl=56 time=209.2 ms
> 64 bytes from 195.113.31.123: icmp_seq=70 ttl=56 time=1004.1 ms
> 64 bytes from 195.113.31.123: icmp_seq=71 ttl=56 time=308.9 ms
> 64 bytes from 195.113.31.123: icmp_seq=72 ttl=56 time=305.4 ms
> 64 bytes from 195.113.31.123: icmp_seq=73 ttl=56 time=9.8 ms
> 64 bytes from 195.113.31.123: icmp_seq=74 ttl=56 time=3.7 ms
>
> ...and they are still there in 2.6.25-git0. I had ethernet EEPROM
> checksum problems, which I fixed by the update, but problems are not
> gone.
pavel, start using "e1000e" instead - this driver replaces e1000 for all the
pci-express devices and has the infamous L1 ASPM disable patch to fix this issue.
make sure you have CONFIG_E1000E=m/y in your .config, otherwise the old e1000 code
will drive your card, and that driver does not have the fix.
BAH, this is a good example how Linus' patch can wreak havoc - a lot of people
will now not see fixes since they only go into e1000e, but people can unnoticed
now go and use e1000 for too long...
Auke
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists