{"thread":{"id":"20061","subject":"Problem with git bisect in git-1.6.3.3","startedAt":"2009-07-09T05:42:16Z","lastAt":"2009-07-10T05:05:24Z","messageCount":4,"participants":["Chris Clayton","Johannes Sixt","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"117649","messageId":"c6b1100b0907082242y7b348b13m8a4607c96b1d164b@mail.gmail.com","threadId":"20061","inReplyTo":null,"subject":"Problem with git bisect in git-1.6.3.3","fromName":"Chris Clayton","fromEmail":"chris2553@googlemail.com","sentAt":"2009-07-09T05:42:16Z","receivedAt":"2009-07-09T05:42:16Z","isPatch":false,"sender":{"key":"chris2553@googlemail.com","avatar":null},"body":"Hi,\n\nI'm using git bisect to track down a problem in 2.6.31-rc2 that is\nlocking up my laptop. I get so far in the bisection process and then\nend up building a kernel that seems to me to be outside the good..bad\nrange. First time up I thought it might be a case of PBKAC, but I've\nrun the process again (very carefully) and got to the same place.\n\nThe bisect log so far:\n\n[chris:~/kernel/linux-2.6]$ git bisect log\ngit bisect start\n# good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30\ngit bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6\n# bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2\ngit bisect bad 8e4a718ff38d8539938ec3421935904c27e00c39\n# good: [e7c5a4f292e0d1f4ba9a3a94b2c8e8b71e35b25a] powerpc/5121: make\nclock debug output more readable\ngit bisect good e7c5a4f292e0d1f4ba9a3a94b2c8e8b71e35b25a\n# bad: [d23c45fd84f79a3b84899dac053dcafe9d43ebc9] NFS: Invalid mount\noption values should always fail, even with \"sloppy\"\ngit bisect bad d23c45fd84f79a3b84899dac053dcafe9d43ebc9\n# bad: [2ed0e21b30b53d3a94e204196e523e6c8f732b56] Merge\ngit://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6\ngit bisect bad 2ed0e21b30b53d3a94e204196e523e6c8f732b56\n\nbut, from Makefile, it appears the last \"bad\" has placed me at a\nchange earlier than 2.6.30:\n\n[chris:~/kernel/linux-2.6]$ head Makefile\nVERSION = 2\nPATCHLEVEL = 6\nSUBLEVEL = 30\nEXTRAVERSION = -rc6\nNAME = Vindictive Armadillo\n\n# *DOCUMENTATION*\n# To see a list of typical targets execute \"make help\"\n# More info can be located in ./README\n# Comments in this file are targeted only to the developer, do not\n\nI'm not an experienced git user, so it may be that I have made an\nerror or false assumption. I guess it's also possible that I've\nscrewed my repository, although basically I only use two types of\ncommand - pull a few times a week and the bisect family when I'm\ntrying to track down a problem.\n\nCome to think of it, I did archive the repository (with tar | bzip2)\nabout a week ago whilst I changed the hard drive in my laptop. Once\nthe new drive was installed, I restored the repository and freshened\nit up with a git pull. Could this be the root of my problem, please?\n\nHappy to provide more information if needed. Please cc me to any reply\n- I'm not subscribed.\n\nThanks\n\nChris\n\n-- \nNo, Sir; there is nothing which has yet been contrived by man, by\nwhich so much happiness is produced as by a good tavern or inn -\nDoctor Samuel Johnson\n"},{"id":"117651","messageId":"4A5590A3.8070404@viscovery.net","threadId":"20061","inReplyTo":"c6b1100b0907082242y7b348b13m8a4607c96b1d164b@mail.gmail.com","subject":"Re: Problem with git bisect in git-1.6.3.3","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2009-07-09T06:39:31Z","receivedAt":"2009-07-09T06:39:31Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Chris Clayton schrieb:\n> git bisect start\n> # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30\n> git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6\n> # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2\n...\n> but, from Makefile, it appears the last \"bad\" has placed me at a\n> change earlier than 2.6.30:\n> \n> [chris:~/kernel/linux-2.6]$ head Makefile\n> VERSION = 2\n> PATCHLEVEL = 6\n> SUBLEVEL = 30\n> EXTRAVERSION = -rc6\n...\n> I'm not an experienced git user, so it may be that I have made an\n> error or false assumption.\n\nNot an error, but false assumptions:\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977\n\nJust continue bisecting. If you can't test the version that bisect warps\nyou to because the feature where the bug happens is not present, mark that\nrevision as \"good\".\n\n-- Hannes\n"},{"id":"117653","messageId":"c6b1100b0907090013q728201d9r5f536d0433e92f2b@mail.gmail.com","threadId":"20061","inReplyTo":"4A5590A3.8070404@viscovery.net","subject":"Re: Problem with git bisect in git-1.6.3.3","fromName":"Chris Clayton","fromEmail":"chris2553@googlemail.com","sentAt":"2009-07-09T07:13:30Z","receivedAt":"2009-07-09T07:13:30Z","isPatch":false,"sender":{"key":"chris2553@googlemail.com","avatar":null},"body":"Hannes,\n\nThanks for your reply.\n\n2009/7/9 Johannes Sixt <j.sixt@viscovery.net>:\n> Chris Clayton schrieb:\n>> git bisect start\n>> # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30\n>> git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6\n>> # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2\n> ...\n>> but, from Makefile, it appears the last \"bad\" has placed me at a\n>> change earlier than 2.6.30:\n>>\n>> [chris:~/kernel/linux-2.6]$ head Makefile\n>> VERSION = 2\n>> PATCHLEVEL = 6\n>> SUBLEVEL = 30\n>> EXTRAVERSION = -rc6\n> ...\n>> I'm not an experienced git user, so it may be that I have made an\n>> error or false assumption.\n>\n> Not an error, but false assumptions:\n>\n> http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977\n>\n> Just continue bisecting. If you can't test the version that bisect warps\n> you to because the feature where the bug happens is not present, mark that\n> revision as \"good\".\n>\n\nAh, it makes sense now. Thanks for your help.\n\nChris\n\n> -- Hannes\n>\n>\n\n\n\n-- \nNo, Sir; there is nothing which has yet been contrived by man, by which\nso much happiness is produced as by a good tavern or inn - Doctor Samuel\nJohnson\n"},{"id":"117750","messageId":"200907100705.24199.chriscool@tuxfamily.org","threadId":"20061","inReplyTo":"4A5590A3.8070404@viscovery.net","subject":"Re: Problem with git bisect in git-1.6.3.3","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2009-07-10T05:05:24Z","receivedAt":"2009-07-10T05:05:24Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Thursday 09 July 2009, Johannes Sixt wrote:\n> Chris Clayton schrieb:\n> > git bisect start\n> > # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30\n> > git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6\n> > # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2\n>\n> ...\n>\n> > but, from Makefile, it appears the last \"bad\" has placed me at a\n> > change earlier than 2.6.30:\n> >\n> > [chris:~/kernel/linux-2.6]$ head Makefile\n> > VERSION = 2\n> > PATCHLEVEL = 6\n> > SUBLEVEL = 30\n> > EXTRAVERSION = -rc6\n>\n> ...\n>\n> > I'm not an experienced git user, so it may be that I have made an\n> > error or false assumption.\n>\n> Not an error, but false assumptions:\n>\n> http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977\n>\n> Just continue bisecting. If you can't test the version that bisect warps\n> you to because the feature where the bug happens is not present, mark\n> that revision as \"good\".\n\nFor information, I added the following very short FAQ entry:\n\nhttp://git.or.cz/gitwiki/GitFaq#Whydoes.22gitbisect.22makesmetestversionsoutsidethe.22good-bad.22range.3F\n\nThanks,\nChristian.\n"}]}