netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Frans Pop <elendil@planet.nl>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: large packet loss take2 2.6.31.x
Date: Fri, 4 Dec 2009 09:05:25 +0000	[thread overview]
Message-ID: <20091204090524.GB6478@ff.dom.local> (raw)
In-Reply-To: <81bfc67a0912031749y15faed66s9c8a924684c97a19@mail.gmail.com>

On Thu, Dec 03, 2009 at 08:49:17PM -0500, Caleb Cushing wrote:
> >
> > modprobe -r e1000e
> > modprobe e1000e IntMode=0
> >
> > Jarek P.
> >
> tested on kernel behaving properly no change. what do these modes do?

e1000e by default uses MSI-X interrupts if possible, which are most
modern. If there are some problems IntMode lets us try older types,
so I rather meant it for the misbehaving kernel.

> 
> I've installed a 10/100 linksys nic into my system. it appears to be
> working fine on a bad kernel (2.6.32-final tested and for sure
> verified). I've only tested it once though. my laptop died so direct
> connection between that won't work. can I test between these 2 nics?
> (suppose no real reason why not) but what should I proceed with at
> this point?

If you have it fixed easily with another nic you should first
reconsider if this debugging is worth of your time. Of course it's
could be very useful for the kernel (unless it's a hardware fault),
but on the other hand this is a popular nic, tested by many people.

Then, if you find time for such testing, I'd suggest to try mainly
2.6.32 - I'm not sure if you tried it with e1000e. So if after longer
testing both linksys and e1000e you find only the latter has problems
I think you should open the new report in bugzilla for e1000e and
submit things like: dmesg, .config, lspci -v from 2.6.32, and if
possible the same things from the last kernel which didn't have these
problems. Add some references to previous attempts in bugzilla and
this thread. (Btw, any reproducible tests should be fine.)

Jarek P.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev

  reply	other threads:[~2009-12-04  9:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <81bfc67a0910310721p21046931o9b512cfd0a8a7acb@mail.gmail.com>
2009-10-31 18:44 ` large packet loss take2 2.6.31.x Frans Pop
2009-11-11 20:19   ` Caleb Cushing
2009-11-11 21:47     ` Andi Kleen
2009-11-11 22:05       ` Frans Pop
2009-11-11 22:48         ` Caleb Cushing
2009-11-12 11:38           ` Jarek Poplawski
2009-11-12 13:46             ` Caleb Cushing
2009-11-12 19:04               ` Jarek Poplawski
2009-11-12 21:47                 ` Jarek Poplawski
2009-11-13 16:25                 ` Caleb Cushing
2009-11-13 17:21                   ` Caleb Cushing
2009-11-13 21:16                   ` Jarek Poplawski
2009-11-18  9:59                     ` Caleb Cushing
2009-11-18 10:00                       ` Caleb Cushing
2009-11-18 13:51                       ` Jarek Poplawski
2009-11-18 18:21                         ` Caleb Cushing
2009-11-18 20:10                           ` Jarek Poplawski
2009-11-18 22:38                             ` Jarek Poplawski
2009-11-22 19:35                               ` Caleb Cushing
2009-11-22 20:50                                 ` Jarek Poplawski
2009-11-24  6:17                                   ` Caleb Cushing
2009-11-24 11:19                                     ` Jarek Poplawski
2009-11-24 13:46                                       ` Jarek Poplawski
2009-11-24 15:57                                       ` [E1000-devel] " Allan, Bruce W
2009-11-24 18:27                                         ` Jarek Poplawski
2009-11-25 14:06                                       ` Caleb Cushing
2009-11-25 16:47                                         ` Caleb Cushing
2009-11-25 19:11                                         ` Jarek Poplawski
2009-11-27 18:07                                           ` Caleb Cushing
2009-11-27 21:36                                             ` Jarek Poplawski
2009-11-27 22:35                                               ` Caleb Cushing
2009-11-27 22:42                                                 ` Jarek Poplawski
2009-12-04  1:49                                                   ` Caleb Cushing
2009-12-04  9:05                                                     ` Jarek Poplawski [this message]
2009-12-04 18:28                                                       ` Caleb Cushing
2009-12-04 20:44                                                         ` Jarek Poplawski
2009-12-04 23:07                                                           ` Caleb Cushing
2009-12-04 23:47                                                             ` Jarek Poplawski
2009-12-05  7:06                                                               ` Caleb Cushing
2009-12-05  7:29                                                                 ` Caleb Cushing
2009-12-05 13:57                                                                 ` Jarek Poplawski

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=20091204090524.GB6478@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=elendil@planet.nl \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xenoterracide@gmail.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;
as well as URLs for NNTP newsgroup(s).