From: Mel Gorman <mgorman@techsingularity.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy'
Date: Fri, 24 Jun 2016 16:50:22 +0100 [thread overview]
Message-ID: <20160624155022.GF1868@techsingularity.net> (raw)
In-Reply-To: <576D3833.7020608@roeck-us.net>
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?
If not, I'll work on replicating it some time next week before the
series is reposted.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2016-06-24 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 6:05 Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy' Guenter Roeck
2016-06-24 8:39 ` Mel Gorman
2016-06-24 13:40 ` Guenter Roeck
2016-06-24 15:50 ` Mel Gorman [this message]
2016-06-24 16:46 ` Guenter Roeck
2016-06-24 18:13 ` Mel Gorman
2016-06-24 20:15 ` Guenter Roeck
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=20160624155022.GF1868@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.