From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: 2.6.35-rc1 regression with pvclock and smp guests Date: Tue, 27 Jul 2010 13:03:40 +0300 Message-ID: <4C4EAEFC.20207@redhat.com> References: <4C483F67.1010007@amd.com> <4C4BF96B.7010005@redhat.com> <4C4D4B8B.80006@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "glommer@redhat.com" , Zachary Amsden , KVM list To: Andre Przywara Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54733 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754927Ab0G0KDo (ORCPT ); Tue, 27 Jul 2010 06:03:44 -0400 In-Reply-To: <4C4D4B8B.80006@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/26/2010 11:47 AM, Andre Przywara wrote: >> Does this go away with CONFIG_DEBUG_RODATA=n? If so, it's a known >> bug in the atomic_*() clobber lists. >> > > Unfortunately the bug persists even with CONFIG_DEBUG_RODATA disabled. > The debug options I had enabled now are: > CONFIG_DEBUG_DEVRES=y > CONFIG_DEBUG_FS=y > CONFIG_DEBUG_KERNEL=y > CONFIG_DEBUG_BUGVERBOSE=y > CONFIG_DEBUG_MEMORY_INIT=y > CONFIG_DEBUG_STACKOVERFLOW=y > CONFIG_DEBUG_BOOT_PARAMS=y > > I even disabled all kernel debug options, that does not help, too. > Does changing last_value in arch/x86/kernel/pvclock.c to be non-static help? What is the guest executing when it hangs? -- error compiling committee.c: too many arguments to function