> That's a pretty wide range to be bisecting, and I think we know for a > fact there were some kvmclock related bugs in that range. thats true, I might try to pick those that seem related and see if it helpts.. > > If you are looking for something causing problems with tcpdump, I'd > suggest getting rid of kvmclock in your testing and using TSC instead; that's the problem, I can't reproduce the problems without kvm-clock enabled, so it must be related to it somehow.. > if you're looking to verify that kvmclock related changed have been > backported to -stable, rather than bisect and run into bugs, it would > probably be faster to check the commit logs for arch/x86/kvm/x86.c and > make sure you're not missing anything from me or Glauber that has been > applied to the most recent branch. yup, I'll try and report... thanks for the hints! n. > > Zach > -- ------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@xxxxxxxxxxx -------------------------------------
Attachment:
pgpmVm4kHajQ_.pgp
Description: PGP signature
