Date: Sun, 19 Jul 2009 15:22:10 +0200
From: Stephan von Krawczynski <skraw@ithnet.com>
To: David Rientjes <rientjes@google.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
       linux-kernel@vger.kernel.org, linux-mm@kvack.org,
       "Rafael J. Wysocki" <rjw@sisk.pl>,
       Justin Piszcz <jpiszcz@lucidpixels.com>
Subject: Re: What to do with this message (2.6.30.1) ?
Message-Id: <20090719152210.b0ec33d7.skraw@ithnet.com>
In-Reply-To: <20090718122311.9955e912.skraw@ithnet.com>
References: <20090713134621.124aa18e.skraw@ithnet.com>
	<4807377b0907132240g6f74c9cbnf1302d354a0e0a72@mail.gmail.com>
	<alpine.DEB.2.00.0907132247001.8784@chino.kir.corp.google.com>
	<20090715084754.36ff73bf.skraw@ithnet.com>
	<alpine.DEB.2.00.0907150115190.14393@chino.kir.corp.google.com>
	<20090715113740.334309dd.skraw@ithnet.com>
	<alpine.DEB.2.00.0907151323170.22582@chino.kir.corp.google.com>
	<20090718122311.9955e912.skraw@ithnet.com>
Organization: ith Kommunikationstechnik GmbH
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1443
Lines: 41

On Sat, 18 Jul 2009 12:23:11 +0200
Stephan von Krawczynski <skraw@ithnet.com> wrote:

> On Wed, 15 Jul 2009 13:24:08 -0700 (PDT)
> David Rientjes <rientjes@google.com> 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.
> 
> Todays' news is that 2.6.29.4 has exactly the same problem. I was able to
> reproduce it. Tonight I will check out 2.6.28.10.
> 
> -- 
> Regards,
> Stephan

I can reproduce the problem with 2.6.28.10.
Next in line is 2.6.27.26.
In the meantime I do believe that the problem really lies inside the e1000e
driver and not the surrounding kernel code.
Any other driver shows this behaviour in the same environment, escpecially
neither e1000 nor tg3.

-- 
Regards,
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/