[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090718122311.9955e912.skraw@ithnet.com>
Date: Sat, 18 Jul 2009 12:23:11 +0200
From: Stephan von Krawczynski <skraw@...net.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Jesse Brandeburg <jesse.brandeburg@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
"Rafael J. Wysocki" <rjw@...k.pl>,
Justin Piszcz <jpiszcz@...idpixels.com>
Subject: Re: What to do with this message (2.6.30.1) ?
On Wed, 15 Jul 2009 13:24:08 -0700 (PDT)
David Rientjes <rientjes@...gle.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
--
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