From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: XP machine freeze Date: Tue, 31 Mar 2015 13:23:39 +0200 Message-ID: <551A83BB.7040107@redhat.com> References: <009701d05ffb$5e37a740$1aa6f5c0$@astim.si> <550EE047.3030605@fnarfbargle.com> <5519BBF4.7080600@redhat.com> <5519EA01.4010102@fnarfbargle.com> <004f01d06b7c$08b96970$1a2c3c50$@astim.si> <551A4A42.10309@fnarfbargle.com> <551A6121.5030400@redhat.com> <551A8213.7080100@fnarfbargle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: Brad Campbell , Saso Slavicic , kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:57212 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751178AbbCaLZD (ORCPT ); Tue, 31 Mar 2015 07:25:03 -0400 In-Reply-To: <551A8213.7080100@fnarfbargle.com> Sender: kvm-owner@vger.kernel.org List-ID: On 31/03/2015 13:16, Brad Campbell wrote: > > If you look at the bisect point I'm currently at it's a mix of i2c and > arm. The only vaguely relevant (as far as I can see) commit is the > addition of the getrandom() syscall, so my bisect is looking dodgy at > best. If I can come up with a better test case on a non-critical box > then I'll be in a better position to try and help get to the bottom of > the issue. Yes, the bisect went wrong somewhere. Still, the 'bad' commit leave both a net-next and a KVM merge, so it could be worse. :) Paolo