On 9/20/07, thad <[EMAIL PROTECTED]> wrote: > On 9/20/07, andrelst <[EMAIL PROTECTED]> wrote: > > Have seen this problem in vmware virtual machines where linux is a > > guest. The fix is to add a parameter in grub/lilo. Check google if > > there is a fix. > > The box is not set up to host any virtual machine, its a database server.
too fast typing it... missed a sentence. Still, there is a parameter in grub/lilo. have you tried passing the no_timer_check parameter? > > NTP won't help you here because it tries to change the time gradually, > > but then the time drifts again and so on and so forth. Besides, NTP is > > smart enough not trust itself for time. run ntpq -pn and you will see. > > It seems it cannot cope with the very fast clock, I have done all the > fix as advised in Redhat Knowledge base and I observe the problem > still persists. Could this be a hardware issue? Well, it seems to be partly Linux fault. Specifically in 2.6.xx kernels. Have not seen this issue in 2.4.xx and 2.2.xx kernels. Partly is the hardware. Have seen this issue from mass produced boards with cheap clock resonators to even the low end non X86 Netra X1, V120, T2000, etc. A bios update might help though... check the release notes. -- regards, Andre | http://www.varon.ca _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
