public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	e1000-devel@lists.sourceforge.net, john.ronciak@intel.com,
	jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [E1000-devel] e1000 1sec latency problem
Date: Thu, 7 Feb 2008 23:24:11 +0100	[thread overview]
Message-ID: <20080207222411.GA1917@elf.ucw.cz> (raw)
In-Reply-To: <47AB4B2E.1030801@intel.com>

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.

Ok, e1000e seems to work for me.

In another email, you asked for lspci -vvvv of failing e1000
case. Should I still provide it?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-02-07 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 14:17 e1000 1sec latency problem Pavel Machek
2008-02-07 16:58 ` Max Krasnyansky
2008-02-07 17:25   ` [E1000-devel] " Kok, Auke
2008-02-07 18:06     ` Max Krasnyansky
2008-02-07 18:12       ` Kok, Auke
2008-02-07 18:30         ` Max Krasnyansky
2008-02-07 18:40           ` Kok, Auke
2008-02-07 18:55             ` Max Krasnyansky
2008-02-07 18:17 ` Kok, Auke
2008-02-07 22:24   ` Pavel Machek [this message]
2008-02-07 22:32     ` Kok, Auke
2008-02-07 22:37       ` Pavel Machek
2008-02-07 23:12         ` Kok, Auke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080207222411.GA1917@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox