tags 681232 - patch
quit
Jesse Rhodes wrote:
> (iii) broke,
> (iv) worked.
Weird. I can't find any obvious candidate for a patch that would have
broken the driver.
Can you bisect? Even a few iterations would help a lot in narrowing
down the search. It works like so:
cd linux
git bisect start
git checkout v3.2.21; # vanilla kernel
make deb-pkg; # optionally with -j<num> for parallel build
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
# hopefully it avoids the bug, so
cd linux
git bisect good
git checkout debian/wheezy; # patched kernel
make deb-pkg; # maybe with -j4
dpkg -i ../<name of package>; # as root
reboot
... test test test ...
# hopefully it reproduces the bug, so
cd linux
git bisect bad
# a rev halfway between is automatically checked out
# to test
make deb-pkg; # maybe with -j4
dpkg -i ../<package>; # as root
reboot
... test test test ...
cd linux
git bisect bad; # if it reproduces the bug
git bisect good; # if it reliably does not
git bisect skip; # if some other bug makes it hard to test
# another rev to test is automatically checked out
... continue until it finds the "first bad rev" ...
At any step you can watch the regression range narrowing by
running "git bisect visualize" if the gitk package is installed.
When finished or bored, please run "git bisect log" to list revs
it has tested so others can analyze your results or pick up where
you left off.
Thanks again, and sorry I have no better ideas.
Sincerely,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
