Messages in this thread | | | Date | Fri, 14 May 2010 15:28:31 -0700 | Subject | Re: TSC unstable due to TSC halts in idle? | From | john stultz <> |
| |
On Fri, May 14, 2010 at 1:13 PM, Jesper Dangaard Brouer <hawk@diku.dk> wrote: > I want to know, if its safe to enable the TSC clocksource, when the > kernel reports: > "Marking TSC unstable due to TSC halts in idle" > > The system selects HPET (in current_clocksource), but I can still see > TSC as an available clocksource (in > /sys/devices/system/clocksource/clocksource0/available_clocksource). > > Is it safe to enable TSC manually (by changing current_clocksource)? > (my workload is 10Git/s routing, cannot survive with a slow clock) > > > Any trick to avoid this? (e.g. kernel config setting, or a /sys/ setting > which changes the minimum P-state?)
Might try booting with the max-cstate=1 option.
thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |