On Mon, May 21 2007, Christoph Lameter wrote: > On Mon, 21 May 2007, Jens Axboe wrote: > > > I can test whatever you want tomorrow morning, it was 100% repeatable > > here. So which one, your patch or Hughs? > > This was an effect of me suggesting to switch off CONFIG_SLUB_DEBUG. If > you did not run without CONFIG_SLUB_DEBUG then you were not affected by > the problem. And the earlier case that you reported was a version of SLUB > that did not have the capability to switch off SLUB_DEBUG. > > Is there any way we can boot with "slub_debug" on the kernel command line > and get early printk output? Looks like an early failure that may have to > do with other kernel debug options being on (lockdep or so?)
Sure, I will try that as well. For reference, the last kernel tested on that box was HEAD 129a84de2347002f09721cda3155ccfd19fade40. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
