mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: vatsa@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	e1000-devel@lists.sourceforge.net, varunc@linux.vnet.ibm.com,
	jbarnes@virtuousgeek.org, greg@kroah.com,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: Strange problem with e1000 driver - ping packet loss
Date: Thu, 19 Jun 2008 22:25:17 +0200	[thread overview]
Message-ID: <19f34abd0806191325s4c10660dt8da146ad2ef4e63b@mail.gmail.com> (raw)
In-Reply-To: <485A9678.5000707@shaw.ca>

On 6/19/08, Robert Hancock <hancockr@shaw.ca> wrote:
> Srivatsa Vaddagiri wrote:
>
> > Hi,
> >        I happened to look at a system which was exhibiting poor ping
> > performance with e1000 driver (in 2.6.25) and had some questions regarding
> that.
> >
> > Ping test was done between the system and a laptop, which were connected
> > using a straight ethernet cable. Ping reported round trip times running
> > into seconds (!) and also packet loss.
> >
> > Upon some investigation, I found that the interrupt count field in
> > /proc/interrupts (associated with eth1) is not incrementing as fast as
> > it should. Moreover eth1 interrupt line is shared with the hard disk
> > interrupt (ata_piix) as below:

Just FYI, it seems that more people have the same (?) problem:

http://www.ussg.iu.edu/hypermail/linux/kernel/0806.2/0499.html

It might be worth joining forces to fight down the bug once and for
all if it's still not fixed after one and a half years? Sorry, I
really meant error instead of bug.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-06-19 20:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.QBOn2aWyqGnBJJticG4h09lpxD0@ifi.uio.no>
2008-06-19 17:25 ` Robert Hancock
2008-06-19 20:25   ` Vegard Nossum [this message]
2008-06-20 12:30   ` Srivatsa Vaddagiri
2008-06-20 14:40     ` Robert Hancock
2008-06-25 14:32       ` Srivatsa Vaddagiri
2008-06-25 18:09         ` [E1000-devel] " hong zhang
     [not found]     ` <alpine.LFD.1.10.0806251455500.3014@localhost.localdomain>
2008-06-25 19:04       ` Len Brown
2008-06-26 13:37         ` Srivatsa Vaddagiri
2008-06-24  4:33   ` Varun Chandramohan
2008-06-18 12:52 Srivatsa Vaddagiri
2008-06-18 19:18 ` Brandeburg, Jesse
2008-06-19  3:45   ` Srivatsa Vaddagiri

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=19f34abd0806191325s4c10660dt8da146ad2ef4e63b@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=hancockr@shaw.ca \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=varunc@linux.vnet.ibm.com \
    --cc=vatsa@linux.vnet.ibm.com \
    /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

all inboxes | Powered by JetHome®