> On Sat, 28 Jul 2001, Mike Smith wrote:
> > You could also try building a kernel with CLK_CALIBRATION_LOOP defined
> > and then booting with -v (without the timer disabled). This might be
> > instructive (I don't know for certain that it'll calibrate the ACPI
> > timer, since it may not have been probed yet).
> It won't. CLK_CALIBRATION_LOOP only iterates calibration of the i8254
> and TSC timers relative to the RTC. None of the clock calibration stuff
> is very useful. All the clock frequencies depend on the temperature,
> so their values at boot time are only slightly more related to their
> values at run time than their values at a random time. Average values
> are probably better than boot time values.
Understsood, however the current problem reports indicate an off-by-2x
problem, which the calibration loops would deal with just fine.
Unfortunately, I can't reproduce the problem here - the new timer seems
to be working just fine. Can anyone seeing this please let me know:
- What power management hardware your system has: look at the output of
pciconf -lv for a "power management controller", eg:
none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82371AB PIIX4 Power Management Controller'
class = bridge
subclass = PCI-unknown
- which timecounter is in use on your system, eg:
mass# sysctl kern.timecounter.hardware
- whether you are seeing any "*time went backwards" console messages.
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message