> > > > > Unable to handle kernel pointer dereference at virtual kernel address (null) > > > > > > This could I suppose be due to failed allocation where the caller > > > isn't expecting failure (or using SLAB_PANIC). > > > > > > Did you manage to test with the prink debugging patch for SLQB that > > > I sent for the power6 boot failure? I don't think I saw a reply from > > > you but maybe I missed it? > > > > Could you send me the debug patch as well? I can give it a quick run as well. > > This is what I had. It is only helpful for the power6 > failure where there was a problem in an allocation from > kmem_cache_create. It doesn't print anything out to the console. kmalloc_node returns 0x10 for the large allocation in init_section_page_cgroup(). The page allocator won't be able to satisfy this request since the requested order is larger than MAX_ORDER on our platform. Now we only need to figure out why the SLQB allocator returns 0x10 instead of NULL ;) -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
