* Michael Tokarev <mjt@xxxxxxxxxx> wrote: > Now, after quite some googling around, I tried to disable hpet, > booting with hpet=disable parameter. And that one fixed all the > problems at once. 7 days uptime, I stress-tested it several times, > it works with TSC as timesource (still a problem within guests as > those shows unstable TSC anyway) since boot, no issues logged. > Even cpufreq works as expected... > > Note that i tried to disable hpet as clocksource several times but > without any noticeable effect - kernel still used hpet and hpet2 > for something, and printed that scary "increasing min_delay" > message on a semi-regular basis usually after the next 'stuck' > state.... It could again go bad like it did before - those messages are signs of HPET weirdnesses. Probably your box's hpet needs to be blacklisted, so that it gets disabled automatically on bootup. Ingo -- 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
