From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751048AbcFXIjZ (ORCPT ); Fri, 24 Jun 2016 04:39:25 -0400 Received: from outbound-smtp08.blacknight.com ([46.22.139.13]:53950 "EHLO outbound-smtp08.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750943AbcFXIjX (ORCPT ); Fri, 24 Jun 2016 04:39:23 -0400 Date: Fri, 24 Jun 2016 09:39:14 +0100 From: Mel Gorman To: Guenter Roeck Cc: Andrew Morton , linux-kernel@vger.kernel.org, Vlastimil Babka Subject: Re: Crashes in -next due to 'mm, page_alloc: remove fair zone allocation policy' Message-ID: <20160624083914.GD1868@techsingularity.net> References: <20160624060533.GA9507@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20160624060533.GA9507@roeck-us.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Mel Gorman SUSE Labs