Is it safe to do 'git bisect' several time on kernel
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it safe to do 'git bisect' several time on kernel
I'm running Debian with 3.2 kernel which is totally good. But I wanted to hack the newest kernel. After installing 3.15.6 (latest stable so far) I realized that my wifi card doesn't work and in fact wasn't recognized.
So I got help from Linux Kernel specialists and found out have to do 'git bisect'.
Now, I need to do it roughly 17 times and boot into built kernel each time to get to the bottom of it finding the very first bad commit to report that, in order to fix the bug.
my question is this: Is it safe for my device to reboot at least 17 times in some continuous hours?
Thank you in advance.
I think you misunderstand what git bisect is used for. You need to write a test that works against the source code from a point that you know works to the point that you know is broken. git bisect will iterate through the history of a git repository executing that test and let you know which commit it starts failing. That is to say you have to clone the Linux kernel git repository and work from two points in the history (or a git repository that is associated with your currently running kernel).
Are you sure that Debian didn't create some patch or hack on the kernel which hasn't been pushed upstream? Try compiling the 3.2 kernel from kernel.org. Is your wifi card still detected then?
If not, then it is likely Debian integrated some patch which you'll have to figure out and forward port to the latest kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.