On Thursday 15 December 2005 02:03 am, Richard Fish wrote: > On 12/14/05, Noah J Norris <[EMAIL PROTECTED]> wrote: > > On Wednesday 14 December 2005 05:39 pm, Richard Fish wrote: > > > 1. Make sure that the first line of /etc/adjtime contains very small > > > values. In fact, you might just want to replace the first line with > > > "0.0 0 0.0". > > > > i tried changeing this is this for the hardware clock drift ? i dont have > > any problem with the hardware clock its the software clock thats fast > > Oh, you are correct. Sorry. > > > > 2. Take a look at the clock= settings in > > > /usr/src/linux/Documentation/kernel-parameters.txt. Maybe you need > > > clock=pit. > > > > looking in this file saw some other options that may help the problem. > > i have an ati chipset (newer laptop chipset) ouput of lspci below > > <snip> > > > some options i saw in that file that i may try > > > > acpi_skip_timer_override [HW,ACPI] > > Recognize and ignore IRQ0/pin2 Interrupt > > Override. For broken nForce2 BIOS resulting in XT-PIC timer. > > > > enable_timer_pin_1 [i386,x86-64] > > Enable PIN 1 of APIC timer > > Can be useful to work around chipset bugs > > (in particular on some ATI chipsets). > > The kernel tries to set a reasonable default. > > > > disable_timer_pin_1 [i386,x86-64] > > Disable PIN 1 of APIC timer > > Can be useful to work around chipset bugs. > > I'm not sure these will help. They seem to be more related to setting > up the frequency for the IRQ0 timer interrupt, for things like running > the scheduler. This should not be related at all to the behavior of > gettimeofday. > > I think if you were getting messages about lost ticks or got extra > ticks or something like that, these might be helpful, or if your > system seemed either to slow or too unresponsive. Of course, if your > clock is defaulting to TSC (which would be bad, BTW), then I guess > these could have a big impact. > i have gotton lost tick messages and apic errors mostly
> Take a look at dmesg or /var/log/messages for the following lines: > > Using TSC for gettimeofday > Using HPET for gettimeofday > Using .* for high-res timesource Using pmtmr for high-res timesource should an amd64 use HPET ? i do not have this enabled in kernel config (note running in 32 bit mode ) > > These will tell us what signal the kernel is using for gettimeofday on > your system. > > -Richard other thing i noticed in dmesg do i need to enable smp support in the kernel ? this is a single processor system that i know of . does amd do any type of hyperthreading ? found SMP MP-table at 000f8510 Using ACPI (MADT) for SMP configuration information ouput of cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 36 model name : Mobile AMD Athlon(tm) 64 Processor 4000+ stepping : 2 cpu MHz : 2587.282 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm bogomips : 5181.75 note here is an example of some errors about apic APIC error on CPU0: 00(40) APIC error on CPU0: 40(40) # this get repeated alot cat /proc/interrupts 0: 39865554 IO-APIC-edge timer 1: 23952 IO-APIC-edge i8042 8: 8 IO-APIC-edge rtc 12: 1559783 IO-APIC-edge i8042 14: 543485 IO-APIC-edge ide0 15: 1427625 IO-APIC-edge ide1 16: 1841139 IO-APIC-level yenta, ndiswrapper 17: 1419 IO-APIC-level ATI IXP 19: 124 IO-APIC-level eth0 20: 1 IO-APIC-level ohci_hcd:usb1, ohci_hcd:usb2, ehci_hcd:usb3 21: 453349 IO-APIC-level acpi NMI: 0 LOC: 19934340 ERR: 18 #notice errors here MIS: 0 -- life is linux linux is life -- gentoo-user@gentoo.org mailing list
