Ok, I kept going like you said. Here is what it said: $git bisect good 44ea2b1758d88ad822e65b1c4c21ca6164494e27 is the first bad commit commit 44ea2b1758d88ad822e65b1c4c21ca6164494e27 Author: Avi Kivity <avi@xxxxxxxxxx> Date: Sun Sep 6 15:55:37 2009 +0300 KVM: VMX: Move MSR_KERNEL_GS_BASE out of the vmx autoload msr area Currently MSR_KERNEL_GS_BASE is saved and restored as part of the guest/host msr reloading. Since we wish to lazy-restore all the other msrs, save and reload MSR_KERNEL_GS_BASE explicitly instead of using the common code. Signed-off-by: Avi Kivity <avi@xxxxxxxxxx> :040000 040000 fcf14f9e5578a996430650f7806a54bcc8184ef6 24f4b80719c5b7931a5ed5604f3554f78352ed67 M arch $ On 7/3/10, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 07/02/2010 10:08 PM, BuraphaLinux Server wrote: >> Hello, >> >> I tried my best to do the bisection, and the result after many kernels >> was: >> >> Bisecting: 0 revisions left to test after this (roughly 0 steps) >> [3ce672d48400e0112fec7a3cb6bb2120493c6e11] KVM: SVM: init_vmcb(): >> remove redundant save->cr0 initialization >> >> So what do I do next? > > > You still need to test that last kernel. "0 revisions left" means that > after this test (and the last "git bisect good" or "git bisect bad") > you'll have the answer. > >> I did not 'make mrproper' between each build - >> should I have done that? >> > > No need. > > -- > I have a truly marvellous patch that fixes the bug which this > signature is too narrow to contain. > > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html