On Tue, 7 May 2013, Tony Lindgren wrote: > OK got it narrowed down to CONFIG_DEBUG_SPINLOCK=y causing the problem > with commit 8a965b3b. Ain't nothing like bisecting and booting and then > diffing .config files on top of that. > > > Without reverting 8a965b3b I'm getting:
The patch (commit 8a965b3baa89ffedc73c0fbc750006c631012ced) merely changed the sequence of slab creation to address an issue in SLAB. Hmmm.. But if KMALLOC_SHIFT_LOW is higher than 6 or 7 then the creation of the non-power of two slab could be skipped as a result of the patch. But we should not need them in those cases. Can I see the kernel config? What is the value of KMALLOC_SHIFT_LOW? Can you figure out which kernel slab the function is trying to access? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/