Re: [Bugme-new] [Bug 8392] New: Hard Lock Subsequent to Boot

[Adrian Bunk <bunk@stusta.de>]

On Sat, Apr 28, 2007 at 11:59:06AM -0700, Andrew Morton wrote:
>...
> 3: Performa a git bisection search, find the buggy patch.  This is quite a
>    lot of work, and I hate asking people to do it because we don't (afaik)
>    have any particularly good documentation on how to perform it.


The text I'm using for telling people how to bisect is:

<--  snip  -->

# install git and cogito on your computer

# clone Linus' tree:
cg-clone \ 
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# start bisecting:
cd linux-2.6
git bisect start
git bisect bad v2.6.21
git bisect good v2.6.20
cp /path/to/.config .

# start a round
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round


After at about 12 reboots you'll have found the guilty commit
("...  is first bad commit").


More information on git bisecting:
  man git-bisect

<--  snip  -->


Is this text understandable?

If not, what is missing?


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/