From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021" Date: Thu, 13 Jun 2013 09:42:44 -0400 Message-ID: <51B9CC54.6070009@redhat.com> References: <5194C254.4000201@sp.consulting.lsexperts.de> <1368925231.3469.98.camel@deadeye.wl.decadent.org.uk> <20130519123227.GA13375@redhat.com> <51AF27A5.5030509@sp.consulting.lsexperts.de> <20130605121024.GZ4725@redhat.com> <51AF3447.6090308@sp.consulting.lsexperts.de> <20130606064240.GR4725@redhat.com> <51B073F1.8030107@sp.consulting.lsexperts.de> <20130606114025.GC4725@redhat.com> <51B07C3F.2060104@sp.consulting.lsexperts.de> <20130609094328.GM4725@redhat.com> <51B9B3AE.2040902@sp.consulting.lsexperts.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , Ben Hutchings , kvm@vger.kernel.org, 707257@bugs.debian.org To: Stefan Pietsch Return-path: Received: from mail-qc0-f174.google.com ([209.85.216.174]:56069 "EHLO mail-qc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756533Ab3FMNmu (ORCPT ); Thu, 13 Jun 2013 09:42:50 -0400 Received: by mail-qc0-f174.google.com with SMTP id m15so4591098qcq.19 for ; Thu, 13 Jun 2013 06:42:49 -0700 (PDT) In-Reply-To: <51B9B3AE.2040902@sp.consulting.lsexperts.de> Sender: kvm-owner@vger.kernel.org List-ID: Il 13/06/2013 07:57, Stefan Pietsch ha scritto: > git bisect tells me: > 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit This is an s390 commit, so the bisect somehow went wrong. Can you confirm that 3.7 works and 3.8 doesn't? Please check these pairs: 9e2d59a and 89f883372fa60f604d136924baf3e89ff1870e9e 39ab967 and 875b7679abbb232b584f2eec59fa6e45690dd6c4 10b3866 and ea4a0ce11160200410abbabd44ec9e75e93a95be 4ffd4eb and ccae663cd4f62890d862c660e5ed762eb9821c14 896ea17 and 66cdd0ceaf65a18996f561b770eedde1d123b019 Please tell us which pair introduced the failure. Then: - if you get a "bad and bad" pair, tell us and we'll figure out what's next :) - if you get a "good and bad" pair, do a "git bisect" between the two commits in that pair. Thanks! Paolo > This is my bisect log: > > git bisect start > git bisect bad 9626357371b519f2b955fef399647181034a77fe > git bisect good ef4e359d9b9e2dc022f79840fd207796b524a893 > git bisect good b5c78e04dd061b776978dad61dd85357081147b0 > git bisect good 9e2d59ad580d590134285f361a0e80f0e98c0207 > git bisect bad 69086a78bdc973ec0b722be790b146e84ba8a8c4 > git bisect good 9ecf9b085a0926e07c78c08a07296bbfd1c37d07 > git bisect bad 21fbd5809ad126b949206d78e0a0e07ec872ea11 > git bisect bad 79fd50c67f91136add9726fb7719b57a66c6f763 > git bisect good 66cdd0ceaf65a18996f561b770eedde1d123b019 > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >