{"thread":{"id":"3739","subject":"Problem with git bisect between 2.6.15 and 2.6.16","startedAt":"2006-03-28T00:00:25Z","lastAt":"2006-03-29T19:28:07Z","messageCount":5,"participants":["Greg Lee","sean","Tony Luck"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"18041","messageId":"0e7301c651fa$9e0fd770$a100a8c0@casabyte.com","threadId":"3739","inReplyTo":null,"subject":"Problem with git bisect between 2.6.15 and 2.6.16","fromName":"Greg Lee","fromEmail":"glee@casabyte.com","sentAt":"2006-03-28T00:00:25Z","receivedAt":"2006-03-28T00:00:25Z","isPatch":false,"sender":{"key":"glee@casabyte.com","avatar":null},"body":"I get the following when I try to git bisect between 2.6.15 and 2.6.16:\n \n[root@Fedora-test tmp]# git clone\ngit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git\n[root@Fedora-test linux-git]# git bisect start\n[root@Fedora-test linux-git]# cd linux-git\n[root@Fedora-test linux-git]# git bisect good v2.6.16\n[root@Fedora-test linux-git]# git bisect bad v2.6.15\ndab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad\n\nWhat is the proper method to do a bisect between 2.6.15 and 2.6.16?\n\nGreg\n"},{"id":"18043","messageId":"BAYC1-PASMTP036F0DBE8F7101BCAD5470AED30@CEZ.ICE","threadId":"3739","inReplyTo":"0e7301c651fa$9e0fd770$a100a8c0@casabyte.com","subject":"Re: Problem with git bisect between 2.6.15 and 2.6.16","fromName":"sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2006-03-28T00:06:27Z","receivedAt":"2006-03-28T00:06:27Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"On Mon, 27 Mar 2006 19:00:25 -0500\n\"Greg Lee\" <glee@casabyte.com> wrote:\n\n> I get the following when I try to git bisect between 2.6.15 and 2.6.16:\n>  \n> [root@Fedora-test tmp]# git clone\n> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git\n> [root@Fedora-test linux-git]# git bisect start\n> [root@Fedora-test linux-git]# cd linux-git\n> [root@Fedora-test linux-git]# git bisect good v2.6.16\n> [root@Fedora-test linux-git]# git bisect bad v2.6.15\n> dab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad\n> \n> What is the proper method to do a bisect between 2.6.15 and 2.6.16?\n> \n\nYou need to do the bisect start after you cd into the linux-git \ndirectory.   Also, it appears you have the good and bad reversed,\npresumably the newer (v2.6.16) is bad, and the older (v.2.6.15)\nis good.\n\nSean\n"},{"id":"18045","messageId":"0e7e01c651fc$e30a2860$a100a8c0@casabyte.com","threadId":"3739","inReplyTo":"BAYC1-PASMTP036F0DBE8F7101BCAD5470AED30@CEZ.ICE","subject":"RE: Problem with git bisect between 2.6.15 and 2.6.16","fromName":"Greg Lee","fromEmail":"glee@casabyte.com","sentAt":"2006-03-28T00:16:40Z","receivedAt":"2006-03-28T00:16:40Z","isPatch":false,"sender":{"key":"glee@casabyte.com","avatar":null},"body":"> You need to do the bisect start after you cd into the linux-git \n> directory.\n\nSorry, cut and paste error, I did the cd before the bisect:\n\n[root@Fedora-test git]# git clone\ngit://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git-fresh\n[root@Fedora-test git]# cd linux-git-fresh/\n[root@Fedora-test linux-git-fresh]# git bisect start\n[root@Fedora-test linux-git-fresh]# git bisect bad v2.6.15\n[root@Fedora-test linux-git-fresh]# git bisect good v2.6.16\ndab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad\n\n> Also, it appears you have the good and bad reversed,\n> presumably the newer (v2.6.16) is bad, and the older (v.2.6.15)\n> is good.\n\nNo, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I\ncan back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad.\n\nGreg\n"},{"id":"18047","messageId":"12c511ca0603271622n6e4614b2s6f936469863efd9d@mail.gmail.com","threadId":"3739","inReplyTo":"0e7e01c651fc$e30a2860$a100a8c0@casabyte.com","subject":"Re: Problem with git bisect between 2.6.15 and 2.6.16","fromName":"Tony Luck","fromEmail":"tony.luck@intel.com","sentAt":"2006-03-28T00:22:33Z","receivedAt":"2006-03-28T00:22:33Z","isPatch":false,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":"> No, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I\n> can back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad.\n\nYou'll need to invert \"good\" and bad\" for this.  I.e. mark 2.6.15 as\ngood, 2.6.16 as bad, and\nthen as you test mark kernels with the bug as good, and ones without\nas bad.  Try not to go\ninsane while working in this inverted parallel universe :-)\n\n-Tony\n"},{"id":"18129","messageId":"117a01c65366$e952dfd0$a100a8c0@casabyte.com","threadId":"3739","inReplyTo":"12c511ca0603271622n6e4614b2s6f936469863efd9d@mail.gmail.com","subject":"RE: Problem with git bisect between 2.6.15 and 2.6.16","fromName":"Greg Lee","fromEmail":"glee@casabyte.com","sentAt":"2006-03-29T19:28:07Z","receivedAt":"2006-03-29T19:28:07Z","isPatch":false,"sender":{"key":"glee@casabyte.com","avatar":null},"body":"> You'll need to invert \"good\" and bad\" for this.  I.e. mark 2.6.15 as good, 2.6.16 as\nbad, and\n> then as you test mark kernels with the bug as good, and ones without as bad.  Try not to\ngo\n> insane while working in this inverted parallel universe :-)\n> \n> -Tony\n\nThis was progressing fine until I ran into an issue that makes the kernel unstable causing\nit to crash at semi-random times.  I'm down to about 350 commits left in the bisect.  I've\ntried:\n\ngit reset --hard HEAD~3\n\nno luck, same problem, unstable\n\nthen I tried --hard HEAD~50\n\nno luck, same problem, unstable\n\nI'm concerned about moving too much further in the \"~\" direction, will this cause me other\nproblems?\n\nGreg\n"}]}