https://bugzilla.kernel.org/show_bug.cgi?id=100221
--- Comment #15 from Aaron Lu <[email protected]> --- git bisect will take some time so no hurry. You will need to find out which kernel version starts to break, instead of bisecting between v3.16 and v4.1, that would be too much commits in between. You need clone Linus' git tree first: $ git clone http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Suppose you find out v3.17 starts to break, then in the cloned tree, you can start bisect by: $ git bisect start $ git bisect bad v3.17 $ git bisect good v3.16 Then it will checking out the commit in the middle of v3.16..v3.17 and you need build kernel and test; according to the result, you need mark that commit as either good or bad: $ git bisect bad/good Then it will checking out a new commit and the steps repeat till the offending commit is found. -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
