http://bugzilla.kernel.org/show_bug.cgi?id=10561
------- Comment #12 from [EMAIL PROTECTED] 2008-04-30 03:53 -------
> ------- Comment #11 from [EMAIL PROTECTED] 2008-04-30 03:31 -------
> > What happens when you boot with clocksource=hpet or clocksource=acpi_pm on
> > the
> > kernel command line ?
>
> Whichever one I boot with is, indeed, used from early on in the boot process
> (when tsc was previously initialized) and goes on being used after processor
> is
> loaded.
> As a result, the period (after loading processor) when the system clock is
> slowed down does not exist.
> However, after loading processor I still get the "tsc clocksource unstable"
> message (so I guess it's alive somewhere).
> Loading p4-clockmod still causes lockups when hpet is used...
Hmm. When you use clocksource=acpi_pm then it works with p4-clockmod, right ?
Can you please provide the output of /proc/timer_list for that scenario ?
Thanks,
tglx
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
