From: Jarek Poplawski <jarkao2@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: Frans Pop <elendil@planet.nl>, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: large packet loss take2 2.6.31.x
Date: Fri, 27 Nov 2009 23:42:06 +0100 [thread overview]
Message-ID: <20091127224206.GA3350@ami.dom.local> (raw)
In-Reply-To: <81bfc67a0911271435g4106652bpe8c9ea07893d0ebd@mail.gmail.com>
On Fri, Nov 27, 2009 at 05:35:34PM -0500, Caleb Cushing wrote:
> > I doubt bisecting is a good idea with so unpredictable bug. First, you
> > should make sure it's not a hardware problem, so go back to the kernel
> > you trust most, and give it a really long try with a few recompilations
> > after slightly changing the config. Btw, I wonder if you tried e1000e
> > module parameters like IntMode=0 or 1.
>
> no, how do I set those?
modprobe -r e1000e
modprobe e1000e IntMode=0
Jarek P.
next prev parent reply other threads:[~2009-11-27 22:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 14:21 large packet loss take2 2.6.31.x Caleb Cushing
2009-10-31 18:44 ` 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 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 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-24 18:27 ` Jarek Poplawski
2009-11-25 14:06 ` Caleb Cushing
2009-11-25 14:06 ` Caleb Cushing
2009-11-25 16:47 ` Caleb Cushing
2009-11-25 16:47 ` Caleb Cushing
2009-11-25 19:11 ` Jarek Poplawski
2009-11-25 19:11 ` Jarek Poplawski
2009-11-27 18:07 ` Caleb Cushing
2009-11-27 21:36 ` Jarek Poplawski
2009-11-27 21:36 ` Jarek Poplawski
2009-11-27 22:35 ` Caleb Cushing
2009-11-27 22:35 ` Caleb Cushing
2009-11-27 22:42 ` Jarek Poplawski [this message]
2009-12-04 1:49 ` Caleb Cushing
2009-12-04 1:49 ` Caleb Cushing
2009-12-04 9:05 ` Jarek Poplawski
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
2009-12-04 23:47 ` Jarek Poplawski
2009-12-05 7:06 ` Caleb Cushing
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=20091127224206.GA3350@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 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.