Re: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy'

[Guenter Roeck <linux@roeck-us.net>]

On Fri, Jun 24, 2016 at 04:50:22PM +0100, Mel Gorman wrote:
> On Fri, Jun 24, 2016 at 06:40:03AM -0700, Guenter Roeck wrote:
> > Hi Mel,
> > 
> > On 06/24/2016 01:39 AM, Mel Gorman wrote:
> > >On Thu, Jun 23, 2016 at 11:05:33PM -0700, Guenter Roeck wrote:
> > >>Hi,
> > >>
> > >>I see a lot of crashes with various architectures in next-20160623.
> > >>I bisected mips and sh; both bisect log point to the same patch.
> > >>Bisect log is attached. arm, ppc, and x86 images crash as well,
> > >>but I did not confirm if the same patch is the culprit there.
> > >>
> > >
> > >The series has been dropped. Due to conflicts with other patches, there
> > >were a few bugs introduced, one which potentially corrupted memory. Just
> > >to be sure though, what sort of workload crashed just in case I need to
> > >adjust the test coverage?
> > >
> > 
> > This is just a basic qemu boot test. No workload at all.
> 
> Ok, is there any chance you could test the mm-vmscan-node-lru-v8r12
> branch from git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> please?
> 
See the "testing" column at http://kerneltests.org/builders. "git describe"
is "v4.7-rc4-295-g572d768". Should be complete in a couple of hours.

Guenter