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: Sat, 5 Dec 2009 00:47:57 +0100 [thread overview]
Message-ID: <20091204234756.GA3517@ami.dom.local> (raw)
In-Reply-To: <81bfc67a0912041507k6ef497f9w7b9294c90012e1a1@mail.gmail.com>
On Fri, Dec 04, 2009 at 06:07:42PM -0500, Caleb Cushing wrote:
> > So, again, if you're willing to debug this, the new bugzilla report
> > seems reasonable to me, plus maybe some notice to this #11998 too.
>
> I will later today. I'm thinking since I now have 2 active nics...
> would hooking the 1 card directly to the other and then running the
> tests be helpful? (I wish this mobo had a 3rd pci slot because I'd
> have put a 3rd card in so I can connect to the net at the same time.
I guess, you should better wait with new tests for some assistance
from e1000e maintainers - it seems they might be interested in some
specific dumps and registers - like in this #11998 case.
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
next prev parent reply other threads:[~2009-12-04 23:47 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
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 [this message]
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=20091204234756.GA3517@ami.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).