On Thu, Jul 31, 2008 at 12:53 PM, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote: > On Thu, 2008-07-31 at 12:50 +0300, Tomas Winkler wrote: >> > There's ath5k in the stack trace but that, of course, doesn't >> > automatically mean it's at fault here. It could have been just the poor >> > bastard who was the next to allocate 4 KB with kmalloc() noticing the >> > corruption. >> > >> > Hope this helps! >> >> I've seen something similar with fragmentation code in iwl4965 but I >> can reproduce it only when using SLAB. With SLUB it didn't shown up. >> Does anyone know what is difference between SLAB and SLUB in this context.? > > Do you have CONFIG_SLUB_DEBUG_ON enabled? (Note: if you only have > CONFIG_SLUB_DEBUG enabled, then you need to enable debugging at run-time > by passing slub_debug to kernel command line.) Yes sure I've done that with slub_debug=FZPU Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
