> It's more like "lets warn about it and fix the problems when we find > some."
It is already known there are lots of problems. I won't repeat them because I already wrote too much about them. Feel free to read back in the thread. Now if all the known problems are fixed and only some hard to know hidden ones remain it might make sense to enable (but even then a little dubious considering how important error handling robustness is), but not at the current state (at least with the full default backtraces) > Btw, how is this different from how the lockdep patches went > in? lockdep is clearly a "only enable if you're developing the kernel" feature (just alone because of its overhead and other problems). So side effects etc. are expected. Softlockup previously (before this patch) was a "can be always safely enabled" feature. Now Ingo's latest unreleased version with single line messages might be actually ok if he turns off the backtraces by default. Unfortunately I wasn't able to find out so far if he has done that or not, he always cuts away these parts of the emails. -Andi -- 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/
