http://bugzilla.kernel.org/show_bug.cgi?id=7706
------- Comment #3 from [EMAIL PROTECTED] 2007-07-06 13:58 -------
Well, when you have working kernel which stops working with next release, you
can find actual patch or change that was incorporated and caused it not work
anymore, by excluding new updates and eventually getting the one that broke
your working kernel. Here is the procedure:
# install git and cogito on your computer (see kernel.org for information)
# 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.18-rc5
git bisect good v2.6.18-rc4
# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round
After at about 9 reboots, you'll have found the guilty commit
("... is first bad commit").
More information on git bisecting:
man git-bisect
It takes multiple reboots and patience... but then you can tell exactly what
patch introduced the problem.
Hope you can spend some time doing this - will be greatly appreciated.
Thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia
