Kernel bisecting: is this the proper way?

stefanwilkens · 2012-09-16 08:35:23

Hello all,

I've been trying to pinpoint the cause of:
https://bugs.archlinux.org/task/30577

I've since found that the regression (certain buttons fail to register, no scancode / xevent reported) occurs somewhere between 3.3.8-1-ARCH and 3.4-1-ARCH. My next step would be to start a bisect between kernels tagged 3.3 and 3.4, as follows:

git clone https://github.com/torvalds/linux.git
git checkout v3.4
git bisect start
git bisect bad
git bisect good v3.3

This, however, leaves me with 4869 revisions. "roughly 13 steps" according to git.

Am I doing this the correct and most efficient way?

Looking to learn here, any tips of properly bisecting this issue to its root will be most welcome

Last edited by stefanwilkens (2012-09-16 10:20:21)

Arch Linux

#1 2012-09-16 08:35:23

Kernel bisecting: is this the proper way?

Board footer