Linda Walsh wrote: > > Eric Sandeen wrote: >> Linda Walsh wrote: >>> David Chinner wrote: >>>> Filesystem bugs rarely hang systems hard like that - more likely is >>>> a hardware or driver problem. And neither of the lockdep reports >>>> below are likely to be responsible for a system wide, no-response >>>> hang. >>> --- >>> "Ish", the 32-bitter, has been the only hard-hanger. >> 4k stacks? > ---- > But but but...almost from the day they were introduced. And > these are more recent probs. Has stack usage increased for some reason, > :-(. I do have the option to detect stack-overflow turned on as well > -- guess it doesn't work so well?
Resource requirements grow over time, film at 11? :) the checker is a random thing, it checks only on interrupts; it won't always hit. you could try CONFIG_DEBUG_STACK_USAGE too, each thread prints max stack used when it exits, to see if you're getting close on normal usage. Or just use 8k. -Eric -- 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/
