James Alexander Cook writes:
I might be wrong here, but doesn't NTP only make occasional adjustments to the
system clock?
It tries to slew the clock as smoothly as possible to bring it into
alignment with the correct time. It does not make sudden large changes
to the clock.
If your clock
Charles Swiger writes:
Try changing the kern.timecounter.hardware sysctl; you can look at the
available choices via:
sysctl kern.timecounter.choice
So what do the choices mean? How are they used?
On one machine, I see TSC, ACPI-fast, i8254, and dummy as choices, and
ACPI-fast is
to be used
* or not, nor when it might be activated. Play it safe.
*/
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Anthony
Atkielski
Sent: Thursday, May 05, 2005 1:44 AM
To: freebsd-questions@freebsd.org
Subject: Re: Clock
Ted Mittelstaedt writes:
Anthony, you really need to look in the code sometime:
It takes a very long time to find relevant sections of code, and unless
the author was very conscientious, there are usually few or no
explanatory comments, anyway.
/usr/src/sys/dev/acpica/acpi_timer.c
Thanks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Anthony
Atkielski
Sent: Thursday, May 05, 2005 4:14 AM
To: freebsd-questions@freebsd.org
Subject: Re: Clock running fast
Ted Mittelstaedt writes:
Anthony, you really need to look in the code
Ted Mittelstaedt writes:
It is probably a tossup between the i8254 driver taking cycles to run
and an internal kernel counter based off the CPU clock taking cycles to
run.
I was talking about SMM, which steals cycles invisibly and also allows
mystery software to run in the BIOS.
--
Anthony
At 14:49 5/4/2005, Ryan Winograd, wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What information would be helpful?
On May 4, 2005, at 3:49 PM, Ryan Winograd wrote:
I recently noticed that the system clock on a machine i recently set
up is running very quickly, about 2x realtime by my measuring. What
can i do to solve/investigate this problem? What information would be
helpful?
Try changing the
On Wed, May 04, 2005 at 03:51:05PM -0500, W. D. wrote:
At 14:49 5/4/2005, Ryan Winograd, wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What
At 16:07 5/4/2005, Kris Kennaway wrote:
On Wed, May 04, 2005 at 03:51:05PM -0500, W. D. wrote:
At 14:49 5/4/2005, Ryan Winograd, wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do
On 5/4/05, Ryan Winograd [EMAIL PROTECTED] wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What information would be helpful?
Thanks,
Ryan
Tomas Quintero wrote:
On 5/4/05, Ryan Winograd [EMAIL PROTECTED] wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What information would be
On Wed, May 04, 2005 at 03:51:05PM -0500, W. D. wrote:
At 14:49 5/4/2005, Ryan Winograd, wrote:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What
Charles Swiger wrote:
On May 4, 2005, at 3:49 PM, Ryan Winograd wrote:
I recently noticed that the system clock on a machine i recently set
up is running very quickly, about 2x realtime by my measuring. What
can i do to solve/investigate this problem? What information would be
helpful?
Try
On May 4, 2005, at 3:49 PM, Ryan Winograd wrote:
I recently noticed that the system clock on a machine i recently
set
up is running very quickly, about 2x realtime by my measuring.
What
can i do to solve/investigate this problem? What information would
be
helpful?
Try changing the
On May 4, 2005, at 6:19 PM, fbsd_user wrote:
sysctl kern.timecounter.choice does not work on my 4.10 system
sysctl kern.timecounter.hardware and sysctl kern.timecounter do
work.
True, this interface has changed slightly, since 4.x as 5.x has better
APCI support. Running a sysctl -a
On May 4, 2005, at 6:19 PM, fbsd_user wrote:
sysctl kern.timecounter.choice does not work on my 4.10 system
sysctl kern.timecounter.hardware and sysctl kern.timecounter do
work.
True, this interface has changed slightly, since 4.x as 5.x has
better
APCI support. Running a sysctl -a
On May 4, 2005, at 6:46 PM, fbsd_user wrote:
Running a sysctl -a kern.timecounter ought to be a
useful starting point for any recent version of FreeBSD.
Your response is not very clear.
Are you saying that kern.timecounter.choice is not in 4.10
How can I find out what choices are?
You can find
Ryan Winograd writes:
Hi all,
I recently noticed that the system clock on a machine i recently set up
is running very quickly, about 2x realtime by my measuring. What can i
do to solve/investigate this problem? What information would be helpful?
If the machine has network access to an NTP
On Wed, 4 May 2005, Ryan Winograd wrote:
Charles Swiger wrote:
On May 4, 2005, at 3:49 PM, Ryan Winograd wrote:
I recently noticed that the system clock on a machine i recently set up is
running very quickly, about 2x realtime by my measuring. What can i do to
solve/investigate this problem?
20 matches
Mail list logo
