On 08/29/2014 04:08 PM, Paolo Bonzini wrote: > Il 29/08/2014 19:36, Chris J Arges ha scritto: >> I still get failures with the following test, I actually tested on >> multiple machines with identical hardware and the same failure occurred. >> In v3.13/v3.16 series kernels this passes. I'll look into which commit >> changed this result for me. I suspect it was fairly recent. > > I would try bisecting between 0e5ac3a8b100469ea154f87dd57b685fbdd356f6 > (might be bad) and 41fa4215f8e8150bdc5d2a5f8704915f1b059fa8 (might be good). > Just sent the other email with my bisect results, the 'bad' commit for me is: 0d3da0d26e3c3515997c99451ce3b0ad1a69a36c A revert on this commit allows the tests to pass again. > Is this a laptop or desktop? Any relationship between the "Offset" and > how long the machine has been up? > > Paolo > This is a server; and no, I've reboot the machine and re-run the test. I've also run it after days of uptime. --chris -- 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
