Re: 2.6.35-rc1 regression with pvclock and smp guests

Zachary Amsden
2010-09-30T15:32:30Z

On 09/30/2010 05:12 AM, Michael Tokarev wrote:
> 30.09.2010 17:54, Zachary Amsden wrote:
> []
>
>> The printk movement is just a bandaid patch, correct? Anything which
>> does printk before kvmclock is registered could trigger the same bug.
>>
> Well, I'd not say it's just a bandaid patch, it's real bug -- either
> we can read kvmclock (so it's initialized), or we don't touch it (at
> least before registration).
>

Yes, that's the bug, but moving the printk doesn't fix that, it just
hides it.

>
>> Can you try with printk timing disabled and see if the bug disappears?
>>
> Yes it disappears so far, at last I can't trigger it anymore, tried
> numerous boots including the 2.6.35.6 32bit kernel (patched with the
> printk registration patch!) which shows the prob in almost every boot.
>

So, looks like we need to do the real fix.

Zach