On Tue, 2010-03-16 at 13:21 +1100, Nick Piggin wrote: > > > Agreed (btw. Peter is there any way to turn lock debugging back on? > it's annoying when cpufreq hotplug code or something early breaks and > you have to reboot in order to do any testing). Not really, the only way to do that is to get the full system back into a known (zero) lock state and then fully reset the lockdep state. It might be possible using the freezer, but I haven't really looked at that, its usually simpler to simply fix the offending code or simply not build it in your kernel. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
