[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0907161113440.1116@p34.internal.lan>
Date: Thu, 16 Jul 2009 11:14:15 -0400 (EDT)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: David Rientjes <rientjes@...gle.com>
cc: Stephan von Krawczynski <skraw@...net.com>,
Jesse Brandeburg <jesse.brandeburg@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: What to do with this message (2.6.30.1) ?
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists