From patchwork Thu Mar 26 15:58:07 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?b?UmFkaW0gS3LEjW3DocWZ?= X-Patchwork-Id: 6100571 Return-Path: X-Original-To: patchwork-kvm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork1.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork1.web.kernel.org (Postfix) with ESMTP id 640939F318 for ; Thu, 26 Mar 2015 15:58:22 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 076C7203EC for ; Thu, 26 Mar 2015 15:58:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D41B820411 for ; Thu, 26 Mar 2015 15:58:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752648AbbCZP6N (ORCPT ); Thu, 26 Mar 2015 11:58:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47607 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752639AbbCZP6M (ORCPT ); Thu, 26 Mar 2015 11:58:12 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 30FFCB6F2F; Thu, 26 Mar 2015 15:58:12 +0000 (UTC) Received: from potion (dhcp-1-126.brq.redhat.com [10.34.1.126]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with SMTP id t2QFw89H023811; Thu, 26 Mar 2015 11:58:08 -0400 Received: by potion (sSMTP sendmail emulation); Thu, 26 Mar 2015 16:58:07 +0100 Date: Thu, 26 Mar 2015 16:58:07 +0100 From: Radim =?utf-8?B?S3LEjW3DocWZ?= To: "Kevin O'Connor" Cc: Andrey Korolyov , "Dr. David Alan Gilbert" , Bandan Das , Paolo Bonzini , Gerd Hoffmann , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error Message-ID: <20150326155807.GA13271@potion.brq.redhat.com> References: <20150312095902.GC2330@work-vm> <20150325205439.GA21667@morn.localdomain> <20150325230259.GA29924@morn.localdomain> <20150326000502.GA1217@morn.localdomain> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20150326000502.GA1217@morn.localdomain> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00,HK_RANDOM_FROM, RCVD_IN_DNSWL_HI, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP 2015-03-25 20:05-0400, Kevin O'Connor: > On Thu, Mar 26, 2015 at 02:35:58AM +0300, Andrey Korolyov wrote: > > Thanks, strangely the reboot is always failing now and always reaching > > seabios greeting. May be prints straightened up a race (e.g. it is not > > int19 problem really). > > > > object file part: > > > > 0000d331 : > > irq_trampoline_0x19(): > > /root/seabios-1.8.1/src/romlayout.S:195 > > d331: cd 19 int $0x19 > > d333: cb lretw > > [...] > > Jump to int19 (vector=f000e6f2) > > Thanks. So, it dies on the "int $0x19" instruction itself. The > vector looks correct and I don't see anything in the cpu register > state that looks wrong. Maybe one of the kvm developers will have an > idea what could cause a fault there. The place agrees with the " 19 cb" part of KVM error output. Suberror 2 means that we were interrupted while delivering a vector, here it is disected: (delivering 'vect_info') vect_info (extra data[0]: 800000ef) - vector 0xef - INTR_TYPE_EXT_INTR (0x000) - no error code (0x000) - valid (0x80000000) intr_info (extra data[1]: 80000b0d) - #GP (0x0d) - INTR_TYPE_HARD_EXCEPTION (0x300) - error code on stack (0x800) [Hunk at the bottom exposes it.] - valid (0x80000000) Notice the 0xef. My best hypothesis so far is that we fail at resetting devices, and 0xef is LOCAL_TIMER_VECTOR from Linux before we rebooted. (The bug happens at the first place that enables interrupts.) This should be handled without an internal error, though. (It's possible we are hitting two bugs here ...) Can you provide KVM event trace as well? (`trace-cmd record -e 'kvm*'`) Thanks. --- -- 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 diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index 50c675b46901..541a29476a56 100644 --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c @@ -5088,9 +5088,10 @@ static int handle_exception(struct kvm_vcpu *vcpu) !(is_page_fault(intr_info) && !(error_code & PFERR_RSVD_MASK))) { vcpu->run->exit_reason = KVM_EXIT_INTERNAL_ERROR; vcpu->run->internal.suberror = KVM_INTERNAL_ERROR_SIMUL_EX; - vcpu->run->internal.ndata = 2; + vcpu->run->internal.ndata = 3; vcpu->run->internal.data[0] = vect_info; vcpu->run->internal.data[1] = intr_info; + vcpu->run->internal.data[2] = error_code; return 0; }