Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade

[Miklos Vajna]

On Thu, Jan 22, 2009 at 08:55:58PM +0100, Ingo Molnar <mingo@xxxxxxx> wrote:
> these look suspect in the good->bad diff:
> 
>  # CONFIG_X86_VOYAGER is not set
>  # CONFIG_X86_GENERICARCH is not set
>  # CONFIG_X86_VSMP is not set
> -# CONFIG_X86_VISWS is not set
> -# CONFIG_X86_RDC321X is not set
> +CONFIG_X86_VISWS=y
> +CONFIG_X86_RDC321X=y
>  CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
> -# CONFIG_PARAVIRT_GUEST is not set
> +CONFIG_PARAVIRT_GUEST=y
> +# CONFIG_VMI is not set
> +CONFIG_KVM_CLOCK=y
> +CONFIG_KVM_GUEST=y
> +CONFIG_LGUEST_GUEST=y
> +CONFIG_PARAVIRT=y
> +CONFIG_PARAVIRT_CLOCK=y
> +# CONFIG_PARAVIRT_DEBUG is not set
>  CONFIG_MEMTEST=y

Hmm it seems my reply to this mail was lost, so:

First I build with CONFIG_X86_VISWS, CONFIG_X86_RDC321X and
CONFIG_PARAVIRT_GUEST disabled, then the clock became normal again.

Then later I tried just disabling CONFIG_X86_VISWS and
CONFIG_X86_RDC321X, and that was enough as well.

Thank you!

Attachment: pgp00000.pgp
Description: PGP signature