On Mon, 6 Apr 2009, Trenton D. Adams wrote: > > > > This went through bisection, but looking at the email log, I tend to > > suspect that maybe Trenton marked some versions good even though they > > weren't (because they got versions numbers from v2.6.27), and didn't > > realize that that messes up bisection in a big way. > > Is it appropriate for me to respond to these things? Yes. I added you to the cc exactly because it was hard for me to judge from the email discussion that is linked to in the regression list whether you actually _did_ mark some versions good because of confusion about the version numbering. That would certainly explain why bisection didn't seem to work. But it's not the _only_ reason bisection doesn't work. Sometimes you can be as careful as possible, but if it's a bug that is even _slightly_ flaky (timing-dependencies etc), and the bisection marked something good that shouldn't have been (or vice versa, but that's unusual), then the bisection end result won't be right. So you may well have done everything right, and I'm not trying to blame you. I just was hoping that maybe that confusion would explain why the bisection didn't seem to pinpoint anything sane.. > I was wondering about that. Someone had mentioned that I should trust > the bisect, even when it takes me into "other versions", and it was > taking me through 2.6.27, which I thought was just really weird. > Would you like me to try the bisect again with a little more > diligence, or do you think it can be found with the info given? It > may take a week or so, due to being a bit busy. It would be good, especially if this bug doesn't end up being solved some other way... And slow results are better than no results at all ;) Linus -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
