On Wed, Nov 25, 2009 at 01:25:18PM -0500, Alan Stern wrote: > On Tue, 24 Nov 2009, Greg KH wrote: > > > > I don't know how to do a 'git bisect', nor do I have the time to learn > > > just at the moment. However, I have pinpointed the broken release to > > > 2.6.27.23. If I run my tests on 2.6.27.22 I do _not_ see the problem. But > > > when I perform the same tests on 2.6.27.23 the kernel oops starts happening > > > 100% of the time. > > > > Heh, you just did bisect it down to the range of changes, which is what > > I asked for, thanks :) > > > > Alan, this points to your 2d93148ab6988cad872e65d694c95e8944e1b626 > > commit that was added to the 2.6.27.23 kernel. > > Not necessarily; it could be caused by Alan Cox's changes to the TTY > core, if any occurred between those two releases. > > Here's something rather confusing. The URL: > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commit;h=2d93148ab6988cad872e65d694c95e8944e1b62 > > brings up a page containing the commit you mentioned above. But that > commit was never added to the 2.6.27.y tree! It's part of Linus's main > tree. The actual commit applied as part of 2.6.27.23 was > 070bb0f3b6df167554f0ecdeb17a5bcdb1cd7b83. So what's going on here? Probably due to the fact that the stable tree is cloned with the "base" being Linus's main tree. So when you ask for a commit, and it can't find it in the local tree, it will go to the "base" to try to find it, and it does. It is a bit weird though, perhaps we should report this to the git developers. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
