On 2010-09-29 11:19, Michael Tokarev wrote: > 29.09.2010 13:17, Michael Tokarev ÐÐÑÐÑ: >> 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 = b6dc43b6, shadow.tsc_shift = ffffffff, >>>> shadow.flags = 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. > > 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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
