From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Campbell Subject: Re: XP machine freeze Date: Tue, 31 Mar 2015 08:27:45 +0800 Message-ID: <5519EA01.4010102@fnarfbargle.com> References: <009701d05ffb$5e37a740$1aa6f5c0$@astim.si> <550EE047.3030605@fnarfbargle.com> <5519BBF4.7080600@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit To: Paolo Bonzini , Saso Slavicic , kvm@vger.kernel.org Return-path: Received: from ns3.fnarfbargle.com ([103.4.17.7]:53654 "EHLO ns3.fnarfbargle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753419AbbCaA1v (ORCPT ); Mon, 30 Mar 2015 20:27:51 -0400 In-Reply-To: <5519BBF4.7080600@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 31/03/15 05:11, Paolo Bonzini wrote: > > > On 22/03/2015 16:31, Brad Campbell wrote: >> >> >> No help I'm afraid, but at least I can conclusively say that 3.16 is >> good, and 3.17 is bad. > > Can you try more specifically around the first KVM pull request? That > would be between c9b88e958182 (presumed good) and 8533ce727188 (presumed > bad)? > G'day Paolo, I can and will. Right now I'm toward the end of the bisect run I detailed in my previous e-mail, however disturbingly git bisect visualize shows no kvm commits at all. I'm beginning to think that something non-deterministic is just making this easier or harder to hit. Bad kernels usually go bad in a day at most, good kernels I've been leaving for up to 5 days. Here's where the log is at right now. visualize shows 68 commits and I can't see any of them being even remotely related to kvm. brad@srv:/raid10/src/linux$ git bisect log git bisect start # good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16 git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6 # bad: [bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9] Linux 3.17 git bisect bad bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9 # good: [f2d7e4d4398092d14fb039cb4d38e502d3f019ee] checkpatch: add fix_insert_line and fix_delete_line helpers git bisect good f2d7e4d4398092d14fb039cb4d38e502d3f019ee # good: [c309bfa9b481e7dbd3e1ab819271bf3009f44859] Merge tag 'for-linus-20140808' of git://git.infradead.org/linux-mtd git bisect good c309bfa9b481e7dbd3e1ab819271bf3009f44859 # bad: [433ab34d26e29d0f036c3f514a09ae96f973d8c5] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net git bisect bad 433ab34d26e29d0f036c3f514a09ae96f973d8c5 # bad: [d27c0d90184a13e9e9f28c38e84f889a259f6b5f] Merge branch 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect bad d27c0d90184a13e9e9f28c38e84f889a259f6b5f # bad: [913847586290d5de22659e2a6195d91ff24d5aa6] Merge branch 'linux-3.17' of git://anongit.freedesktop.org/git/nouveau/linux-2.6 git bisect bad 913847586290d5de22659e2a6195d91ff24d5aa6 # good: [d1e458fe671baf1e60afafc88bda090202a412f1] svcrdma: remove rdma_create_qp() failure recovery logic git bisect good d1e458fe671baf1e60afafc88bda090202a412f1 # bad: [023f78b02c729070116fa3a7ebd4107a032d3f5c] Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6 git bisect bad 023f78b02c729070116fa3a7ebd4107a032d3f5c # bad: [ad1f5caf34390bb20fdbb4eaf71b0494e89936f0] Merge branch 'fixes' of git://ftp.arm.linux.org.uk/~rmk/linux-arm git bisect bad ad1f5caf34390bb20fdbb4eaf71b0494e89936f0 If someone could give me some hard tests to do along the lines of what Saso is up to I could probably get that done faster. With the right bad kernel I can reproduce this lockup in a matter of hours. Regards, Brad