On Fri, 2 Mar 2007 17:40:04 -0800 William Lee Irwin III <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 02, 2007 at 02:59:06PM -0800, Andrew Morton wrote: > > Somehow I don't believe that a person or organisation which is incapable of > > preparing even a simple testcase will be capable of fixing problems such as > > this without breaking things. > > My gut feeling is to agree, but I get nagging doubts when I try to > think of how to boil things like [major benchmarks whose names are > trademarked/copyrighted/etc. censored] down to simple testcases. Some > other things are obvious but require vast resources, like zillions of > disks fooling throttling/etc. heuristics of ancient downrev kernels. noooooooooo. You're approaching it from the wrong direction. Step 1 is to understand what is happening on the affected production system. Completely. Once that is fully understood then it is a relatively simple matter to concoct a test case which triggers the same failure mode. It is very hard to go the other way: to poke around with various stress tests which you think are doing something similar to what you think the application does in the hope that similar symptoms will trigger so you can then work out what the kernel is doing. yuk. - 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/
