From: Pavel Machek <pavel@ucw.cz>
To: 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,
auke-jan.h.kok@intel.com
Subject: e1000 1sec latency problem
Date: Thu, 7 Feb 2008 15:17:18 +0100 [thread overview]
Message-ID: <20080207141718.GA2030@elf.ucw.cz> (raw)
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.
irqpoll helps.
nosmp (which implies XT-PIC is being used) does not help.
16: 1925 0 IO-APIC-fasteoi ahci, yenta, uhci_hcd:usb2, eth0
Booting kernel with nosmp/ no yenta, no usb does not help.
Hmm, as expected, interrupt load on ahci (find /) makes latencies go
away.
It should be easily reproducible on x60 with latest bios, it is 100%
reproducible for me...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2008-02-07 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 14:17 Pavel Machek [this message]
2008-02-07 16:58 ` e1000 1sec latency problem 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
2008-02-07 22:32 ` Kok, Auke
2008-02-07 22:37 ` Pavel Machek
2008-02-07 23:12 ` Kok, Auke
-- strict thread matches above, loose matches on Subject: below --
2008-02-07 22:31 Martin Rogge
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=20080207141718.GA2030@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.