From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arjan Koers <0h61vkll2ly8@xutrox.com>
Subject: Re: 2.6.35-rc1 regression with pvclock and smp guests
Date: Wed, 29 Sep 2010 21:26:54 +0200
Message-ID: <4CA392FE.5090009@xutrox.com>
References: <4C4D4B8B.80006@amd.com> <4C4DDB00.50203@xutrox.com> <4C4F48D0.8090609@xutrox.com> <4C500872.1020809@redhat.com> <4C536F80.5090205@xutrox.com> <4C538CCE.1010104@redhat.com> <4C540EC9.1010008@xutrox.com> <4C54512B.6000307@xutrox.com> <4C54B7DE.4060901@redhat.com> <20100802144300.GD14448@mothafucka.localdomain> <4C5729F6.2050605@redhat.com> <4C573A20.6030001@xutrox.com> <4CA2F8A3.80400@redhat.com> <4CA30424.9030007@msgid.tls.msk.ru> <4CA30493.6090503@msgid.tls.msk.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Avi Kivity <avi@redhat.com>, Zachary Amsden <zamsden@redhat.com>,
	Glauber Costa <glommer@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Andre Przywara <andre.przywara@amd.com>
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from smtp-out2.tiscali.nl ([195.241.79.177]:51756 "EHLO
	smtp-out2.tiscali.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755060Ab0I2T1G convert rfc822-to-8bit (ORCPT
	<rfc822;kvm@vger.kernel.org>); Wed, 29 Sep 2010 15:27:06 -0400
In-Reply-To: <4CA30493.6090503@msgid.tls.msk.ru>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 2010-09-29 11:19, Michael Tokarev wrote:
> 29.09.2010 13:17, Michael Tokarev =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
>> 29.09.2010 12:28, Avi Kivity wrote:
>>>  On 08/03/2010 12:35 AM, Arjan Koers wrote:
>>>> I don't think that pvclock_clocksource_read is receiving
>>>> completely random uninitialized data. The values in shadow
>>>> are wrong, but could be interpreted as valid data
>>>> (shadow.tsc_to_nsec_mul =3D b6dc43b6, shadow.tsc_shift =3D fffffff=
f,
>>>> shadow.flags =3D 0 and shadow.version is always even).
>>>>
>>>> I've attached the printk patches for 2.6.34.1 and 2.6.35, in case
>>>> anyone needs them...
> []
>> Avi, this is definitely a -stable material, for 2.6.32 (longterm
>> stable) and 2.6.35.
>=20
> Er. Please excuse me for the misinformation.  It is _not_ for 2.6.32
> ofcourse.

I wish you hadn't mentioned 2.6.32. I just tried 2.6.32.23 and it also
hangs. Reverting commit 1345126c761f0360dc108973bf73281d51945bc1
(introduced in 2.6.32.16) makes it boot again.

The kvmclock printk patch doesn't help, but I'll try to figure out
what's wrong.