> No, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I > can back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad. You'll need to invert "good" and bad" for this. I.e. mark 2.6.15 as good, 2.6.16 as bad, and then as you test mark kernels with the bug as good, and ones without as bad. Try not to go insane while working in this inverted parallel universe :-) -Tony - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html