From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754008AbbIROZO (ORCPT ); Fri, 18 Sep 2015 10:25:14 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:35546 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752595AbbIROZL (ORCPT ); Fri, 18 Sep 2015 10:25:11 -0400 Date: Fri, 18 Sep 2015 17:25:07 +0300 From: "Kirill A. Shutemov" To: Guenter Roeck Cc: "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Kirill A. Shutemov" , Andrew Morton , Mikael Starvik , Jesper Nilsson , Minchan Kim , linux-cris-kernel@axis.com Subject: Re: crisv32 runtime failure in -next due to 'page-flags: define behavior SL*B-related flags on compound pages' Message-ID: <20150918142507.GA30125@node.dhcp.inet.fi> References: <55FAEA67.9000102@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55FAEA67.9000102@roeck-us.net> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 17, 2015 at 09:29:27AM -0700, Guenter Roeck wrote: > Hi, > > my crisv32 qemu test fails with next-20150917 as follows. > > NET: Registered protocol family 16 > kernel BUG at mm/slab.c:1648! > Linux 4.3.0-rc1-next-20150917 #1 Wed Sep 16 23:56:59 PDT 2015 > Oops: 0000 > > [ register dump follows ] > > See http://server.roeck-us.net:8010/builders/qemu-crisv32-next/builds/83/steps/qemubuildcommand/logs/stdio > for a complete log. Is there a chance to get proper backtrace? -- Kirill A. Shutemov