MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
There is some kind of problem in Mandriva Linux 2006.0 that causes my software clock to run very fast.... it is gaining over two minutes every hour.
This is the first time I have run 2006.0 64bit SMP on this machine, previously I had LE 2005 (10.2) 32bit SMP running on it and there was no clock drift. Thus far, everything else seems to be running smoothly.
Asus A8N-SLI Deluxe, Athlon 64 X2 4200+, 1GB RAM, SCSI 2940, IDE, NVidia FX
Have you tried running ntp as a daemon or ntpdate? these will update your clock with a timeserver (be sure to find one of the round-robin dns time servers so that no single time server is overloaded).
In your ntp configuration file just put the following:
that will allow their dns to rotate through different time servers --helping to conserve bandwidth.
You can also update it manually by using ntpdate pool.ntp.org -- and you can run this in a cron job such as
0 * * * * (ntpdate pool.ntp.org)
You can configure these to run as often as needed (just beware that transaction processing programs such as Oracle do not like time shifts -- if you insert something at a date that is "before" the current time, it will mess it up).
Yes, I am (was) already running ntpd. The sw clock is so fast that ntpd will not keep it updated; besides- that doesn't fix the problem, just put a bandage on it. Since it is a home system, the time jumps aren't critical so...
It gets worse. I don't know if this is part of the same bug or not, but now, every day when I get home from work to use this home computer the keyboard stutters badly and I have to restart the Xserver to regain control. About every other key I press results in anywhere from 2 to 12 of that key being sent. Ug.
This is the summary based on my research and observations.... there is a problem in the 2.6.12 kernel that causes the kernel to make an incorrect assumption about the type/use of the clocks on an AMD 64 X2 dual core system. The problems it causes seems amplified by high/continuous CPU usage. You can tell if you are bitten because you will see one or more of three symptoms:
1) Your software clock will run too fast- gaining sometimes minutes per hour
2) At some point the keyrepeat under X will go haywire and cause keyboard stuttering
3) You will see messages like this "warning: many lost ticks." in /var/log/messages
The workaround is to boot the kernel with the "notsc" option. This will force the kernel to not use tsc. There is a patch to the kernel, also, that supposedly fixed the problem properly. When it makes it into the official tree, I don't know.
This is a serious enough kernel problem to warrant Mandriva posting Errata about the issue, since it will affect [probably] all people using 2006.0 with an AMD X2 processor and possibly issusing a new 64 bit kernel. Of course, this will affect all distributions, since it is a kernel issue.
Originally posted by crxssi This is a serious enough kernel problem to warrant Mandriva posting Errata about the issue, since it will affect [probably] all people using 2006.0 with an AMD X2 processor and possibly issusing a new 64 bit kernel. Of course, this will affect all distributions, since it is a kernel issue.
I was using 2006 and noticed this problem with my 3.0GHz x86 processor, so it may be more widespread than just AMD and 64 bit kernel. Mine gained about 2 minutes per day, give or take a few nanoseconds!
The workaround is to boot the kernel with the "notsc" option. This will force
the kernel to not use tsc. There is a patch to the kernel, also, that
supposedly fixed the problem properly. When it makes it into the official
tree, I don't know.
So therre's the workaround, but I'm not sure where to input this option.
I found several cases with the same problem. Try to add following options to the kernel at startup : "noapic nolapic". Mandriva's doc warns not to use apic and lapic if the PC is not a multi-processor.
You may modify these options for lilo or grub to make them permanent.
I seem to be having the same problem but with an AMD Sempron 3000+
The time is flying past almost at double speed... other than that everything seems fine. (except he keyboard struttering but easily fixed by slowing the repeat rate)
I tried the 'notsc' option but that changed nothing..