Messages in this thread | | | Subject | Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers | From | Thomas Gleixner <> | Date | Sat, 11 Nov 2006 15:08:52 +0100 |
| |
On Sat, 2006-11-11 at 14:59 +0100, Andi Kleen wrote: > On Saturday 11 November 2006 14:58, Thomas Gleixner wrote: > > > > > > > > > My guess is that some of the checks in there are just broken and need > > > > > to be fixed. > > > > > > > > It's the unconditional mark_unstable call in ACPI C2 state. /me looks. > > > > > > The system doesn't support C2 states. It's an older single socket Athlon 64 > > > with VIA chipset. I haven't looked in detail on why it fails. > > > > Does it have cpu freqency changing ? > > Yep. But only OS controlled one (powernow). > > Most likely it happens when ondemand starts doing its thing.
Yes, thats one of the criterias the tsc clocksource is using. I'm looking into that right now.
tglx
- 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/
| |