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). > 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. Thanks! /mjt -- 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
