On Fri, Mar 4, 2016 at 1:44 PM, Dave Airlie <airl...@gmail.com> wrote: > > ------------[ cut here ]------------ > kernel BUG at mm/slub.c:3625!
Yeah, not a lot to go on. That case should probably use
VM_BUG_ON_PAGE() to five a little more information, but on the whole
it's does look like just major memory corruption.
The call trace doesn't really strike me as a likely source of the bug.
Enabling slub debugging does seem to be the best idea.
Linus
