From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Minchan Kim <minchan@kernel.org>,
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'
Date: Fri, 18 Sep 2015 17:25:07 +0300 [thread overview]
Message-ID: <20150918142507.GA30125@node.dhcp.inet.fi> (raw)
In-Reply-To: <55FAEA67.9000102@roeck-us.net>
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
next prev parent reply other threads:[~2015-09-18 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 16:29 crisv32 runtime failure in -next due to 'page-flags: define behavior SL*B-related flags on compound pages' Guenter Roeck
2015-09-18 14:25 ` Kirill A. Shutemov [this message]
2015-09-18 14:53 ` Jesper Nilsson
2015-09-18 15:13 ` Guenter Roeck
2015-09-21 15:34 ` Kirill A. Shutemov
2015-09-22 1:17 ` Guenter Roeck
2015-09-22 12:03 ` Kirill A. Shutemov
2015-09-22 12:19 ` Mikael Starvik
2015-09-22 12:50 ` Hans-Peter Nilsson
2015-09-22 13:27 ` Kirill A. Shutemov
2015-09-22 13:57 ` Hans-Peter Nilsson
2015-09-22 15:18 ` Paul E. McKenney
2015-09-22 15:31 ` Kirill A. Shutemov
2015-09-22 15:40 ` Paul E. McKenney
2015-09-23 10:53 ` Kirill A. Shutemov
2015-09-23 15:02 ` Guenter Roeck
2015-09-24 4:45 ` Paul E. McKenney
2015-09-22 16:16 ` Hans-Peter Nilsson
2015-09-22 16:39 ` Paul E. McKenney
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=20150918142507.GA30125@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=jesper.nilsson@axis.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=minchan@kernel.org \
--cc=starvik@axis.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).