linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: David Rientjes <rientjes@google.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: What to do with this message (2.6.30.1) ?
Date: Thu, 16 Jul 2009 11:14:15 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0907161113440.1116@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.0907151323170.22582@chino.kir.corp.google.com>



On Wed, 15 Jul 2009, David Rientjes wrote:

> On Wed, 15 Jul 2009, Stephan von Krawczynski wrote:
>
>>> If you have some additional time, it would also be helpful to get a
>>> bisection of when the problem started occurring (it appears to be sometime
>>> between 2.6.29 and 2.6.30).
>>
>> Do you know what version should definitely be not affected? I can check one
>> kernel version per day, can you name a list which versions to check out?
>>
>
> To my knowledge, this issue was never reported on 2.6.29, so that should
> be a sane starting point.
>

After talking to Stephan offline--

I am also using the Intel e1000e for my primary network interface to the
LAN, I suppose this is the culprit?  I have both options compiled in e1000
and e1000e as I have Intel 1Gbps PCI nics as well.. I am thinking back now
and before the introduction of e1000e I do not recall seeing any issues,
perhaps this is it?

Justin.



--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-07-16 15:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090713134621.124aa18e.skraw@ithnet.com>
2009-07-14  5:40 ` Jesse Brandeburg
2009-07-14  5:53   ` David Rientjes
2009-07-14  9:21     ` Stephan von Krawczynski
2009-07-15  6:47     ` Stephan von Krawczynski
2009-07-15  8:18       ` David Rientjes
2009-07-15  8:31         ` Justin Piszcz
2009-07-15  9:37         ` Stephan von Krawczynski
2009-07-15 20:24           ` David Rientjes
2009-07-16 15:14             ` Justin Piszcz [this message]
2009-07-16 16:44               ` What to do with this message (2.6.30.1) ? (happened again) Justin Piszcz
2009-07-18 10:23             ` What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-19 13:22               ` Stephan von Krawczynski
2009-07-20 12:15             ` Stephan von Krawczynski
2009-07-21 13:38             ` Stephan von Krawczynski
2009-07-22 11:53             ` Stephan von Krawczynski
2009-07-15  9:46         ` Stephan von Krawczynski
2009-07-15 20:22           ` David Rientjes
2009-07-16 13:19             ` Stephan von Krawczynski
2009-07-17  6:36             ` Stephan von Krawczynski
2009-07-14  9:16   ` Stephan von Krawczynski
2009-07-14 10:14   ` Stephan von Krawczynski

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=alpine.DEB.2.00.0907161113440.1116@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=rjw@sisk.pl \
    --cc=skraw@ithnet.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