TSC cannot be used as a time source?

• To: fedora-list@xxxxxxxxxx
• Subject: TSC cannot be used as a time source?
• From: Linn Kubler <lkubler@xxxxxxxxx>
• Date: Fri, 15 Oct 2004 16:48:24 -0500
• Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=lQuc8qWQpfuZw+F/F8yfwATPAePrYkuITo16+WBD+pgbwl/kZj26S/jZuqz50pxBA9kD9fLDtv1F3iYd9PzKLHypWwLHGDODjJ/qTGX89tnKeqM9mR1yJ+tDXoG0IquauN2LQe96d2/TtKvZEpJQ7I41u0wmiS5zhVV/PZDtq4g
• Reply-to: Linn Kubler <lkubler@xxxxxxxxx>, For users of Fedora Core releases <fedora-list@xxxxxxxxxx>

Hi,

Frist time posting here, if this is the wrong list for this type of
question please forgive me.

When I boot my server I get this message after logging in:
TSC cannot be used as a timesource.
Possible reasons for this are:
  You're running Speedstep,
  You don't have DMA enabled for you're hard disk (see hdparm),
  Incorrect TSC synchronization on an SMP system (see dmesg).
Falling back to a sane timesource now.

Can someone explain what's happening here and how to correct it?  When
I installed the server I used the same timesource I use on other
non-Linux systems.

BTW, this is an installation on VPC.

Thanks in advance,
Linn

• Follow-Ups:
  • Re: TSC cannot be used as a time source?
    • From: John DeDourek

• Prev by Date: Re: FLAME____ Why is the kernel source not included
• Next by Date: Re: FC2 locked up when killing runaway process
• Previous by thread: Dual Booting Windows XP and Fedora FC2
• Next by thread: Re: TSC cannot be used as a time source?
• Index(es):
  • Date
  • Thread