Re: kernel: rtc: 1000 > kern.hz: Timing will be inaccurate, please increase hz.

From: Nate Lawson <nate_at_root.org>
Date: Tue, 20 Apr 2004 10:38:44 -0700 (PDT)
On Thu, 15 Apr 2004, Ion-Mihai Tetcu wrote:
> I've started to get this messages after upgrading to
> /src/sys/dev/acpica/acpi_pcib.c rev=1.38 from rev 1.36
> and recompiling kernel. I've did that because of an incorrect routing
> that was fixed by Nate in this revision.
> (See the thread on current_at_ beginning with:
> http://docs.freebsd.org/cgi/mid.cgi?20040322192654.2f24ef17 )
>
> The new dmesg -v and sysctl hw.acpi and
> KERNCONF (KSE_ULE_UP_apic_2004_04_09 file) at:
> http://www.people.tecnik93.com/~itetcu/acpi/rtc/
>
> CLK_USE_I8254_CALIBRATION not specified - using default frequency
> Timecounter "i8254" frequency 1193182 Hz quality 0
> Calibrating TSC clock ... TSC clock: 2040351672 Hz
> CPU: AMD Athlon(tm) XP 2400+ (2040.35-MHz 686-class CPU)
>   Origin = "AuthenticAMD"  Id = 0x681  Stepping = 1
>   Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
>   AMD Features=0xc0400000<AMIE,DSP,3DNow!>
> Data TLB: 32 entries, fully associative
> ..........ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> ACPI timer looks GOOD min = 1, max = 2, width = 1
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
> acpi_cpu0: <CPU> on acpi0
> acpi_button0: <Power Button> on acpi0
> ...............
> procfs registered
> Timecounter "TSC" frequency 2040351672 Hz quality 800
> Timecounters tick every 1.000 msec
> ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to deny, logging disabled

I can't see anything wrong with your dmesg.  A quick grep through the
kernel doesn't show any message like in the subject line.  I'm ccing this
to current_at_ because the message sounds like it's hz or timecounter
related.  It's not likely that this message is acpi-related.

-Nate
Received on Tue Apr 20 2004 - 08:38:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:51 UTC