From patchwork Thu Jul 26 09:52:41 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Chris Clayton X-Patchwork-Id: 1241001 Return-Path: X-Original-To: patchwork-kvm@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id A08A1DFFBF for ; Thu, 26 Jul 2012 09:53:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750849Ab2GZJwo (ORCPT ); Thu, 26 Jul 2012 05:52:44 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:36593 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750766Ab2GZJwn (ORCPT ); Thu, 26 Jul 2012 05:52:43 -0400 Received: by eaak13 with SMTP id k13so155857eaa.19 for ; Thu, 26 Jul 2012 02:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=URKDNR7P7ZjUalD/G42jR0svFF629ghDcQjTtEiWLkQ=; b=iwXnD0bHosEglNWCz0n/8IoO5ZuipgLdEkK0fqXQTnZApSOB5ETjnn70q0gXyMOGTx QccZIVFijP6jEwpmcfKT2YV0FCnpOCRw1TzYQ9VaLk8PQZrQcVLMsnafbpyQ8ih9pVGQ p9v7prRsxsPhaXxbOZMqbp6+slvZUC95AH25+qmcMTTno9rQb2frtssxIQ5D32AW1OBf gkY3KsCvgBhIouYSb32a5KxaQ4vOgi4Nk4448jZ0vQDisqZyJwjwxBaRYKAy0czQEXNV Ag6AgNvOMqrBlluwa5uOjWbV99x+Pf6L/ikjReQduXQfLsmH36yZ99Z8/jxIA6npKPHm P8tg== Received: by 10.14.211.6 with SMTP id v6mr3295097eeo.29.1343296361830; Thu, 26 Jul 2012 02:52:41 -0700 (PDT) Received: from [192.168.0.40] (5e025c88.bb.sky.com. [94.2.92.136]) by mx.google.com with ESMTPS id d7sm7216450eep.1.2012.07.26.02.52.40 (version=SSLv3 cipher=OTHER); Thu, 26 Jul 2012 02:52:41 -0700 (PDT) Message-ID: <50111369.6020209@googlemail.com> Date: Thu, 26 Jul 2012 10:52:41 +0100 From: Chris Clayton User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Avi Kivity CC: Gleb Natapov , kvm@vger.kernel.org Subject: Re: qemu-kvm-1.1.0 crashing with kernel 3.5.0-rc6 References: <4FFAB92C.4030001@googlemail.com> <4FFD26B6.8000802@googlemail.com> <20120711071200.GG23898@redhat.com> <4FFD28B9.9040604@googlemail.com> <20120711072255.GH23898@redhat.com> <50031F85.6020908@googlemail.com> <5007FA1C.5080606@googlemail.com> <5007FAD6.2010407@redhat.com> <500850AD.8080504@googlemail.com> In-Reply-To: <500850AD.8080504@googlemail.com> Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 07/19/12 19:23, Chris Clayton wrote: > On 07/19/12 13:17, Avi Kivity wrote: >> On 07/19/2012 03:14 PM, Chris Clayton wrote: >> >>>> Change of diagnostics, unfortunately. qemu-kvm-1.0.1 can, in fact, >>>> crash >>>> on 3.5.0-rc6 (and rc7). I didn't get it earlier because it takes many >>>> times more invocations before the crash occurs with 1.0.1 and I haven't >>>> used qemu-kvm much in the past few weeks. >>>> >>>> I'm now checking whether I can get crashes (with 1.0.1 and/or 1.1.0) on >>>> linux-3.4.4. I'll report back in a day or two. >>> >>> I've started up qemu-kvm on kernel 3.4.4 many times and not see a crash. >>> That would indicate that the problem is in the kernel. However, I pulled >>> the latest and greatest from Linus yesterday evening and I now can't get >>> the crash there either, so whatever it was seems to have been fixed. If >>> I checkout and build 3.5.0-rc[1..7], I can get the crash pretty quickly, >>> so it's been fixed in the last few days. >> >> There were no kvm changes post-rc7. >> > Yes, I'm aware of that, Avi. This thread started because I was getting a > crash in qemu-kvm, which I thought was only in v1.1.0. Later it turned > out the the problem was also present in v1.0.1, but much harder to hit. > However, it only ever happened with 3.5.0 kernels. 3.4.4, with either > version of qemu-kvm, was stable. So then it seemed that the problem was > in the kernel, (but not necessarily in the kvm code). > > Something that's changed since rc7 has either fixed the problem or made > it much harder to hit. With rc7 and earlier I can recreate the crash > quite easily with qemu-kvm-1.1.0 and with enough runs of 1.0.1. With > rc7+, I haven't been able to get a crash at all. > Well, I'm getting the crash again, but this time I've managed to get a backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb60ffb40 (LWP 9405)] 0xb7803d77 in __strcmp_sse4_2 () from /lib/libc.so.6 (gdb) bt #0 0xb7803d77 in __strcmp_sse4_2 () from /lib/libc.so.6 #1 0xb7e65333 in g_str_equal () from /usr/lib/libglib-2.0.so.0 #2 0xb7e6458d in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0 #3 0x8014e2cf in type_table_lookup (name=0x802b0c50 "apic-common") at qom/object.c:94 #4 type_get_by_name (name=name@entry=0x802b0c50 "apic-common") at qom/object.c:149 #5 0x8014e933 in object_dynamic_cast (obj=obj@entry=0x80a5d818, typename=typename@entry=0x802b0c50 "apic-common") at qom/object.c:416 #6 0x8014e8b9 in object_dynamic_cast_assert (obj=obj@entry=0x80a5d818, typename=typename@entry=0x802b0c50 "apic-common") at qom/object.c:478 #7 0x80193462 in cpu_set_apic_tpr (d=0x80a5d818, val=8 '\b') at /home/chris/rpm/BUILD/qemu-kvm-1.1.1/hw/apic_common.c:60 #8 0x801d0560 in kvm_arch_post_run (env=env@entry=0x80a55a60, run=run@entry=0xb6239000) at /home/chris/rpm/BUILD/qemu-kvm-1.1.1/target-i386/kvm.c:1695 #9 0x801cb05f in kvm_cpu_exec (env=env@entry=0x80a55a60) at /home/chris/rpm/BUILD/qemu-kvm-1.1.1/kvm-all.c:1269 #10 0x80199d1e in qemu_kvm_cpu_thread_fn (arg=0x80a55a60) at /home/chris/rpm/BUILD/qemu-kvm-1.1.1/cpus.c:752 #11 0xb7a1fd9e in start_thread () from /lib/libpthread.so.0 #12 0xb77bbbbe in clone () from /lib/libc.so.6 This is with kernel 3.5.0 and qemu-kvm-1.1.1. glibc is 2.16.0 built against 3.4.4 kernel headers. The glibc, the kernel headers and the kernel are vanilla and the only change to the qemu-kvm sources is: Please let me know of anything I can do to help track this down. Thanks Chris > I'm not inclined to bisect to find out which patch provided the fix, but > this mail should at least close the mail thread down tidily. > > Chris --- 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 --- qemu-kvm-1.1.0/configure~ 2012-07-15 22:38:39.000000000 +0100 +++ qemu-kvm-1.1.0/configure 2012-07-15 22:39:09.000000000 +0100 @@ -2783,7 +2783,7 @@ int main(int argc, char **argv) } EOF if ! compile_prog "" "" ; then - CFLAGS+="-march=i486" + CFLAGS+="-march=i686" fi fi