Messages in this thread | | | Subject | Re: AMD X2 unsynced TSC fix? | From | john stultz <> | Date | Wed, 08 Nov 2006 17:13:24 -0800 |
| |
On Thu, 2006-11-09 at 00:39 +0000, Sergio Monteiro Basto wrote: > On Wed, 2006-11-08 at 20:53 +0100, Thomas Gleixner wrote: > > This one is a lock dependency problem, which is fixed in -rc5-mm1 > > yes, oops fixed w/ and w/o notsc option. > Other question, hrtimer in 2.6.18 found acpi_pm clocksource and use it. > With 2.6.19-rcx can't get acpi_pm clocksource even trying force at boot > kernel with clocksource=acpi_pm, any idea ? > because with this clocksource my lost ticket disappears
Looking at the dmesg in the bugzilla: http://bugzilla.kernel.org/show_bug.cgi?id=6419
I noticed you're using x86_64. x86_64 doesn't yet support clocksource overrides in mainline, as it is not converted to GENERIC_TIME. (Probably printing out such a warning if an override is used would be nice. I'll try to get to that soon.)
Now, the code to convert x86_64 is in tglx's hrtimer patch set, so I'm glad to hear its working for you, however I'm not sure if it really is solving the issue or just hiding it (as lost ticks won't affect timekeeping when you use continuous clocksources and GENERIC_TIME).
To use the ACPI PM w/ a 2.6.19-rcX kernel, use "notsc", and you'll see the line: time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
Using the "notsc" option, do you continue to see lost tick messages after bootup?
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/
| |