Messages in this thread | | | Date | Fri, 18 Sep 2015 16:53:09 +0200 | From | Jesper Nilsson <> | Subject | Re: crisv32 runtime failure in -next due to 'page-flags: define behavior SL*B-related flags on compound pages' |
| |
On Fri, Sep 18, 2015 at 05:25:07PM +0300, Kirill A. Shutemov wrote: > 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?
Yes, it should be possible with CONFIG_KALLSYMS=y in the kconfig.
/^JN - Jesper Nilsson -- Jesper Nilsson -- jesper.nilsson@axis.com
| |